We are using a 3rd party scheduler called adtempus to run a batch file, this will work fine for a couple of weeks and then the job will stop working and the only thing that 'fixes' it is a reboot of the machine. We see the same behavior when using
SQL Agent as well as windows task scheduler to run the batch file. running the batch file manually always works, even after the scheduled job fails. The scheduled jobs fail with the below error, its the same error no matter what scheduling
tool we use, the batch file just launches an application and this is happening on multiple jobs. I've seen a lot of posts relating to MSVCR90.dll as it relates to specific applications, but nothing this generic. I've also read another post suggesting
to add permissions through the directories all the way down to the batch file and that doesn't work either.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.