You might try recovering the file and seeing if the server schedule still has this issue when run on the recovered copy. This crash could be due to a damaged file.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).
Michael: we have exactly the same issue. And we have reinstalled the server (Windows 2008r2) and Recovered the files and so on.
Did you solve this? How?
We have found a workaround that prevents the scripts from craching: adding som steps in the script that moves some not used data in other tables. Very strange, but it makes them not abort.