Skip to main content
To homepage To homepage

Hi,

 

We are facing the (known) error of Execution status Unknown/Running. After a few months of no problems. We are currently on version: 6284.1

In TimeXtender Classic I always fixed this by deleting the log rule in the Repository Administration, but in TimeXtender Data Integrator, this is not possible anymore, causing the next schedules to not execute anymore.

 

I restarted the execution service and deleted the corresponding TimeXtender task via Task manager. Anyone knows if this is enough to let the next execution run succesfull? Or knows how to delete this unknown/runnign execution log rule?

 

Regards,

Devin

Hi @devin.tiemens 

When a execution is started that runs a execution package it behaves the same as always.

So here I got a job that runs my incremental load package from my DW instance.

When it runs like this.

You can see that you have an extra timextender.exe task that runs in the task manager as the user that runs the Execution Service.

If there is no additional timextender.exe tasks running as the same user as the execution service, then it is not running and should start an execution on the next scheduled time.

Hi Thomas,

 

Thanks for your reply! I saw an extra TimeXtender task in the task manager which I indeed killed. The only difference with your screenshot is that the state is "Idle” at my job monitor:

But probably this is due to the fact that it is already running for a few days.

I have temporarly scheduled the task at 10.00 UTC today. I will let you know if it has run succesfully after that.

 

The scheduled job has now run succesfully 😀

 

Hence, in case of Execution Unknown/Running status and you want to kill this execution, you should perform the following steps:

  1. Stop TimeXtender Execution service via services.
  2. Delete running task (called TimeXtender) via Task Manager.
  3. Start TimeXtender Execution service again via services.

 

Kind regards,

Devin

Hi @devin.tiemens 

That has always been my suggestion as well. Once you locate the task and wants to stop it end the timextender.exe task and you are good to go. The starting and stopping of the Execution service is a good idea but I don’t think it is 100% necessary.

I have it in our old guide as well.

https://legacysupport.timextender.com/hc/en-us/articles/115004728763-Scheduled-Execution-issues-Did-it-not-start-did-it-fail-or-is-my-execution-still-running#Fix

Reply


Terms and ConditionsCookie settings