Server.CreateObject failed on Windows 2003.
Posted on 2005-04-26
We have a web application that consists of ASP pages that instantiate an ATL COM Object to communicate with a Server application. In our testing this is working great. However, when it is deployed to the client server PC, which is running Windows 2003, it runs for a while and then the web server eventually crashes. The nature of the failure is inconsistent -- sometimes the web server will simply stop responding and other times it will generate a message stating that Server.CreateObject failed (I'm waiting for the next failure to get the specific syntax of the error). An "iisreset" command resurrects the application for a while but eventually it fails again. Originally I thought this was due to a memory leak in our COM Object. However, I've left it running for many hours on a Windows XP machine with multiple browsers running and making calls every few seconds. TaskInfo indicates that memory usage is remaining unchanged and the application continues to respond even after 12 hours of usage. It appears that the problem is environmental with the Windows Server 2003 machine. I did find information on Microsoft.com regarding ASP/COM memory leaks but the hotfix that they prescribed is rolled into Service Pack 1, which is installed at the client site. So I'm stumped. Any advice is appreciated.