Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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?

↑ Back to the top


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.

↑ Back to the top


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.

↑ Back to the top


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'

↑ Back to the top


Status

This behavior is by design.

↑ Back to the top


Keywords: KB318108, kbprb, kbnofix

↑ Back to the top

Article Info
Article ID : 318108
Revision : 5
Created on : 6/4/2003
Published on : 6/4/2003
Exists online : False
Views : 320