Classic ASP debugging tools or system?

We have a third-party application that was written in classic asp.
Every once in a while, the application causes the server to stay at 100% CPU Usage. Requiring a reboot.

How can I pin point the problem? What tools can I use?

I could ask the users what they were doing at the moment, but it's too many of them, and it would be hard to identify who caused the expensive operation on the servers CPU.

Any help or ideas is greatly appreciated.
silentthread2kSenior Software EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

HainKurtSr. System AnalystCommented:
open the asp code
put

debugger;
or
stop

in IIS, enable asp debugging... also IE, tools->internet options->advanced->uncheck "disable script debug for ie"

now browse the page, it will ask for debugger , choose what is available on your pc
visual studio 2000, vs 2005, vs 2008... script debugger...

also use fiddler to debug response-requests
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.