PRB: MsgBox Function in WSC Component May Cause an XLANG Schedule to Appear as Though It Has Stopped Responding (830489)
The information in this article applies to:
- Microsoft BizTalk Server 2002
- Microsoft BizTalk Server 2000
SYMPTOMSYou can use Microsoft BizTalk Server Orchestration Designer to
implement schedule ports by using Microsoft Windows Scripting Component (.wsc)
components. However, if you start an XLANG schedule that calls a .wsc file that uses the
Microsoft Visual Basic Scripting Edition (VBScript) MsgBox function, the schedule may appear to have stopped responding. CAUSEThis problem may occur if the application identity of the XLANG Scheduler COM+
application is not set to Interactive User.RESOLUTIONVerify that the application identity of the XLANG Scheduler COM+
application is set to Interactive User.STATUS This
behavior is by design.MORE INFORMATIONWhen the application identity of the XLANG Scheduler COM+
application is set to something other than Interactive User, and you start an XLANG schedule that calls a
.wsc file that uses the VBScript MsgBox function, the MsgBox function fires correctly. However, the resultant message box is not visible. When this
problem occurs, you cannot click anything that is in the message box. Therefore, the script
component cannot continue to run and the schedule appears to have stopped responding.
| Modification Type: | Major | Last Reviewed: | 10/9/2003 |
|---|
| Keywords: | kbprb KB830489 kbAudDeveloper |
|---|
|