The following is a list of general issues known to exist at the time of Quest release:InTrust 9.5.
CR0115565
Two InTrust Servers cannot concurrently process each other using agents.
CR0115564 You may not be able to log on interactively to a computer where InTrust Server is installed, if the InTrust Configuration database went offline while restarting the computer. Wait until the database goes back online or for about 5 minutes, then try logging on again.
CR0122083,
CR0122368
Don't delete the Default configuration objects (Default databases, repositories, operators, etc.) even if you never use them in InTrust sites, policies etc. Other predefined objects may have references to the Default objects by default, which may result in hard-to-find errors if referenced objects no longer exist in your InTrust configuration database. Note that the deleted predefined configuration objects are not recreated at InTrust upgrades or reinstallations, some of them causing errors at the setup phase if missing from the configuration database.
The recommended practice is to keep default configuration objects as templates for the custom ones you create for the routine use.
CR0112241 If two operator records with the same computer name exist in the InTrust configuration and both are specified as operators to notify, then two NET SEND notifications are sent to that one computer.
CR0114810
When you manually stop the Quest InTrust Server service, check the state of its dependent services (Quest InTrust Agent and Quest InTrust Agent Installer) while it is being stopped. If stopping the Quest InTrust Service takes a considerable time, its dependent services may be restarted and will have to be stopped manually. This behavior of dependent services may also prevent the Quest InTrust Server service itself from being stopped successfully, and you will have to manually terminate its process in Windows Task Manager.
CR0114831
When you restart InTrust services on an InTrust Server serving a large number of agents, real-time monitoring and gathering may require a few minutes to start working again after the services are started.
CR0115601
If you attempt to start Quest InTrust Server or Quest InTrust Real-Time Monitoring Server service and receive the error 'Unspecified error', in most cases this means that the license related to this service has expired. Look in the InTrust event log on the InTrust Server machine for a more detailed description of the error.
CR0151967
If there is an e-mail notification configured to be sent to multiple Operators and InTrust fails to send it to one Operator, for example because of an invalid e-mail address, the notification isn't sent to the other Operators on the list either.
CR0151964
You may receive the following error message when you try to view the details of a specific license in the Installed Licenses dialog: 'Error 0x00004655: Cannot open dialog. Reason: 0x839C0002: Unknown error: 0x839C002'. This happens when you try to view details of a license that has expired.
CR0145993
When the system time is set back on an InTrust Server computer or on a computer with InTrust agent running, InTrust agent-server operation may become unstable or even broken. It is recommended to restart InTrust services (either Quest InTrust Server or Quest InTrust Agent) on the computer after setting the system time back on it. Automatic time adjustment for daylight savings does not produce this effect on InTrust and does not require restarting any InTrust services.
CR0155892
The following error message logged to the session results of an InTrust task may indicate of a frequent changes in the system time on the InTrust Server computer:
Error: 0x80040e2f Cannot initialize the required component. Cannot initialize session. Sessions Error- The statement has been terminated. Sql State: 01000 Native Error Code: 3621 Violation of PRIMARY KEY constraint 'PK_ITGSessionsInfo'. Cannot insert duplicate key in object 'dbo.ITGSessionInfo'. Sql State: 23000 Native Error Code: 2627 , !! IDispatch error #3119
This may be happening because of some problems with hardware or operating system, frequent time synchronizations with multiple hosts on the network or some other reason.
CR0130865
If an InTrust Site includes an AD site that has subnets misconfigured, InTrust may try processing, when monitoring or gathering from this InTrust Site, a lot of unrelated computers or even all computers in the Domain(s) that the AD site spans.
CR0155885
You may be confused with events you may find in the InTrust event log on the InTrust Server computer stating that a job has completed with error and providing an error code without any error description. These events don't signal of any problem and may be ignored. They are logged to the InTrust event log in order to have process exit codes for InTrust jobs saved for the purpose of possible troubleshooting.
CR0146236
When you edit filters in data sources for IIS logs, ISAS logs, DHCP logs and Exchange events, and you want to use filtering by empty string value, specify empty strings. To do it, leave the text box in the Add/Edit String dialog box empty and click OK.
