Home/ Questions/Q 8461049
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T13:46:21+00:00

I am supporting an application written in classic ASP with IIS 6.0 on Windows

  • 0

I am supporting an application written in classic ASP with IIS 6.0 on Windows Server 2003. I have NO priviledges to add or configure any of the software on this purely development use server, so I cannot install any 3rd party tools. I have requested and requested Visual Studio, but the system admin is old school and says we don’t need that for classic ASP development. So… we’re stuck with Notepad and IE 7.

The sys admin says that both client-side and server-side debugging is turned on in IIS and that IIS was restarted after the change. However, I can’t get any response from the script debugger when I insert a stop statement or a 1/0 expression. (I do get appropriate error messages on the page – just no debugger.)

I have both checkboxes cleared in Internet Options/Advanced so IE and Other debugging will be allowed.

What else do I need? What am I missing? Maybe the script debugger isn’t installed? How can I tell?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You are going to have to modify the script to output your own debug information to the browser.

    You can’t STOP server-side code using this technique, but you can spit out the value of any data to variables you think are relevant to solving the problem. If you’re worried about users seeing the debug code you can wrap the output in HTML comments <!-- ... --> and view the page srouce.

    • 0