KNOWN ISSUE: Getting multiple errors related to: System.Web.HttpException (System.Web): The file '/Altiris/NS/NS/Agent/PostEvent.aspx' does not exist.

Article:TECH214871  |  Created: 2014-02-10  |  Updated: 2014-07-22  |  Article URL http://www.symantec.com/docs/TECH214871
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.
Article Type
Technical Solution


Issue



 Customer noticed multiple errors on the NS logs related to the following message:

Description: Unhandled exception. System.Web.HttpException (System.Web): The file '/Altiris/NS/NS/Agent/PostEvent.aspx' does not exist.

Also, you may see this for other pages:
"The file '/Altiris/NS/NS/Agent/CreateResource.aspx' does not exist."
"The file '/Altiris/NS/NS/Agent/GetClientPolicies.aspx' does not exist."

 


Error



"Errors", "Unhandled exception. 
System.Web.HttpException (System.Web): The file '/Altiris/NS/NS/Agent/PostEvent.aspx' does not exist.
at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IE xecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) Exception logged from:
at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception, String footer)
at Altiris.NS.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
at Altiris.NS.UI.AltirisWebApplication.Application_Error(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.HttpApplication.RaiseOnError()
at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(Http Context context, AsyncCallback cb, Object extraData)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr) at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)


Environment



 ITMS 7.5


Cause



 Known issue. 


Solution



 This issue has been reported to the Symantec Development team. A fix has been included in the ITMS 7.5 SP1 release. The fix should prevent this issue for occurring but if you already have the issue previous to the final fix, you may need to follow the steps below.

The current workaround is the following:

1. Create a new folder anywhere on your SMP server. As an example, we created a folder called “C:\NSRedirect”
2. On the new folder, double-click>properties>security tab and add ‘IIS_IUSRS’



3. Open IIS Manager and add a new IIS virtual directory under Default Web Site>Altiris>NS called "NS"
a) Navigate to Default Web Site>Altiris>NS and double-click>Add Virtual Directory



b) On the ‘Add Virtual Directory’ window, under ‘Alias:’, call it ‘NS’
c) Under ‘Physical path:’, browse to the new directory created on step 1




4. Add a redirect so any request that comes for "/Altiris/NS/NS/...." will go to '/Altiris/NS/' 
a) Select the new virtual directory and under the IIS section on the main frame, double-click on HTTP Redirect



b) Under the ‘HTTP Redirect’ window, check the box ‘Redirect requests to this destination:’ and add the desired URL. In this example we are using ‘http://smp-w2k8-01/Altiris/NS’. If you use SSL, modify the URL to match your certificate. Click ‘Apply’



Note: if you open the IE browser and type ‘http://smp-w2k8-01/Altiris/NS/NS’ for example, it should redirect you to ‘http://smp-w2k8-01/Altiris/Console/Default.aspx’. Any communication requesting to reach ‘…/Altiris/NS/NS/…’ should be now redirected to ‘…/Altiris/NS/…’

If you get an HTTP 500x error trying to redirect, you will need to enable 'Anonymous Authentication' for the new created virtual directory in step 3.

5. Enable the Alternate URL for all client policies so those can use '/Altiris/NS/' as their URL and clean up the bad reference. 
a) Go to the SMP Console>Settings>All Settings>Agents/Plug-ins>Symantec Management Agent>Settings>Symantec Management Agent Settings – Targeted>All Desktop computers (excluding ‘Site Servers’)>Advanced tab and enable ‘Specify an alternate URL…’ option
b) Do the same for any other policy targeting systems, like ‘All Site Servers’ that may be affected.
6. To clean up the bad URL reference for “/altiris/ns/ns/agent/getclientpolicies.aspx”, the NS redirect added in step 4 will not be sufficient in some instances. You may need to remove the bad reference (removing the /NS entry) on the following regkeys: 

HKLM>Software>Altiris>Altiris Agent>Servers>SMPserver.YourDomain.com>Web 
HKLM>Software>Altiris>Express>NS Client>NSs>SMPserver.YourDomain.com>Web 


After that your client machines should start getting their policies. 
After that your client machines should start getting their policies. 
 

You can use the SSETools (HOWTO60787) and under General tab there is an IIS log viewer. Open the IIS logs. Use the Stats button and under URL filter, identify the bad URL entries. You should be able to see all the IP Addresses for all the client machines that are trying to access the bad URL references.


Supplemental Materials

SourceETrack
Value3422812, 3427311


Article URL http://www.symantec.com/docs/TECH214871


Terms of use for this information are found in Legal Notices