Error messages

UNICOM Intelligence Professional displays a message in the Output pane when an error occurs when you run a script. Some messages are simple and self-explanatory. However, some error messages are more complex and can originate in more than one component. For example, the following message was displayed when running a table script in which the connection string for an RDB database was specified incorrectly.

Table aggregation failed: Aggregator error 239: Failed to initialise CDSC.:
Error creating RDB2 schema. Schema creation is required because the SchemaVersion
table is missing. A partial schema may have been created and this will need to be
dropped before attempting to reconnect: Unknown table 'SchemaVersion'

The first part of this message originated in the Table Aggregator, which is a component that is used by the Table Object Model (TOM) to populate tables. (For more information, see Table population sequence.) The second part of the message originated in RDB DSC 2, which the Table Aggregator uses to access the case data in the RDB database. This is merely an example of an error message that originates in two UNICOM Intelligence components. Some error messages might originate in more than two components, and might include messages from Windows components and any other components you reference in your scripts.

Error messages that originate in UNICOM Intelligence components generally contain an identifying text or a prefix, and this is helpful when attempting to track down the cause of the problem. For example, knowing that the error originated in RDB DSC 2 helped the scriptwriter establish the cause of the error.