Connect to SQL database ERROR from IRPRMTLR or IRPRMCOL in wvlog.txt
Logged when these components cannot connect to the PRM database. The detailed SQL error is also returned in the message. For example, “SQL Server does not exist or access denied” would indicate that the SQL server is not currently available. While this error is being logged, data will not be available in the PRM Displays and Thresholds.
It is recommended to reconfigure Transact using the prmconfig script to specify the correct connection details for the database. Transact requires an SQL login to the database. The prmconfig script will provide a warning if the connection details are incorrect. If unsure of the correct details, these can be first confirmed using the SQL Server Management Studio.
Batch Error and DumpFile threshold conditions do not trigger
These threshold conditions rely on the ADD WATCH_DIR settings in the PRM Configuration on the server where Authproc or the Analytic Gateway is running. If these settings are not configured or are pointing to the wrong directories, then these threshold conditions will not trigger.
Correct the ADD WATCH_DIR settings in the PRM Configuration. The directories to be configured vary between version 7 and 8. This is described in Configure the AuthProc/Analytic Gateway.
DatabaseID <nn> not found error from IRMSSQL in wvlog.txt
Typically a view has been started on the MSSQLTables or MSSQLIndexPhysicalStatistics records with incorrectly specified Associate Names. The Tables window in the Proactive Risk Manager Platform Display is one example. This window needs to be edited after install to specify the database ID of the NRT database within the specified SQL server instance.
Find the database ID of the NRT database. If the prmconfig script has been used to configure the product, list the properties of the active PrmThresh threshold from the Prognosis Windows Client and check the Associate Names tab on the TableSize condition. The entry will be of the form PRM <nn> where <nn> is the database ID (e.g. PRM 4). Enter the database ID in any PRM Displays, Thresholds or Databases that produce this error when run.