Contents tagged with IIS6
-
ASP 500 Error and Error Code 0x800700aa when browsing a simple .asp page
I recently helped a customer with an issue where ASP pages would not execute and returned the following error page:
-
“Parser Error Message: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.” when .net page has debug=”true”
Recently, I came across an issue where the customer faced an FIPS (Federal Information Processing Standards) related error on the .aspx pages which had debug=”true”. His ASP.net application was hosted on IIS7 running on Windows Server 2008 SP2. And, he was able to reproduce the issue using a very simple page. The error message was:
-
Troubleshooting HTTP 401.3 errors with Process Monitor
Last week I posted the following blog which showed how to use Process Monitor to troubleshoot service startup issues.
-
Troubleshooting service startup issues with Process Monitor
Many things can cause a service, like IIS’s World Wide Web Publishing Service, to fail on startup. When troubleshooting such an issue, Process Monitor can be an invaluable tool. What Process Monitor does is monitor all File and Registry access on the system in real-time. The latest version of process monitor can be obtained here.
-
How To View what ASP.NET Requests are doing at runtime on IIS 6.0
This is just a quick blog to mention a forgotten tool. The managed stack explorer can be run on an IIS 6.0 Server running ASP.NET 2.0 to investigate the managed call stacks. Looking at the call stacks when an ASP.NET application is not responding may help identify what the requests are doing.
-
Troubleshooting HTTP Compression in IIS 6.0
Cross-posted from http://blogs.msdn.com/mike