Win Server 2003 - IIS

I have been receiving Internal Server Errors (Message 500) periodically for a few different applications that are running on a Windows 2003 server. It must crash IIS because it affects other applications on that same server. (I receive that same error when I try to access other apps on the server)

I asked my web host about this and they told me that it's an across the board Microsoft bug with Windows 2003 and using ODBC connections to a database, such as Access. It becomes unstable and crashes IIS. Has anyone heard of this Microsoft bug or know what can be done to correct this? It's not good having IIS crash and bring down all the applications on the server. To restore the applications, IIS has to be manually restarted on the server.

It's difficult to determine why it would keep crashing. What sort of applications do you have there? Anything involving COM? :D :D

Take a look at this too:

http://www.microsoft.com/downloads/d...DisplayLang=en

I've found IIS quite unreliable in a shared hosting environment. Very often applications pull down the entire IIS or ASP process.

Thanks for the posts guys.

No, I'm not running any COM objects. It's straight VBScript for these applications. The one application is a very well known shopping cart (which does not use COM objects unlike many of them). The other one is a dynamic calendar application. Both of these apps use an Access database.

It's just really strange the way it works. I'll be browsing through the calendar and then all of a sudden it will quit working. So, then I'll look at the other website on that same server and the shopping cart on it quits working as well (due to IIS crashing).

Check your error logs after the crash occurs. There should be a clue there.

When looking at the log file, I see "Unspecified_error 500" during the time it occurred. I thought it would tell me more than that. Since it's a hosting account, I don't have full access to the server.