PRB: The Just-In-Time Debugging Message Appears When You Attempt to Compile BizTalk Orchestration Schedule

Article translations Article translations
Article ID: 318108 - View products that this article applies to.
This article was previously published under Q318108
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all

SYMPTOMS

When you are attempting to compile a BizTalk Orchestration Schedule, you may receive either of the following two messages:
Just-In-Time Debugging

Would you like to debug using the selected debugger?
-or-
Microsoft Development Environment

An exception of type 'Runtime Error' was not handled. Would you like to debug the application?

CAUSE

This behavior may occur if the XLANG schedule contains one or more decision shapes and the Just-in-Time debugging script is enabled on the computer on which you are compiling the XLANG schedule.

RESOLUTION

To resolve this behavior, disable the Just-in-Time debugging script. To disable Just-in-Time debugging, make the following modifications to the registry.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Start Registry Editor (Regedt32.exe).
  2. Locate the following key in the registry:
    [HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings]"JITDebug"
  3. On the Edit menu, click Modify, type 0, and then click OK.
  4. Quit Registry Editor.

MORE INFORMATION

The error condition that is discussed in this article may cause you to receive an error message similar to the following when you try to run the Buyer1 XLANG Orchestration schedule from the BizTalk Server 2002 tutorial:
Microsoft VBScript runtime error: Object required: 'POReq'

STATUS

This behavior is by design.

Properties

Article ID: 318108 - Last Review: June 4, 2003 - Revision: 3.2
APPLIES TO
  • Microsoft BizTalk Server 2000 Standard Edition
  • Microsoft BizTalk Server 2002 Standard Edition
Keywords: 
kbnofix kbprb KB318108

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com