Resolving Stuck Scheduled Executions in Jet Analytics
Issue
A scheduled execution in Jet Analytics did not complete and remains in an unknown/running state. As a result, this project and other related projects are no longer executing according to their scheduled plans.
Symptoms:
Execution status shows as Unknown/Running in the execution log.
Right-clicking and selecting Resume does not resolve the issue.
Subsequent scheduled executions are not triggered.
Root Cause:
This typically occurs when the Jet Data Manager (JDM) crashes or is interrupted during execution, leaving the process in a hung state.
Resolution Steps:
-
Resolve the Stuck Execution: To resolve the issue with the execution stuck in the unknown/running state, please refer to the following guide:
Restart TimeXtender Services: After clearing the stuck execution, restart the TimeXtender services to ensure the scheduler resets properly.
-
Check for running processes:
Open Task Manager.
Look for timeXtender.exe. If it’s running while JDM is closed, terminate the process manually.
Manual Execution (Optional): Manually execute the package to confirm that it completes successfully without getting stuck or entering an unknown/running state.
Use SQL Server Profiler (Advanced): Use SQL Server Profiler to check for any ongoing Jet-related activity in the database.
Test with a New Schedule: Create a simple test execution package and schedule it to run a few minutes in the future. If the test completes successfully without issues, it confirms that the scheduling system is functioning as expected.
Additional Notes:
Always ensure that backup jobs and JDM executions are not scheduled at the same time to avoid conflicts.
Regularly monitor the execution log for any stuck or failed jobs.