Active Script Debugger

The Active Script debugger enables you to detect and diagnose errors in embedded client-side scripts from a Web page (*.htm, *.html or *.jsp) displayed by Microsoft(R) Internet Explorer. The Active Script debugger also hosts and allows you to debug stand-alone scripts with *.vbs or *.js file extensions. With the plug-ins, you can control the execution of the script by setting line breakpoints, suspending launches, stepping through your code, and examining and changing the contents of variables.

The Active Script debugger requires installation of the Microsoft Windows(R) Script Debugger, which can be found at http://msdn.microsoft.com/library/default.asp (select Web Development > Scripting > Downloads from the table of contents in the left-hand frame and then, in the resulting page, select the link to the Microsoft Windows Script Debugger).

Known problems and workarounds

HTML Script Application

You may experience the following problems when trying to launch an HTML Script Application debugging session:

• A persistent "Error creating debug target" message.
• When trying to attach to an existing browser for debugging, the debugger is unable to obtain a list of running browsers.

You may correct these problems by doing the following:

1. Close all running browsers and Microsoft Windows Explorer windows before trying to start another debugging session.
2. If the above step does not solve the problem, the mdm.exe process is corrupted. Close all running browsers and file explorers, and then terminate mdm.exe from the Windows Task Manager. Restart the debug session.
3. When trying to attach to an existing browser for debugging, do not attempt to attach to the WebSphere Studio workbench internal browser. Attaching to the internal browser for debugging will cause your workbench to stop responding and unexpected results may occur.

You may experience the following problems during an HTML Script Application debugging session:

• The current location is not highlighted in the editor when the debugging session is suspended.
• Breakpoints cannot be installed.
• Source is not available for display if the source is located outside of the workbench workspace.

You may correct these problems by doing the following:

1. The browser may not be loading the page properly. Refresh the page in Microsoft Internet Explorer (you may need to do this several times).
2. If refreshing the page does not correct the problem, terminate the debugging session. Close all running browsers and file explorers, and then restart the debugging session.
3. If the above step does not solve the problem, the mdm.exe process is corrupted. Terminate the debugging session, all running browsers and file explorers. Then terminate mdm.exe from the Windows Task Manager and restart the debugging session.

Script Host Application

You may experience the following problem when trying to launch a Script Host Application debugging session:

• A persistent "Error creating debug target" message.

You may correct this problem by doing the following:

1. Close all running browsers and Microsoft Windows Explorer windows before trying to start another debugging session.
2. If the above step does not solve the problem, the mdm.exe process is corrupted. Close all running browsers and file explorers, and then, terminate mdm.exe from the Windows Task Manager. Restart the debugging session.

The debugger is not able to launch a script with a compiling error. A launch may be created in the Debug view, but there will be no thread or debugging target under that launch. Ensure that you manually terminate and remove this unsuccessful launch. Otherwise, it may interfere with subsequent debugging sessions.