Error: Request timed out ... [System.Web.HttpException @ ] when accessing /altiris/NS/Agent/GetClientPolicies.aspx
search cancel

Error: Request timed out ... [System.Web.HttpException @ ] when accessing /altiris/NS/Agent/GetClientPolicies.aspx


Article ID: 246185


Updated On:


Client Management Suite IT Management Suite


Suddenly started seeing GetClientPolicies.aspx requests time out in the Notification Server logs:

Severity: 1
Date: 7/15/2022 7:58:39 AM
Tick Count: 42834078
Host Name: <NS name> 
Process: w3wp (808)
Thread: 814
Module: Altiris.Web.NS.Agent.dll
Source: Altiris.Web.NS.Agent.Global.Application_Error
Description: Unhandled exception.

Request timed out.
   [System.Web.HttpException @ ]

Exception logged from: 
   at Altiris.Web.NS.Agent.Global.Application_Error(Object, EventArgs)
   at System.Web.HttpApplication.RaiseOnError()
   at System.Web.HttpApplication.RecordError(Exception)
   at System.Web.HttpApplication+PipelineStepManager.ResumeSteps(Exception)
   at System.Web.HttpApplication.BeginProcessRequestNotification(System.Web.HttpContext, AsyncCallback)
   at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)

User [<domain>\<AppID>], AppDomain [/LM/W3SVC/1/ROOT/Altiris/NS/Agent-2-133023209880783165]

HTTP [POST]: https://<NS server>.<domain>.net/altiris/NS/Agent/GetClientPolicies.aspx
 ip: []; x-sma-version: [8.6.3269.0]; languages: [en-US]; content-length: [6410];
 timings: [[W] 00:10:13.5180984];
 response: [200 OK]; x-smp-error: [8000FFFF]; x-smp-nsversion: [8.6.3268.0];


ITMS 8.6 RU2 & v1 pointfixes


The errors went away after the Notification Server was rebooted and didn't come back (assuming that restarting IIS may also have resolved this)

NOTE: Another scenario was that the Notification Server (NS) was seeing the error above when the NS randomly rebooted and this issue was resolved by moving the NS to another node in the virtual environment.