IIS Service keeps stopping

[brad10]

We are running IIS on NT4 and just lately the service keeps stopping at random intervals. I just maintain a fairly small intranet on it - this is all that's on it.

Our IT Dept are putting the blame on my 'sloppy asp code' however the site has been working fine for a number of years with the same asp code - and all asp pages seem to work without error.

I'm told from elsewhere that bad asp code wouldn't stop the service as it's run in a different memory address to the IIS Service and therefore not connected and it's more likely to be server issues - can anyone clarify this and save me from taking the rap for this.

 

[brad10]

Does anyone out there know if this is right?

Can an error in asp code keep stopping the iis service? Is this correct - bad asp code wouldn't stop the service as it's run in a different memory address to the IIS Service and therefore not connected - it's more likely to be server issues.

Can someone confirm or deny?

 

[skurpyun]

Brad10,
I can neither confirm nor deny ASP being able to shut down IIS. But, from one experience I had, I know that a global.asa file written in VBScript had cause my companies IIS to run extremely slow (eventually leading to it basically shutting down) because there was a very simple mistake in the code that nobody noticed.

But since your code had been running fine previously wihtout any hitches, I would say that there is a server problem that's causing IIS to shut down. Were there any recent intalls? new programmes? new DLLs? anything new on the server that might be conflicting with IIS? Also, can the IIS support unlimited connections? or just 10 connections? I ask this since you said it was a small intranet site, you might be running it from an IIS that does not have the license to support a lot of connections (thank microsoft for that one!).

-skurpyun

 

[brad10]

Is there an easy way to tell how many connections our IIS can support. Apologies for the lack of knowledge.