IIS Issue?

Topic

New Reply

So, I’ve been having this problem with our client’s server for quite some time, now. Here’s how it goes.

We recently developed an ASP app for them. It uses ADO and an ODBC data source to hit an Access DB.
The app works FINE on both our NT4 and Win2k development boxes.

HTML also works fine. However, after any asp data access occurs, you lose IIS (altogether, it no longer renders or returns anything… html or asp.)
The production server is NT4 – SP6a, MDAC 2.6SP1. The symptoms are: IIS no longer responds, and will not respond until after a reboot (trying to stop and restart the service puts it in a state where it is forever trying to stop w3svc).

We suggested that the client totally rebuild the machine… which they did, to no avail. Now I have to start asking… is there ANY possibility that this is hardware related? We’re running a full RAM test on the box this afternoon. Does anyone have any other ideas? (NT4, IIS, ASP, Hardware, or otherwise?)

Thanks,
– Lynn

Reply | Quote

Replies

Do you have any custom components in your web? We’ve seen IIS hang mostly on external components called from ASP.
Have permissions changed? Is the account that the web runs under the same in both environments?

Reply | Quote

No custom components… Like I said, brand new server install. This app doesn’t use any COM objects either (it’s strictly vbscript.)
I don’t think the permissions have changed. Especially since the server has been rebuilt. I’m fairly certain that IUSR_MACHINENAME is running the service, but I can double check on that.

This server doesn’t even host any other web content.

Reply | Quote

Is there a VirusScanner on the web server? We’ve seen the heuristic scanning in McAfee’s NetShield kill the ASP scripts. NAV is also known to cause problems when running on a web server with ASP.

Reply | Quote