Skip to main content
To homepage To homepage

I have a scenario where Exmon periodically seems to loose synchronization, or perhaps has some status issue relating to a package, Where the TX package will just error out immediately on the process map with an error that the job is already running. I am using Exmon against the SAAS version of TimeXtender (holistic). 

The underlying package is definitely not erroring out or is running. But Exmon seems to think that the package/Job is running.

So far the only way I have been able to correct this is by deleting the package and re-adding it. But this keeps reappearing randomly or different packages with the Exmon processes. 

Is there a way to clear the status of an Exmon package or is this a bug that needs addressing?

Using TX 6645.1 and Exmon 24.2.0.28

Help! finding it hard to explain this one away with the client!

Just found this looking at the history of the package from the Process Map.

Seems a job started and Exmon missed the end of the job somehow. If I try to open the log details on the “unfinished” package it never loads.

 

Well I think that I have found the issue! It appears that another developer was setting execution schedules on the TimeXtender Jobs that were running at the same scheduled time as the Exmon schedule. So I think that periodically they would collide exactly and both systems would “start” the job. This seemed to cause the Job system in TimeXtender to flag the Job as “Active” and leave it there. So even though I could execute the ODX transfer step directly in the ODX instance in TimeXtender, I was not able to run the Job or the Exmon step.

I fixed this by restarting the TimeXtender Execution service and ODX Service on our server which cleared everything out.

I have removed the conflicting Job Schedules in TimeXtender and all seems to be working properly now.

@Paul McLeod Bespoke Analytics thanks for confirming. Please also see the following fix regarding job status updates in TimeXtender Data Integration 6766.1, which may be potentially related:

“Resolved an issue where job statuses failed to update after task completion by implementing retry logic.“

 

Thanks Christian, I have been thinking we need to catch up on the releases, even more reason to do so!

Reply


Terms and ConditionsCookie settings