iis 7 - Classic ASP on IIS7: refusing to send errors to browser on 500... Respect! If you first select you ASP web side by clicking on it and then start doing the above changes - you will make those changes on the web site level what For this error, we can run Process Monitor OR use Failed Request Tracing to get the Directory name where it fails. this contact form
The real problem we had was that webDAV authoring rules was added at both website and virtual directory. I can't really imagine myself coming up with a solution to this issue. WebDAV authoring rules can not be set on both Website and virtual directory. I've been reading your web site for a long time now and finally got the bravery to go ahead and give you a shout out from Austin Tx! his explanation
You can find the detailed instructions here *************************************** Scenario 1 Error Message: HTTP Error 500.19 - Internal Server Error Description: The requested page cannot be accessed because the related configuration data Can you try collecting the ETW traces using the instructions at http://tomasz.janczuk.org/2011/09/using-event-tracing-for-windows-to.html? share|improve this answer answered May 22 '14 at 2:29 user3663167 111 add a comment| up vote 0 down vote Something to note on this in the future is when you code Config File \\?\C:\inetpub\wwwroot\web.config Requested URL http://localhost:8081/ Physical Path C:\inetpub\wwwroot\ Logon Method Not yet determined Logon User Not yet determined Config Source 144: 145:
If it’s a UNC share, you need to either run your app-pool as an account that has sufficient permission to the UNC share or configure the virtual directory with a user There is a problem with the resource you are looking for, and it cannot be displayed. So far as I can deduce, A webdav request is all http PUT or DELETE requests as far as IIS is concerned, even if you have removed the webdav handler from There Is A Problem With The Resource You Are Looking For And It Cannot Be Displayed. Iis This is just how it is.
Reply Said says: September 15, 2011 at 4:35 am Thanks a lot. Sounds like a IIS issue. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false". But if Microsoft ever fixes IIS, we will start working automagically. -->