Posted to
Troubleshooting
by
dblount
on
04-07-2008, 6:31 PM
I came across this error today after restarting one of my production web servers. The issue only appeared when ASP.NET was initializing on the first request from a web browser. If you requested the website a second time, the application would finally kick-in and start. However, if you restarted the W3SVC service (effectively reloading IIS and ...