- 4 minutes to read

Start Orchestration action

Discover how Nodinite empowers you to Start BizTalk Server Orchestrations quickly and efficiently using the intuitive Web Client or the powerful auto-healing feature. Streamline orchestration management and ensure your environment is always ready for business.

Stop and then Start an Orchestration from a Monitor View, animated walkthrough (6.4.2)
Animated walkthrough: Stop sets the Started Orchestration to Enlisted (Warning), and Start brings it back to OK.

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 Start the selected BizTalk Server Orchestration.

A Started Orchestration can be Unenlisted or Stopped. There is no need to use the BizTalk Server Administration Console (MMC) for this administrative task.

After you have successfully started a BizTalk Server Orchestration, you can later Stop it (so that it is no longer running and processing messages). For information about stopping an Orchestration, see How to Stop an Orchestration.


How do I Start a BizTalk Orchestration?

To Start a BizTalk Orchestration, you have several options with Nodinite:

  • Use the Action button menu item Start (as described on this page)
  • Use the Start button available from within the Details modal
  • Use the Auto healing feature – use with care!

To Start a BizTalk Server Orchestration, press the Action button on the selected row and select the Start button menu item:
Action menu of an Orchestration with the Start menu item (7.12)
Start Orchestration button menu item.

The user will be prompted to confirm the Start operation in the Execute action? dialog: Are you sure that you want to execute action 'Start' on resource '(name)'.
Execute action? confirmation for Start on the Orchestration Lab.Orders.i0100_Started (7.12)
Confirmation dialog when starting an Orchestration.

After confirmation, the Action dialog shows Communicating with the Agent… while it waits, and then the answer of the BizTalk Monitoring Agent: Orchestration '(name)' set to Started. Start also enlists an Orchestration that is unenlisted.
Action dialog with Orchestration Lab.Orders.i0100_Started set to Started (6.4.2)
This image shows a successful start operation.

Warning

The Orchestration may have incomplete configuration or other dependencies that prevent it from starting. If Nodinite fails, you likely cannot start it from the BizTalk Server Administration MMC either.

When the Orchestration is Started, Nodinite evaluates it as being in the OK state:
Started Orchestration Lab.Orders.i0100_Started in OK state with the Log Text Started (6.4.2)
This image shows a started Orchestration in Monitor Views.

Auto Healing

Nodinite can automatically issue the Start, Stop, Enlist, or Unenlist command for you. Learn more in the Auto Healing user guide. This feature helps keep selected BizTalk Server Orchestrations in the intended run-time state.

Tip

Using Auto Healing keeps your BizTalk environment in its intended state.

Frequently asked questions

Find additional solutions to common problems and the FAQ for the Nodinite BizTalk Monitoring Agent in the Troubleshooting user guide.

Why can't I Start my Orchestration?

The Start operation may fail for several reasons. The most common reasons are:

  • The Orchestration must be in one of the following states:
    • Stopped
    • Enlisted (in which case the Start operation is also a Stop operation)
    • Unenlisted

Make sure to configure the Orchestrations first.

  • Bindings must be properly configured:

    • Host assigned
    • Port bindings set if applicable

    New 6.4.2 The Resource's Log Text names what is missing: no host is selected, the logical ports that are not bound to a physical port, or a host that does not exist. See What is evaluated for BizTalk Orchestrations?

  • BizTalk Server refuses Start unless every port the Orchestration sends through is enlisted, and every Orchestration it calls is started.

When BizTalk refuses the Start, the Action dialog shows There is a problem to execute operation for '(name)' in category 'Orchestration'. Please retry. If the problem persists, contact the system administrator. See diagnostics for details (CorrelationId: …):
Action dialog after a refused Start of Lab.Orders.i0100_OrderFlow, with a CorrelationId and no BizTalk details (6.4.2)
Failed Start operation example: the send ports of Lab.Orders.i0100_OrderFlow are unenlisted.

New 6.4.2 BizTalk's own reason is written only to the agent's diagnostic files, under that CorrelationId, because it holds internal details such as assembly names. Search the diagnostic files for the CorrelationId to find it. The agent also rolls the refused change back, so BizTalk management keeps working. Older agents showed BizTalk's raw text in the dialog, and a refused change could lock the BizTalk management database until the agent was restarted (see Troubleshooting).

The BizTalk Monitoring Agent cannot start Orchestrations that you cannot start from the BizTalk Server MMC either.

Tip

Test the start operation from the BizTalk Server MMC if the operation fails using Nodinite, or look up the CorrelationId in the agent's diagnostic files.

Next Steps

Stop
Enlist
Unenlist
Tracking
Details

BizTalk Orchestrations
Monitor Views
Remote Actions