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
When you are attempting to compile a BizTalk Orchestration Schedule, you may receive either of the following two messages:
Would you like to debug using the selected debugger?
Microsoft Development Environment
An exception of type 'Runtime Error' was not handled. Would you like to debug the application?
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.
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.
On the Edit menu, click Modify, type 0, and then click OK.
Quit Registry Editor.
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'