This is the guide for one of three issues.
You had no new data after the nightly execution, but also received no failure notification on email.
This is because it did not start the nightly execution, because it newer got a end date, or because it still is running.
The normal way to tell that a execution is running is by going to the Execution pane and there will be a note about a execution packages last run time. Right click on that and go to the execution overview. This will show the start time and the end time. It is running if the End is equal Unknown/Running, total time is empty and the succeeded equal Unknown.
Is it still running?
How to check what is running.
I made a guide for that here Is my execution running
It is not running
The scheduler service
When you by going through the previous guide, saw that it was not running start by checking if the scheduler service is running.
If not, you have the explanation as to why it did not get a end and why it did not start a new one. How to find the error below.
If it was running all along. Try to log in as the scheduler user. If it does not point to the correct repository, it will not start.
The ProcessId issues
Take a look at the Schedule Execution Log. You can see the process id the job got here. At times this will block future executions. This is most likely the reason why it did not start.
You can remove the ProcessId by right clicking on the row and set it to empty. Some times this isn't enough, so I will add a script to deal with this issue below.
Find the error
The most common issue is that the execution doesn't start again because it is blocked by old ProcessIds. See how to fix that below.
If it is related to the service you can find the error that caused the missing fail notification. The best place to look is the event viewer. The errors will be located. If the error is out of the ordinary, send the error message to us at firstname.lastname@example.org.
Fix the issues
If the server service is stopped consider setting it up like this, to keep it running. Automatic (Delayed Start) is to make it wait for the SQL server to start before starting itself. Restart the service, is what it does if it accidentally fails.
Stop a currently running scheduled execution
Sometimes it simply is slow execution, perhaps a change of a lookup has made the data cleansing procedure many hours too long. To stop it simply stop the scheduler service. Go to the Details pane of the Task manager. Find the timeXtender.exe processes that are running. End all of them by pressing End Task. Fix the issue in your project, deploy the changes and start the service again. You may also need to run the following to be certain it starts again.
You can remove them with the two following scripts. The first part is the one that gets you the schedules that have issues. Run it against the repository database.
SELECT * FROM dbo.ScheduleJobs WHERE ProcessId is not null or ProcessId = ''
The second part makes sure they do not block new scheduled jobs from running. It does not erase anything. Be sure to stop the scheduler service before running this and that no current executions are running.
UPDATE dbo.ScheduleJobs SET ProcessId = NULL WHERE ProcessId is not null or ProcessId = ''
After this you can erase the old logs through the Repository Administration tool. The ones that has no end date is equal those with an unknown status.
Restart the service and anything should be up and running again.