How to Debug a Windows Scripting Component That Is Called from an XLANG Schedule

You can use Microsoft BizTalk Server Orchestration Designer to implement schedule ports by using Microsoft Windows Scripting Component (.wsc) components. This article describes how to step through the .wsc script code in a debugger after an XLANG schedule that is running has called the script.

To break into a scripting component that has been called from an XLANG schedule, follow these steps:

1. Enable Microsoft Script Debugger just-in-time (JIT) debugging. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
   269827� PRB: VBScript 'STOP' Statement in .wsc Components Does Not Start Script Debugger When Called from ASP
2. Paste the following line of code at the top of your component code, just before the registration tag.

   <?component error="true" debug="true"?>

3. Put STOP statements in your code where you want the debugger to break in.
4. Install Microsoft Script Debugger.
   
   The following file is available for download from the Microsoft Download Center:
   
   Download the Microsoft Script Debugger package now.
   
   For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
   119591� How to Obtain Microsoft Support Files from Online Services
   Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
5. Verify that the application identity of the XLANG Scheduler COM+ application is set to Interactive User or to the specific account that you will use to log on when you start your debugging session.
6. Stop the XLANG Scheduler COM+ application before you try to debug your scripting component. You may have to repeat this step every time that you want to start a debugging session.
7. You must be logged on to the BizTalk Server console directly to start a debugging session. If you are connected to the BizTalk Server through a Terminal Server session, the debugger will break into the script code at the STOP statement. However, the prompt to start the debugger will only be visible on the BizTalk Server console.
   
   If BizTalk Server is installed on a computer that is running Microsoft Windows XP or Windows Server 2003, you can start a Terminal Server session to the computer that is running BizTalk Server by using the optional /console switch (mstsc.exe /console) to gain access to the BizTalk Server console.