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?)