Client computers, as well package servers, are not receiving new client policies. The client computer shows the following warning on the Agent logs:
Priority: 2 Date: 7/12/2007 8:23:01 AM Tick Count: 1636171500 Host Name: ComputerName Process: AeXNSAgent.exe (6736) Thread ID: 5532 Module: AeXNSAgent.exe Source: ConfigServer Description: RequestPolicies failed: Unexpected response from URL http://ServerName/Altiris/NS/Agent/GetClientPolicies.aspx?xml=<Request configVersion="2"><WrkstaGuid>d75ae639-b452-4306-a27d-5ed8a9805637</WrkstaGuid></Request>&compress=1&hash=1: Unable to get the client policies for specified resource (Resource: d75ae639-b452-4306-a27d-5ed8a9805637, Exception: Exception of type System.OutOfMemoryException was thrown.) (-2147418113)
As well, you may find similar messages on your Package Servers: Priority: 1 Date: 7/12/2007 8:23:38 AM Tick Count: 1636208063 Host Name: ComputerName Process: AeXNSAgent.exe (6736) Thread ID: 6532 Module: AexPackageDelivery.dll Source: PackageDownload Description: Download Snapshot failed: Unable to get the package snapshot. Reason: Unable to get the snapshot for package Example Package. Reason: Exception of type System.OutOfMemoryException was thrown. (-2147418113)
Looking on the Notification Server logs, you can find error messages referring to unable to provide client policies for specified resource which in this case are every computer that is trying to get a configuration or policy. In the error message you may see the computer name and then 'Deleted' as part of the message. For example: MyClientComputer001. Deleted: MyClientComputer001.
As well as part of the error message on the NS logs, you will find that there are OutOfMemoryExceptions when client policies are requested.
Unknown. The cause will have a direct relationship to any process on the NS that is consuming large amounts of memory.
Any "out of memory" issue is a result of poor server configuration, a legitimate lack of physical memory, or a memory leak. If you observe this issue, use Task Manager to identify the processes that are using large amounts of memory. Make note of this information for future troubleshooting. Out of memory conditions are likely to reoccur if nothing is done to address the cause of the issue.
Apply the latest NS rollup and the latest Active Directory Integrated Component, both have resolved issues with memory leaks.
If SQL server is present on the same box, determine if SQL has been configured to use to reserve too much memory. For small servers, SQL should be left in dynamic mode, or configured to use no more than 50% of the addressable memory (up to 1.5GB). SQL server is very reluctant to release memory for usage by IIS and the Altiris services, thus hard coding it to use 2GB of memory on a 4GB server will cause out of memory errors.
Use the Altiris supplied Perfmon counters from the KB system to identify if additional memory should be installed on the server.
Disable any unneccessary services and 3rd party applications on the box, and configure virus scanners to stop scanning all incoming NSE packets and database files.
A temporary fix is to restart the Altiris Service, Altiris Client Message Dispatcher, and IIS. After these services restart, try to request configuration from one of the affected computers. This should refresh the threads on the Notification Server and free up some of the memory assigned to it.
Applies To Notification Server 6.0.6074 SP3 Altiris Agent 6.0.2386
Imported Document ID: TECH32110
Subscribing will provide email updates when this Article is updated. Login is required.