Unenlist action for Orchestrations
Discover how you can use the web-based administration console (Web Client) of Nodinite to Unenlist BizTalk Server Orchestrations. Take control of your integration environment with just a few clicks!

Animated walkthrough: from Enlisted (Warning), Unenlist turns the Orchestration Error, and Enlist brings it back to Enlisted (Warning).
From Monitor Views where you have access and where BizTalk Orchestrations are included and Remote Actions are allowed, you can use the Nodinite Web Client to Unenlist selected BizTalk Server Orchestrations.
To Unenlist the Orchestration, press the Action button menu item.
An Unenlisted Orchestration can be Enlisted, Stopped, or Started. You no longer need to use the BizTalk Server Administration Console (MMC) for this administrative task—Nodinite makes it simple and secure.
Warning
Unenlisted orchestrations may miss processing jobs since they are not actively subscribing and will not process any messages.
New 6.4.2 Unenlist is the only action that removes the subscriptions. Stop keeps the Orchestration enlisted, so messages queue until it is started again. Before BizTalk Monitoring Agent 6.4.2, Stop did the same as Unenlist.
How do I Unenlist an Orchestration?
With Nodinite, you have several options to Unenlist Orchestrations:
- Use the Action button menu item Unenlist (as described on this page)
- Use the Unenlist button available from within the Details modal
- Use the Auto Healing feature for automated control—use with care!
To Unenlist a BizTalk Server Orchestration, press the Action button menu item on the selected row and select Unenlist:

Unenlist Orchestration button menu item in Nodinite Web Client.
You will be prompted to confirm the Unenlist operation in the Execute action? dialog:

Confirmation dialog when unenlisting an Orchestration.
Once confirmed, the Action dialog shows the answer of the agent to the user, Orchestration '(name)' set to Unenlisted:

Example of a successful unenlist operation.
Note
An unenlisted Orchestration is only "Bound"—it is configured with a binding and a host handler, but not actively processing messages.
If Unenlisted, the BizTalk Server Orchestration will be evaluated as being in the Error state, with the Log Text Orchestration is unenlisted. It has no subscriptions, so messages for it fail routing:

Orchestration in Error state after being unenlisted.
An Orchestration that is not bound (no host, or logical ports without a physical port) has its own Log Text, which names what is missing. See What is evaluated for BizTalk Orchestrations?
Auto Healing
Nodinite can automatically issue the Unenlist, Start, Stop, or Enlist command for you. Learn more in the Auto Healing user guide. Use this feature to keep selected BizTalk Server Orchestrations in their intended run-time state—ensuring compliance and reducing manual intervention.
Tip
Using Auto Healing helps maintain your BizTalk environment in its intended state.
Frequently asked questions
Find more solutions and FAQs for the Nodinite BizTalk Monitoring Agent in the Troubleshooting user guide.
Why can't I Unenlist my Orchestration?
- The Orchestration must be in one of the following states:
- Enlisted
- Started
Next Steps
Start - Start processing messages (also enlists the Orchestration)
Stop
Enlist - Start subscribing for messages to process when started
Details
Tracking