For two weeks my clients Power Bi report was refreshed daily without issues.
Last week this changed after the TimeXtender Execution server stopped running. I ran the TimeXtender ODX Server Configuration on the desktop and started the TimeXtender execution server again.
The next days the execution jobs where triggered again but I would like to know why TimeXtender Execution stopped running in the first place.
How could this have happened?
Best answer by rory.smith
Hi,
it looks like your service is set up as “Manual” startup type. So if something else triggers a reboot of the machine (Windows updates, etc.) your service won't automatically come up. That is what the Automatic and Automatic (Delayed) options are for. The delayed variant only starts the service after a registry-set delay has passed (usually 2-3 minutes).
You should be able to use Windows Event Viewer to determine what happened. The TimeXtender services log information into the Software category, there are other places like System where Windows will log events (reboots, etc.).
it looks like your service is set up as “Manual” startup type. So if something else triggers a reboot of the machine (Windows updates, etc.) your service won't automatically come up. That is what the Automatic and Automatic (Delayed) options are for. The delayed variant only starts the service after a registry-set delay has passed (usually 2-3 minutes).
You should be able to use Windows Event Viewer to determine what happened. The TimeXtender services log information into the Software category, there are other places like System where Windows will log events (reboots, etc.).
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.