KNOWN ISSUE: Search for a file report times out
|Article:TECH28001|||||Created: 2007-03-27|||||Updated: 2007-03-30|||||Article URL http://www.symantec.com/docs/TECH28001|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
The Search for a file report fails with a time out error
Recovery Solution 6.2
Database connection timeout.
Using the Notification Server Configurator, change the following settings in the CoreSettings.Config file. Note: The CoreSettings.Config is located at InstallPath\Program Files\Altiris\Notification Server\Config. When using the Notification Server Configurator to change the setting, stopping and restarting the Altiris Services on the Notification Server is not required.
- ReportingCommandTimeout—If reports are timing out, increase the value by 300. If reports are still timing out, increase the value by another 300.
- DbCommandTimeout—Keep this value synchronized with the ReportingCommandTimeout value. Note: The DbCommandTimeout setting in the CoreSettings.config file is the same setting as the Altiris Console > Server Settings > Notification Server Settings > Database Settings Command timeout field value.)
These changes are implemented immediately. It is not required to restart services or reboot the Notification Server computer for the setting changes to take effect.
|Description||Logged in tlndev (Altiris - Talinn) database|
Article URL http://www.symantec.com/docs/TECH28001