Manually Resolving Inconsistencies
LemonTree detects different kinds of inconsistencies. While it is able to resolve some of these, other inconsistencies may need to be manually fied.
This page shows an overview what kinds of inconsistencies may occur in your model and what you can do about them.
| Error Level | ErrorCode | Description | Details | Solution | Found by EA Integrity Check? |
|---|---|---|---|---|---|
| Fatal | 200000000 | Element with Type '{0}' was found, which has the same Guid. | A duplicate GUID in the database. That is so far the only inconsistency LemonTree is not able to handle. LemonTree cannot process these models. | Resolved by EA Integrity Check.1 | yes |
| Error | 92000000 | Referenced Element 'Owner' with Reference '{0}' couldn't be found. | LemonTree found an element that has no owner set. So it cannot be found in the model. | Resolved by EA Integrity Check.1 | yes |
| Error | 92000000 | Referenced Element 'Represents' with Reference '{0}' couldn't be found. | LemonTree found a diagram link that has no connector set. | Resolved by EA Integrity Check.1 | yes |
| Error | 210000000 | Element with Type 'genopt' was found, which has the same Guid. | The database table t_genopt holds settings for MDG technologies This table contains two settings for the same target. | Resolved during LemonTree Merge.2 | no |
| Error | 112000000 | Reference 'Owner' isn't set, because 'OwnerObjectId' is not defined. | LemonTree found a connector that has no owner set. So it cannot be found in the model. | Resolved by EA Integrity Check.1 | yes |
| Error | 112000000 | Reference 'Source' isn't set, because 'SourceObjectId' is not defined. | LemonTree found a connector that has no source set. So it cannot be found in the model. | Resolved by EA Integrity Check.1 | yes |
| Error | 112000000 | Reference 'Target' isn't set, because 'TargetObjectId' is not defined. | LemonTree found a connector that has no target set. So it cannot be found in the model. | Resolved by EA Integrity Check.1 | yes |
| Error | 52000000 | Unexpected type '' in 'ElementID' occured. Expected type 'System.Int32'. | An element-reference has been lost. | Resolved by EA Integrity Check.1 | yes |
| Error | 412000000 | t_package entry with GUID '{0}' found, where the corresponding t_object entry has a different GUID '{0}'. | The database (correctly) contains two entries for a package, but the unique identifiers differ. | Resolved during LemonTree Merge.2 | no |
| Warning | 92000000 | Referenced Element 'ConveyedInformationFlowItem' with Reference '{0}' couldn't be found. | The connector listed in the "Element GUID" has "Information Items Conveyed" that no longer exist. EA ignores that items. The list in the EA UI will not contain that elements. But the link to them is still stored in the database (table t_xref). | Take a look at that connector and see if there is some information missing. 1) Find the connector via EA "SQL Scratch Pad": select Connector_ID from t_connector where ea_guid = '{B}' 2) Find the diagram containing the connector: a) select diagramID from t_diagramlinks where ConnectorID = 1 b) select * from t_diagram where diagram_ID = 2a 3) Check if the diagram contains all the expected information 4) Select the connector and add the correct "Information Items Conveyed" Note: If the list should be empty. Add any item and delete it again, EA will then update the list. |
no |
| Warning | 92000000 | Referenced Element 'LoopNodeLoopVariable' with Reference '{0}' couldn't be found. | A LoopNode is referencing a variable that is no longer present in the model. | Take a look at the LoopNode an see if something is wrong. 1) Find the LoopNode a) EA: "SQL Scratch Pad" select Name from t_object where EA_GUID = '{2}' b) Common Searches → Simple: Search for the Name 2) Check if the LoopNode is containing all expected information and correct it otherwise. Note: To get rid of the inconsistency and the loop is correct, add a variable and delete it again. |
no |
| Warning | 92000000 | Referenced Element 'Type' with Reference '{0}' couldn't be found. | Catch-All Inconsistency for elements of various types which reference elements which no longer exist. | Automatic option: resolved during LemonTree Merge. Manual option: find the element in EA and remove the type reference 1. Download and import the search AnyElementByGuid In EA: Search (Ctrl + F) > Model:  2. Select the category "My Searches" and the search "AnyElementByGuid" 3. Enter the GUID reported by the LemonTree Inconsistency check into the <Search Term> box 4. Run the search (F5) 5. Right-click the search result and select "Find in Browser" 6. Edit the type of the element a. In case of attributes, ports, activity parameters and action pins, it is the "type" b. in case of operation, it is the "return type" c. in case of all other elements it is the classifier (Ctrl + L) 7. In the type selection dialog you will see that no element is select (since EA cannot find the linked element) 8. Scroll to the very bottom and select the entry <None>  |
no |
| Warning | 100012000000 | Xref of stereotype with Name '{0}' doesn't contain Guid nor FqName. | Stereotype entry in table t_xref is incomplete. | Resolved through Stereotype Fix Tool. 3 | no |
| Warning | 200012000000 | Referenced Stereotype '{0}' with Name 'implements' couldn't be found. | Stereotype cannot be found due to incomplete entry in database. | Resolved through Stereotype Fix Tool. 3 | no |
| Warning | 80012000000 | Primary Stereotype with Name '{0}' doesn't have respective xref. | Entry in table t_xref is missing. | Resolved through Stereotype Fix Tool. 3 | no |
| Warning | 400012000000 | Referenced Stereotype '{0}' with Name '{1}' couldn't applied to element with MetaInfo '{2}'. | An element has a sterotype assigned, whose "AppliesTo" settings do not allow this combination. | Resolved through Stereotype Fix Tool. 3 | no |
| Warning | 10014000000 | Action with guid '{0}' references its 'result' Pin (name of Pin: '{1}') with wrong Pin direction. Requested direction 'output', but was 'input'. | The names of pins imply certain directions. A pin was found, for which this implication does not hold. | Resolved during LemonTree Merge.2 | no |
| Warning | 52000000 | Found a package in t_object without matching entry in t_package. | A package requires two database entries to fully store its data. One of these entries does not exist, making the stored information incomplete. | Resolved by EA Integrity Check.1 | yes |
| Warning | 52000000 | Unexpected type '' in 'PDATA1' occured. Expected type 'System.Int32'. | An element-reference has been lost. | Resolved by EA Integrity Check.1 | yes |
| Info | 54000000 | Property (Attribute) found, where the Type string doesn't match the Classifier. Type='{0}', Classifier='', GUID of Classifier='{1}'. Try to use the Project Integrity check of Enterprise Architect to correct the model. | A property may refer to an element, or a fixed text as its type. This property has both variants set, but the set fixed text does not match the name of the element. | Resolved by EA Integrity Check.1 | no |
| Info | 8014000000 | Unexpected Property-Value '{0}' for Property '{1}' occured. | A property has a value which is not within the set of allowed values for this property. | Resolved during LemonTree Merge.2 | no |
1) Information on resolving inconsistencies via the EA Integrity Check is available here: Resolving Inconsistencies via the Enterprise Architect Integrity Check
2) Information on the automatic resolution of inconsistencies during a LemonTree merge is available here: Automatic Resolution of Inconsistencies During Merge
3) Information on resolving inconsistencies via the Stereotype fix tool is available here: Resolving Stereotype Inconsistencies