CAST Management Studio - Information - Type of issues
The purpose of this page is to describe the type of issues you can face using all CAST AIP tools.
These are the most common issues that we use to see at CAST Technical Support :
A crash is an unexpected issue that stops suddently the process you are running.
When you open the log file of the process that has failed you will see that the log file is not complete.
Example of crash
If an analysis has crashed, the analysis log file will appear as below :
You can see in the above screenshot that the log file is not complete.
A fatal error is an unexpected issue that stops the process you are running. The log file of the process that has failed is complete but the last message before the end of the log is an Error message.
Example of Fatal Error
In the DMT, if an extraction is crashing, the extraction log file will appear as below :
NON FATAL ERROR
A non fatal error is an error message that does not stop the process you are running. In the log file of the process, the Error message are not appearing just above the end of the log file.
Example of Non Fatal Error
Warning message are non blocking messages.
Performance issue means either that the process currently running is stuck and never ends or it takes longer than expected to finish.
After the analysis and the snapshot have been performed, objects may have been not analyzed and not visible in Enlighten or not taken into account in the Dashboard.
During analysis, some links may have not been resolved. This is visible in Enlghten, when we expect link between two objects, or in Transaction Configuration Center (TCC) when we notice that a transaction is missing or incomplete.
These are inconsistencies between results on the CAST Engineering Dashboard and results from another CAST product or between different pages of the CAST Engineering Dashboard.