Execution Package Fails to Start in Orchestration After Creating New Instance in TDI

Symptoms

When starting a new deliver execution package in Orchestration, the process does not begin as expected. Instead, it continuously spins and eventually times out after the set period. Other similar processes work correctly, but the affected process appears to have multiple running instances, even though only one is actually running. Running the execution package directly from TimeXtender Data Integration works without issue, but attempts to execute from TimeXtender Orchestration fail. The problem may expand to other processes, particularly new ones, while existing ones continue to function.

Cause

This issue occurs when a new deliver or prepare instance is created in TDI, but the TimeXtender Execution Service configuration is not updated to include the new instance. As a result, Orchestration cannot communicate with the new instance, causing the process to hang and eventually time out. The service bus for the new instance does not start, and there are no corresponding entries in the Windows event log for the new instance.

Resolution

1. After creating a new deliver or prepare instance in TDI, rerun the TimeXtender Execution Service configuration tool on the server.
2. Ensure that the new instance appears in the configuration tool and is selected for execution.
3. Complete the configuration wizard to update the Execution Service with the new instance.
4. Restart the TimeXtender Execution Service to apply the changes.
5. Check the Windows event log to confirm that the service bus for the new instance has started successfully. Look for an entry stating "Message bus started."
6. Attempt to run the execution package from Orchestration again. The process should now start and complete as expected.

Additional Notes

• If you create additional deliver or prepare instances in the future, always rerun the configuration tool to include them in the Execution Service.
• Running the execution package directly from TimeXtender Data Integration may still work even if the Execution Service is not configured for the new instance, but Orchestration will not be able to execute it until the configuration is updated.
• If the issue persists after updating the configuration and restarting the service, consider restarting the server to ensure all services are running correctly.

Reference Ticket

35379