HostOnNet.com

admin · Site Admin Joined: 23 Jan 2003 Posts: 256 Location: India

This happens at times when using a global.asa in ASP application. But it happens randomly.

For more info see:

http://support.microsoft.com/default.aspx?scid=kb;en-us;248013&Product=iis50
http://support.microsoft.com/default.aspx?scid=kb;EN-US;248013

Quote:

"When you save changes to the Global.asa file, the server finishes processing all of the current application requests before it recompiles the Global.asa file. During that time, the server refuses additional requests and returns an error message stating that the request cannot be processed while the Web site is restarting. "

And yes, these problems were happening right after I made a change to the script in global.asa. The ASP engine recognizes this. The 'old' global.asa is used until all other sessions are abandoned, and the app ends. Since the file has been changed, global.asa is re-compiled on the next time the applicaiton starts. This can cause the 500-12 HTTP error.

I am using a session variable to hold the connection string in my app. The argument of using session variables at all is out of the scope of this post. But I don't think they should be avoided, especially when you know your IIS administrator by first name.

Session variables are powerful, and they work great on dedicated servers (not shared server) and with intranet apps that see a limited amount of concurrent users (under 50).
_________________
HostOnNet.com - Reseller Hosting
Free Ads Forum, Promote your site
NetFreeHost.com - Free Web Hosting, phpBB Hosting