HTML Script Application
You might experience the
following problems when trying to launch an HTML Script Application debug
session:
- A persistent "Error creating debug target" message.
- When trying to attach to an existing browser for debug, the debugger is
unable to obtain a list of running browsers.
To correct these problems, complete the following steps:
- Close all running browsers and Microsoft® Windows® Explorer windows before trying
to start another debug session.
- If the previous 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.
When trying to attach to an existing browser for debug, do not attempt
to attach to the WebSphere® Studio workbench internal browser. Attaching
to the internal browser for debug will cause your workbench to stop responding
and unexpected results might occur.
You might experience the following
problems during an HTML Script Application debug session:
- The current location is not highlighted in the editor when the debug session
is suspended.
- Breakpoints cannot be installed.
- Source is not available for display if the source is located outside of
the workbench workspace.
You can correct these problems by completing one of the following tasks:
- The browser might not be loading the page properly. Refresh the page in Microsoft Internet
Explorer (you might need to refresh the page several times).
- If refreshing the page does not correct the problem, terminate the debug
session. Close all running browsers and file explorers, and then restart the
debug session.
- If the previous step does not solve the problem, the mdm.exe process
is corrupted. Terminate the debug session, all running browsers and file explorers.
Then terminate mdm.exe from the Windows Task
Manager and restart debug session.
Having the workbench Help window or internal browser opened during
an Active Script debug session might interfere with the debug session and
result in unexpected behavior. Some editors and views, like the Page Designer
Editor and the Java™ Script Editor, have preview panes which also use
the internal browser. Do not use these editors during an Active Script debug
session - if they are used, do not open the preview pane.
Breakpoints
set before a debug session are ignored if the page is deployed onto a server.
To set a breakpoint, suspend the debug session to bring up the source and
set the breakpoint at that temporary page. Refer to Setting
a line breakpoint for details.
The Active Script debugger makes
use of the Microsoft Script debugger to obtain debug information.
For additional issues related to Microsoft Script debugger, refer to
its ReadMe.htm.
Breakpoints can be added for a file with a *.js extension
only if the file resides in the workspace. You cannot set breakpoints in *.js
files if they do not reside in the workspace.
Breakpoints cannot be
added for a file with a *.js extension if you have started the debug session
by way of Debug on Server.
Script Host Application
You might experience the
following problem when trying to launch a Script Host Application debug session:
- A persistent "Error creating debug target" message.
You can correct this problem by doing the following:
- Close all running browsers and Microsoft Windows Explorer windows before trying
to start another debug session.
- If the previous 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.
- When adding a breakpoint for a VisualBasic script file (files with *.vbs
extension), two breakpoints will be added for each line breakpoint that is
set. The second breakpoint will have no effect during a debug session and
can safely be ignored.