I believe the script debugger is handled by the IE groups, but I cannot confirm that. Haven't heard of anybody having issues with it
before.
Thank you. I hope this information is helpful.
Tim Coffey [MSFT]
This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft
Corporation. All rights reserved.
--------------------
| Content-Class: urn:content-classes:message
| From: "JT New Mexico" <Richie RemoveThis @Zianet.com>
| Sender: "JT New Mexico" <Richie RemoveThis @Zianet.com>
| Subject: Script Debugger
| Date: Thu, 4 Sep 2003 13:02:00 -0700
| Lines: 13
| Message-ID: <226201c3731f$6734a670$a601280a@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNzH2c01rUYN/jcQlqaamxuAXdJOw==
| Newsgroups: microsoft.public.inetserver.iis
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:273957
| NNTP-Posting-Host: TK2MSFTNGXA14 10.40.1.166
| X-Tomcat-NG: microsoft.public.inetserver.iis
|
| I develop mostly ASP application and have used the
| debugging flags to trouble shoot problems. Recently the
| debugging flags stopped functioning. With the script
| debugger and debugging flags on I can run a page with an
| error but the script debugger does not catch the problem
| and display the break point. I've reinstalled the
| debugger and I'm up to date with all the security
| patches. Is anyone else experiencing this or have an
| idea where to turn next?
|
| Windows Server 2000 SP4
| IIS 5.0
| IE 6
|
>> Stay informed about: Script Debugger