« Previous Next »

• 03-19-2009, 3:57 AM

  Metek Joined on 10-06-2008, 2:38 PM Posts 10

  Microsoft Script debugger doesn't catch on Server Reply Contact 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, Al

  Tags: Script Debug

• 03-19-2009, 4:57 PM

  In reply to

  Madness80 Joined on 06-19-2007, 1:17 PM Posts 75	Re: Microsoft Script debugger doesn't catch on Server Reply Contact Try using Visual Web Developer Express. http://www.microsoft.com/express/vwd/

• 03-20-2009, 8:11 AM

  In reply to

  Metek Joined on 10-06-2008, 2:38 PM Posts 10	Re: Microsoft Script debugger doesn't catch on Server Reply Contact 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, Al

• 03-24-2009, 5:59 AM

  In reply to

  Leo Tang - MSFT Joined on 12-12-2008, 2:47 AM Posts 930

  Re: Microsoft Script debugger doesn't catch on Server Reply Contact 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. Leo Tang Microsoft Online Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help.

• 03-25-2009, 10:47 AM

  In reply to

  Bjorn S Joined on 03-25-2009, 9:25 AM Posts 5

  Re: Microsoft Script debugger doesn't catch on Server Reply Contact 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.

• 03-30-2009, 5:38 AM

  In reply to

  Metek Joined on 10-06-2008, 2:38 PM Posts 10	Re: Microsoft Script debugger doesn't catch on Server Reply Contact 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?

• 03-30-2009, 5:41 AM

  In reply to

  Metek Joined on 10-06-2008, 2:38 PM Posts 10	Re: Microsoft Script debugger doesn't catch on Server Reply Contact 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?

• 03-31-2009, 10:07 AM

  In reply to

  Leo Tang - MSFT Joined on 12-12-2008, 2:47 AM Posts 930

  Re: Microsoft Script debugger doesn't catch on Server Reply Contact 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? Leo Tang Microsoft Online Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help.

• 03-31-2009, 4:27 PM

  In reply to

  Metek Joined on 10-06-2008, 2:38 PM Posts 10

  Re: Microsoft Script debugger doesn't catch on Server Reply Contact 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?