So far all seems right (and it works on IIS6 since ever).Ībout the "404" again: I strongly assume it belongs to a security setting, because the same web exception could happen on IIS6 if the permissions are not set properly:īut the management UI has totally changed - as I wrote in my opening post - I dont know where to look for a similar security setting, besides the one I found in the advanced AppPool settings (see above) and have already set to the least secure setting %windir%\Microsoft.NET\Framework\v7\aspnet_isapi.dllĪs you mentioned I check the "Request Restrictions" - the checkbox is unchecked. NET AppPool" and the *rem handler is set to (this is similar to check if file exists). Make sure it's mapped correctly to aspnet_isapi.dll and under "Request Restrictions" the checkbox called "Invoke handler only if request is mapped to:" is UNCHECKED. Can you please look at the handler mappings for *.REM - specifically for the vdir or site where your remoting application reside?
0 kommentar(er)
