IIS 6.0 Slowing down

Hi,

My company is having problem with the intranet lately. The response time of the access to the default page is unacceptably slow.
The response time is back to normal when we reset the IIS. It can happen 3 - 4 times a day and every now and then i have to reset the IIS. I have been trying to observe the available logs and performance monitor. There's nothing wrong with them. At the same time, my company is implementing the Active Directory, so I suspect that the authentication might be an issue here. I tried to allow annonymous access to the page ( previously, the option is not checked). It didnt help. The slowing down problem still happen. Then we moved the intranet to new server. The problem is not fixed either..can anyone give me a hint what to do?

many thanks

if you have AntiVirus program on the server, disable its Script Blocking ability - for Norton AntiVirus right click its icon in the task bar --> Configure --> Script Blocking and restart your server. if you have Panda remove it from the server, it kills all ASP related code. the Norton only kills IIS when it's executing File System related code, as it identifies it as malicious code. (no, Microsoft and Symantec are not friends)

From your description it sounds like you have some kind of coding problem that's causing the server to run out of resources over time (leaks). I doubt it's an antivirus issue since your site does work for some time before it quits.

Review any server code in your pages and make sure you destroy objects your code creates.

Are you by any chance using an access db in any asp code? If so look around any server code that uses the mdb very carefully

Norton kills IIS only when it executes FSO code... maybe he has page with such code, so only when someone access this page the server would crash.

What I've seen with Norton script blocking can cause a page to hang, but not to slowly crash. Usually script blocking causes any asp page to just hang, not always just fso pages.

I once had this problem also - all pages worked fine, until I executed page with FSO code - the page has frozen, and so all other pages after that. maybe different antivirus programs or different versions kills IIS in different manners.

Doug,
You re right. We re using alot of access database.
I will check the code..
BTW, if the code is causing the server to run out the resource, the perfmon should indicate that..shoudnt it?

but from my observation, the perfmon indicates that the memor & processor usages are normal...
are there other counters that I should check?

rgds

I don't know what other counters might be helpful, maybe some asp counters like connections, etc. I don't even know if there are ADO counters.

There is some third-party IIS ADO monitor program out there that will let you know what code is connecting to what db's.

This page offers good guidlines for looking over your code

http://msdn.microsoft.com/library/d...tml/ASPtips.asp