Hi ​@avanrijn 

How exactly does they not work?

If the Execution Service is running, it is supposed to start the jobs at the specific time, but you say it doesn’t start.

Hi Thomas,

Thank you for your reply. I am going to schedule a meeting with my customer to have a look what is going on. Right now they refresh their DWH by hand. 

Could you give me hint where to look in the TX logging to find out what is causing this.

I can think of:

EventViewer (appl Windows Log): TimeXtender.Job.ExecutionService, TimeXtender Ingest Service 6766.1

Execution package: View execution history log

Any tip would be helpfull Thomas.

Thanks in advance.

Regards,

Arthur


 

Hi ​@avanrijn 

Start with the end. That is the Execution Overview log on the execution package.

You can see if package could be running when this is suppose to start in the event viewer. The message will not be an error, just an information message where it will state something like package could not start due to being blocked by another.

If you use Concurrent Packages to allow multiple packages to run simultaneously, then you can check if they are supposed to start at exactly the same time. That is not allowed despite using this option.

Then there is the setup of the Execution Service, see if it is set to restart on error, not do nothing. This will make sure it is restarted if there is an issue because it will not be able to start anything when it is somehow down.

​@avanrijn does the above comment answer your question? Please let us know if you have any follow up questions