--- title: "CMJ Field layout scheme entity - DB misconfiguration" canonical: "https://support.appfire.com/space/SUPPORT/80117902/CMJ%20Field%20layout%20scheme%20entity%20-%20DB%20misconfiguration" format: markdown --- ### **Symptoms** The deployment is failed with the unknown error | **2022-05-26 13:24:35,390 http-nio-8080-exec-120 url: /rest/configuration-manager/1.0/deployment/5/conflicts/analysis; user: marius.rusu ERROR marius.rusu 804x345034x1 ww8fmg 109.166.131.111,100.64.133.139 /rest/configuration-manager/1.0/deployment/5/conflicts/analysis [rollout.impl.rest.AbstractResource] com.atlassian.jira.exception.DataAccessException: No FieldLayoutScheme found for id 11511**
**com.atlassian.cache.CacheException: com.atlassian.jira.exception.DataAccessException: No FieldLayoutScheme found for id 11511**
**        at com.atlassian.cache.ehcache.DelegatingCache.get(DelegatingCache.java:113)**
**        at com.atlassian.jira.issue.fields.layout.field.DefaultFieldLayoutManager.getFieldConfigurationScheme(DefaultFieldLayoutManager.java:544)** | | --- | ### Cause There is a problem with an association between a Field Configuration and a Field Configuration Scheme and this prevents CMJ from displaying the different in the deployment wizard. **Resolution** - Perform Jira's system integrity checker and fix any detected errors on the target system? The detailed instructions here - [https://confluence.atlassian.com/adminjiraserver071/using-the-database-integrity-checker-802592958.html](https://confluence.atlassian.com/adminjiraserver071/using-the-database-integrity-checker-802592958.html) - If the reindexing doesn’t solve the issue, follow the workaround solution proposed in the link. You can do it by deleting the missing references from **fieldlayoutschemeentity**** **table which should be performed and tested on the testing environment. For more details, please refer to the [https://jira.atlassian.com/browse/JRASERVER-68635](https://jira.atlassian.com/browse/JRASERVER-68635) . **Workaround** > Macro (inline-external-image)  **DELETE** statements are to be used at your own risk and aren't supported by Atlassian. > Macro (inline-external-image)  Take a database dump before deleting rows from your database. Delete the missing references: > ℹ️ DELETE FROM fieldlayoutschemeentity WHERE scheme NOT IN (SELECT id FROM fieldlayoutscheme);