Skip to main content

No Execution Lock on Instance Error When Running PRD Processes from Orchestration in TimeXtender


Symptoms

When finalizing the Orchestration setup for your TimeXtender environment, you notice that DEV processes start without issues, but PRD processes do not start from Orchestration, whether scheduled or triggered manually. You are able to manually run Ingest tasks on the PRD instance without issues. After reconfiguring Execution Services (switching between single and multiple services per environment), PRD processes still fail to start from Orchestration. No errors are initially shown in the web interface, but later, error emails are received after manual attempts to start processes from Orchestration.

Error: No execution lock on instance

Additionally, log output may include:

  • log4net:ERROR You have tried to set a null level to root.
  • log4net.Core.LogException: Error in the application.

Cause

This issue occurs when the Execution Service does not have the required lock on the instance needed to run the process. This can happen if:

  • Execution Services are not correctly assigned to the appropriate Prepare and Deliver instances for each environment.
  • There are configuration mismatches after changes to the Execution Service setup (such as switching between single and multiple services per environment).
  • Recent changes to system time zone or daylight saving time settings have affected scheduled executions and service locks.

Resolution

  1. Ensure that each environment (DEV, PRD) has its own dedicated Execution Service running on the correct VM.
  2. Assign each Execution Service to the specific Prepare and Deliver instances it should control. For example, the PRD Execution Service should have a lock on the PRD Prepare and Deliver instances, not on DEV instances.
  3. After making changes to Execution Service assignments or time zone settings, restart the Execution Services to ensure new configurations are applied.
  4. Verify the CET (Central European Time) or other time zone configuration in both the system and TimeXtender settings to ensure scheduled executions align with the intended schedule.
  5. If you recently changed the time zone or experienced a daylight saving time change, review and, if necessary, recreate or reschedule any affected tasks to ensure they trigger as expected.
  6. Check the Orchestration and Execution Service logs for any additional errors or warnings that may indicate misconfiguration or permission issues.
  7. If the issue persists, confirm that no other Execution Service is attempting to control the same instance, which could prevent the lock from being acquired.

Reference Ticket

35505

Did this topic help you find an answer to your question?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings