.bat and schedule jobs not running
Hi, I have a batch file scheduled through scheduled tasks to run a ssis package to run everyday. This job has been running successfully for a year now but suddenly stopped working a few days back. I was unable to run the batch file manually ,but i was able to run the package manually. when i click on the .bat file it just disappears without giving out any error description. Can someone help me with this issue. Any help will be greatly appreciated. Thanks
December 8th, 2010 10:46am

Start a command-line window and execute your batch file. Talk to me now on
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2010 11:16am

are you using DTexec ? if so try to catch the error (see: http://msdn.microsoft.com/en-us/library/ms162810.aspx) and tell us what the error is. from my experiance point of view, ETL that are running and stop after one year is beacase of 1- mainly (more than 90% of the time) security and rights , on files and folders 2- some compiler change (less than 0.1 of a % - my experiance one package every 2 years) , like updating the .Net framework , upgrate of a service pack IN your case because you mentioned that "you can run it manually" , you answer is the number one, security and rights Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
December 8th, 2010 11:52am

Hi, Thanks for your quick reply. i ran the batch file from the command line and it came up with the following error. Description: Unable to load the package as XML because of package does not ha ve a valid XML format. A specific XML parser error will be posted. End Error Error: 2010-12-08 13:05:29.98 Code: 0xC0011002 Source: {FB918E16-EC6D-43EE-9C4E-A55C40622ED0} Description: Failed to open package file "D:\projects\Nova\Packages\Report.dtsx" due to error 0x80070003 "The system cannot find the path specified." . This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an in correct file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. Another thing that i discovered that all the batch (.bat) files under the folder 'Packages' failed with the same error.So it related to the file path being not recognized. how do i go about solving this issue. Thanks
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2010 1:21pm

Is the batch file in another directory on another machine?Arthur My Blog
December 8th, 2010 2:16pm

Hi ArthurZ, The answer for your question is NO.
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2010 2:25pm

I am curious if this could be caused by an Antivirus program, could you exclude the directory in question from being scanned and retry? Now, as an aside, if the jobs were successful, then what has recently changed?Arthur My Blog
December 8th, 2010 3:50pm

Thanks for all the replies. I finally solved the problem by moving all the packages to a new folder and all the packages worked like a charm . Thanks Leo
Free Windows Admin Tool Kit Click here and download it now
December 17th, 2010 10:48am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics