CMI (Casewise Analytics)
Log Files:
Path and name can be set in the Load automation application.
|
Load Automation Errors | |
|
Error: Illegal XML characters detected in column(s): {Column Name(s)} |
Data Error: May or may not stop the load Troubleshooting steps: 1.Run Validate Repository to collect the error. 2.Use – applyfixes:1005 with the validate repository in the command line. If the above doesn’t work, contact Service Desk or Support Team. |
|
Error: {Object Type} is an intersection object (or intersection-like object) without an association type |
Data Error: This may not stop data loading. The association may have been deleted from the original model, but it hasn't been cleaned up. |
|
{Time} {Model File Name}\Operation Duration: 01:48:06.216 (6.48622e+006 ms) [Errors: {NrErrors} Warnings: {NrWarnings}] |
When the load finishes, if it stops the load then would need checking. Troubleshooting steps: 1.Examine the error log for errors. 2.Fix the error manually or apply fixes. If the above doesn’t work, contact Service Desk or Support Team. |
|
Model: {Model File Name} Table: Validating: CMTOBJECTTYPE
{Time} Error: Errors occurred during data validation |
If validation errors occur, they may or may not stop the load, but if you need to know which model it applies to, you must read the 4 lines (including a blank line) during loading. No Troubleshooting steps, contact Service Desk or Support Team. |
|
ERROR: Model '{Model File Name}' failed to load - Error code: {Error Code}
LoadAutomation Summary: Error: CM Unload for model DEVCINSP failed with error code 1. Model 'DEVCINSP' successfully loaded. Model 'DEVOPSW' successfully loaded. Model 'DEVOPSTS' successfully loaded. |
If an unload fails, it will be reported here but may not stop the load.
Occurs due to above scenarios. No Troubleshooting steps, contact Service Desk or Support Team. |
|
FAILED: {Some Error} |
If the error is Obvious from the logs, then user may be able fix it or contact Service Desk. |
|
ERROR: Failed to unload the Administration model into CMI - Can not continue! |
If the error is Obvious from the logs, then user may be able fix it or contact Service Desk |
|
Passed log file path could not be created! |
Troubleshooting steps: 1.Make sure the Location path is correct. 2.Verify that the user can access the location. If the above doesn’t work, contact Service Desk or Support Team. |
|
Could not find CM install folders |
Troubleshooting steps: 1.Make sure the desktop tool and CMI are on the same machine. If the above doesn’t work, contact Service Desk or Support Team. |
|
Rarely occurring Errors | |
|
"(Shape) Symbol {Symbol Id} on diagram {Diagram Id} does not exist. |
Warnings: Maintaining the Data's Integrity |
|
(Line Ending) Symbol {Symbol Id} on diagram {Diagram Id} does not exist. |
Warnings: Maintaining the Data's Integrity |
|
Diagram definition is unreadable. Rejecting diagram. |
Contact Service Desk or Support Team. |
|
Duplicate Record, ID = {Unique Identifier} |
Troubleshooting steps: 1.Examine the error to identify its root cause. If the above doesn’t work, contact Service Desk or Support Team. |
|
Built in Object Type {Object Type} is missing |
Occurs when the source data is corrupt or incomplete |
|
Built in Property Type {Object Type}. {Property Type} is missing |
Occurs when the source data is corrupt or incomplete |
|
Built in Pane {Object Type}." {Pane} is missing |
Occurs when the source data is corrupt or incomplete |
|
Built in Lookup {Object Type}." {Property Type}{LookupUUID}) is missing |
Occurs when the source data is corrupt or incomplete |
|
Built in Association Type {Association Type} is missing |
Occurs when the source data is corrupt or incomplete |
|
Initialization Errors | |
|
No Models in the parameter List |
Command line is not set correctly. Troubleshooting steps: 1.Set command line correctly. |
Error messages
Error messages
Use the table below to understand any error messages you may encounter:
|
Upgrade for grid failed because of the intersection node is missing inside the page <attribute_associations> on node Table (Complex) which is a cwWebDesignerTreeNodeBehaviourKendoGrid |
|
This happens when the Intersection Grid option is selected in a Table (Complex) behavior, but there is no intersection node for the table. To resolve this error, use the Selected Properties to add the properties. |
Font Size Too Big on Diagrams
Font Size Too Big on Diagrams
To change the palette version the user needs to be able to run SQL management studio .
1.Open SQL Management studio select the model and expand the tables
2.Select the diagram table and chose edit top 200 rows
3.Change to the SQL view and replace the text with:
SELECT TOP (200) MODEL_NAME, DI_ID, ANO_ID, ANO_TABNR, DI_NAME, DI_SYMBOLS, DI_TEMPLATE, DI_TITLE
FROM DIAGRAM
WHERE (DI_ID = 2) AND (MODEL_NAME = 'CWFREX09')
Replace DI_ID with your diagram ID and replace CWFREX09 with the correct model file name
|
|
This must be upper case , if upgrading all diagrams, omit DI_ID and change (200) depending on how many models you require |
4.In the DI_SYMBOLS column click inside the cell to edit the palette XML.
5.Set the element <OriginalVersion OriginalVersion='2'> to <OriginalVersion OriginalVersion='4'>
6.Close SQL Management studio when complete.
7.When all of these have been changed using one of the CM applications (Corporate Modeler, Model Explorer or Object Explorer) the font size in styles that are referenced in the palette are reduced by 20%. Open every object on the palette, go to its style (if it has one) and reduce the font to the nearest whole number that is 20% smaller (e.g a 10pt font becomes an 8pt font).
Elastic/Global Search Using Too Much Memory
Elastic/Global Search Using Too Much Memory