To homepage To homepage
Solved

Execution Package Unknown/Running and never Finished

  • 25 January 2024
  • 3 replies
  • 96 views
kerry_bespoke
Rank
Userlevel 1
Badge

The daily build of a data warehouse started for an Execution package but never finished. I am unable to see any cause of this job stopping in the TX logs or Event Viewer (Unknown_Running.png) of the server. Is there somewhere else I can check to determine the cause of the build to cancel while running for no reason?


Since there was no direction to resolve this issue, we left the build to try to run again today and are now receiving an error that says the job is currently executing (Warning.png). How do I clear this stuck job in TX?

 

icon

Best answer by Thomas Lind 25 January 2024, 14:45

View original
Kerry // Bespoke Analytics

3 replies

bas.hopstaken
Rank
Userlevel 3
Badge +4

Hi @kerry_bespoke :


You can use this article to troublehoot the Unknown/Running status issue: 

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-

Most of the time, the solution is decribed in 'Remove old unknown schedules’, in the article above.

Bas Hopstaken (2Foqus)
Thomas Lind
Rank
Userlevel 6
Badge +5

Hi @kerry_bespoke 

I made this guide to help figure out what is going on.

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

https://legacysupport.timextender.com/hc/en-us/articles/360000004126#what-is-currently-running-on-my-system

Based on the message you see in the Event Viewer I would think that it is still running. You can stop it by ending the timextender.exe task that has the processId you see in the message.

Like you can see here in the image from the guide.

 

kerry_bespoke
Rank
Userlevel 1
Badge

Thank-you @Thomas Lind  and @bas.hopstaken for your swift response on this matter. Both articles were incredibly useful in troubleshooting and resolving our issue.

I did find a stuck TimeXtender process in the Task Manager that we were able to kill and get the overnight build to process again without issue.

I am now using your articles to assist in building this error into our TX Dashboards to highlight when this error occurs to the client.

Thank-you again!

Kerry

Kerry // Bespoke Analytics

Reply


Terms and ConditionsCookie settings