IIS7 - Classic ASP

Re: Microsoft Script debugger doesn't catch on Server

Metek — Tue, 31 Mar 2009 20:27:07 GMT

Hi Leo,

To be open, I would like to avoid installing VS2008 on the server for do not compromise server security. Yes, I can try it, if there is no other way to figure out what's wrong. Is there any other way?

Also, could you please tell me: is it enough if I'm enabling server/client debug on the virtual directory? Or should I do it WEB-site wide or even server-wide?

Re: Microsoft Script debugger doesn't catch on Server

Leo Tang - MSFT — Tue, 31 Mar 2009 14:07:20 GMT

Hi,

The first request will active a w3wp.exe process. Since you have enabled Client-side/Server-side Debugging in ASP debugging properties, the response should contains debugging information.

Could you check if you can debug on the local server machine?

Re: Microsoft Script debugger doesn't catch on Server

Metek — Mon, 30 Mar 2009 09:41:25 GMT

Bjorn,

Thank you. I'm using Stop, of course. In my experience division by 0 is not worst to break in debugguer. I assumes, that something in IIS server settings may prevent debugger, but what ir could be?

Re: Microsoft Script debugger doesn't catch on Server

Metek — Mon, 30 Mar 2009 09:38:24 GMT

Leo,

Thank you for your reply. Yes, SP1 is installed on client PC.

I do not see w3wp.exe process on the WEB server PC at all.

So, inside of which process scripts are running?

Which settings (except Enable Client-side/Server-side Debugging in ASP properties) may prevent debugging?

Re: Microsoft Script debugger doesn't catch on Server

Bjorn S — Wed, 25 Mar 2009 14:47:09 GMT

You can force a dialog where you will be asked which debugger you would like to choose by entering Stop in the ASP-page at a row right before where you want to start debugging. That invokes the debugger (this is of course only for testing purposes and should be removed after the test is finished).

That way you don't have to worry about which process that is the current one.

Re: Microsoft Script debugger doesn't catch on Server

Leo Tang - MSFT — Tue, 24 Mar 2009 09:59:52 GMT

Hi,

Have you installed Visual Studio 2008 Service Pack 1(SP1)? Classic ASP support is only available in SP1. Also, the work process is w3wp.exe process. Hence, we should attach to the w3wp.exe process.

As far as I know, the Script Debugger is deprecated unless a new version release.

Re: Microsoft Script debugger doesn't catch on Server

Metek — Fri, 20 Mar 2009 12:11:38 GMT

Hi Madness80

Thank you for your reply.

I downloaded and installed on the server. Then started Remote Debug Monitor and connected from Visual Studio 2008 to InetMgr process. It doesn't catch division by 0 in script either. Did I connected to wrong process? Why MS Script debugger doesn't work?

Thank you in advance,

Re: Microsoft Script debugger doesn't catch on Server

Madness80 — Thu, 19 Mar 2009 20:57:40 GMT

Try using Visual Web Developer Express. http://www.microsoft.com/express/vwd/

Microsoft Script debugger doesn't catch on Server

Metek — Thu, 19 Mar 2009 07:57:45 GMT

Hello,

I'm using IIS 7.0 on top of Windows 2008 Server x64. I need debug ASP page written on VBScript (server side script). I installed MS Script debugger and enabled Server side debug in ASP applet (I tried enable it for Virtual Directory, Site-wide and Server-wide).

I added division by 0 operation into the script. However when exception occurs, server logs it into Failed request Log, but script debugger doesn't catch it.

What is missing in my setup?

Thank you in advance,