global.asa on remote machine causing application restart?
From: Steve Browning (usenet_at_sbrowning.com)
Date: 06/07/04
- Next message: Egbert Nierop \(MVP for IIS\): "Re: IIS is going crazy"
- Previous message: Aron P: "Re: Accessing 32 bit COM components in 64 bit IIS"
- Messages sorted by: [ date ] [ thread ]
Date: 7 Jun 2004 06:16:50 -0700
I have a website (win2k server, iis5) that is experiencing the 'HTTP
Error 500-12 Application Restarting' problem. According the microsoft,
virus scanner can be causing this. (Microsoft Knowledge Base Article
- 248013). We do have a global.asa file.
We have excluded global.asa from the virus scan, but it hasn't fixed
the problem.
The twist in our case is that the content for the website is not
located on the webserver itself, but on a share located on another
computer (the Home Directory tab, share located on another computer
radio button). We have turned off virus scanning both on the webserver
and the other computer which hosts the content with no result.
As a test, I moved all the content local to the webserver and changed
the Home Directory properties, and immediately the problem went away.
So, it appears having global.asa hosted on a another machine is
causing IIS to think it is being changed every few minutes, and IIS is
restarting the application.
But, we really need to keep the content on another host, since we will
have multiple webservers accessing the same content files.
Does anyone know why this is, or how to fix it? Is there a way to have
global.asa local but all other content remote? TIA...
- Next message: Egbert Nierop \(MVP for IIS\): "Re: IIS is going crazy"
- Previous message: Aron P: "Re: Accessing 32 bit COM components in 64 bit IIS"
- Messages sorted by: [ date ] [ thread ]