The Orchestration Debugger timed out waiting for a response from the orchestration runtime. This may occur if the orchestration instance is not in Breakpoint or if the BizTalk host is stopped. Use the Operations views to check the state of the Orchestration instance. Use the BizTalk Server Administration tool to check the status of the host.
The orchestration cannot be found. It may have been deleted or renamed. The call orchestration's configuration will be lost. ...
The orchestration cannot be found. It may have been deleted or renamed. The start orchestration's configuration will be lost. ...
The orchestration cannot be started because it is dependent (uses Call or Start) on other orchestrations that have not been ...
The orchestration cannot be stopped because there are other orchestrations which depend on it (using Call or Start) that ...
The Orchestration Debugger timed out waiting for a response from the orchestration runtime. This may occur if the orchestration ...
The Orchestration Designer for Business Analysts requires Automation Events be turned on. To turn on Automation Events: 1. ...
The orchestrations in assembly "{0}" are compatible with previously deployed assembly versions. The names and count of orchestrations, ...
The orchestrations listed are included in the assemblies available to this application. You must specify a host that will ...
The ordered delivery send port %1 has stopped processing messages due to an unknown error. This can usually happen if there ...