| Cause | Issue occurs because of missing Handler Mappings in IIS that need to be added.
The user did not see an error, but the w3wp log file contains the following exception:
<ApplicationData>
<TraceData>
<DataItem>
<TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
<TraceIdentifier>Archer.Web</TraceIdentifier>
<LogReferenceId>040416-131411-0671</LogReferenceId>
<Description>The file '/RSAarcher/ArcherAsyncUploadHandler.ashx' does not exist.</Description>
<AppDomain>/LM/W3SVC/1/ROOT/RSAarcher-1-131042445675616158</AppDomain>
<ContextData>
<BaseUrl>https://ARCHERWEB/RSAarcher/ArcherAsyncUploadHandler.ashx</BaseUrl>
<type>rau</type>
</ContextData>
<Exception>
<ExceptionType>System.Web.HttpException, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a</ExceptionType>
<Message>The file '/RSAarcher/ashx.ashx' does not exist.</Message>
<Source>System.Web</Source>
<StackTrace>
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate)
at System.Web.UI.SimpleHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
</StackTrace>
</Exception>
</TraceRecord>
</DataItem>
</TraceData>
</ApplicationData>
|
| Resolution | Check if the "ArcherAsyncUploadHandler" IIS Handler Mapping exists:
- From IIS Manager, select the Archer web site
- In the middle pane, open Handler Mappings
- Review the list of Handler Mappings. Notice ArcherAsyncUploadHandler.ashx is not visible in the list:
How to add the Managed Handler: - From Handler Mappings in the Actions pane, click Add Managed Handler.
- From the Managed Handler window, enter the following info:
Request Path: ArcherAsyncUploadHandler.ashx
Type: ArcherTech.Web.HttpHandlers.RadUploadHandlers.ArcherAsyncUploadHandler
Name: ArcherAsyncUploadHandler - Click the Request Restrictions button and verify these selections:
- Mapping tab - Invoke handler option is not enabled.
- Verbs tab - All Verbs option is selected
- Access tab - Script option is selected
- When complete, select OK.
- Verify the Handler Mapping is enabled and perform an IISRESET.
|
on Oct 5, 2016
