ASP Locking Up

Hi guys

Whilst I'm searching google on this, I thought I'd ask the question here anyway - it doesn't already seem to have been asked.

[If google returns the solution, of course, I'll post it here]

I'm using IIS6 on W2003 Standard edition.  However, I was running IIS4 last week with the same problem so I suppose it's not version specific.  The server, BTW, has plenty of capacity (without going in to detail).

Every now and again, ASP just seems to stop working on the server.  Any page that runs an ASP script will not show in the browser and no error will be displayed.  I just get a timer bar waiting for the page to load.  No errors seem to be written to the Windows or IIS logs about this.  It is always cured by simply restarting the WWW service and then ASP starts working again.  When it's working, everything works great.

Any ideas how I can investigate where the problem lays?  Any good ASP monitoring tools / techniques I could use.

Thanks for any hints.

Gareth

Thanks for replying.

I'm almost certain it's my code - it must be.  But, what code?  All the pages that run run fine unless the problem has occurred.  Running the common pages, even under heavy use, doesn't trigger the problem.  It just seems to happen.

It doesn't happen during the weekends or of an evening though when there's very light use.  But some times I can have over 400 people connected and there's no problem, sometimes 200 people and there is a problem.  I'm perplexed.

The reason I'm not getting very far with google is because I don't know quite what I'm looking for (no error codes!).

Thanks

Gareth

@MorningZ

It would be very handy to know exactly what the code was that was causing the error so I can see if I have it anywhere.  I know I've used the ASP replace() command extensively throughout my apps but testing always seem to show no problems.

I'm experimenting with the Web Application Stress tool and hopefully this will help track it down.

Could it be due to my heavy use of Access databases?  I have several databases and several connections to each loading on the home page of the site (heavy traffic).  Or would you expect to see a specific error if it was related to db access.

I really need this sorting as I'll be leaving my current job soon and don't want to leave my replacement with the problem of fixing some unknown portions of my code.