Windows Script Debugger Is Not Started If Windows Script Host Detects a Script Error (234063)


The information in this article applies to:

  • Microsoft Windows 2000 Server
This article was previously published under Q234063

SUMMARY

When Windows Script Host finds an error in a script, it displays an error message instead of loading the Windows Scripting Debugger and displaying the error in the text file.

MORE INFORMATION

In Windows 2000, the Windows Scripting Debugger is not started by default when a script error is detected. You can debug the error by setting a temporary switch for the Windows Script Host. At a command prompt, type the following line

wscript bad_script_name.xxx //X

where bad_script_name.xxx is the script file name and //X is a switch that starts the debugger.

Typing wscript /? displays the syntax for Wscript.exe and the available options.
Modification Type:MajorLast Reviewed:10/9/2002
Keywords:kbinfo kbui KB234063
©2002 Microsoft Corporation. All rights reserved.