<p>We have a task that&nbsp;runs a .bat file that takes offline backups of&nbsp;a database for a 3rd party product.&nbsp;&nbsp;We run&nbsp;it daily (except Sunday) so we have the trigger&nbsp;setting as weekly and tick every day except sunday and run it at specified times (or that's our intention);.</p><p>&nbsp;</p><p>The .bat file commands have been verified as correct by the 3rd party software provider.&nbsp;</p><p>&nbsp;</p><p>If you run the scheduled task manually (i.e right-click and Run) it works and does what we want it to do.</p><p>&nbsp;</p><p>What we can't get working consistently is running it to a timed schedule.&nbsp;It runs on time and the first time it does the action successfully, subsequent times it runs at the appointed time but shutsdown almost immediately having, it&nbsp; seems,&nbsp;carried out the first command in the .bat file as the database has been shutdown.</p><p>&nbsp;</p><p>We have noticed that when it doesn't do what we &nbsp;want it says it has successfully completed but the status is (0x1) not (0x0)&nbsp;&nbsp;but we can't find any clues in the task history as to why.</p><p>&nbsp;</p><p>We have tried two ways of invoking the .bat file:</p><p>&nbsp;</p><p>1. directly&nbsp;by briowsing to the file in the Actions tab Program/Script field and then filling in the path in the Start in field</p><p>2. by invoking the cmd.exe file in the C:\Windows\System32 folder and then putting the following command in the /C \D:[path to the bat file] in the Add Arguments field</p><p>&nbsp;</p><p>both behave the same way. Its very concerning becuase&nbsp;this task is an out of office task and therefore cannot operationally be run manually, it has to work out of office hours.</p><p>&nbsp;</p><p>We have had this task running in W2003 for years and we're trying to move to W2008 as part of an upgrade program.&nbsp;</p><p>&nbsp;</p><p>Anyone come across this or know how to diagnose why its happening ? We'd really appreciate help.&nbsp;&nbsp;&nbsp;&nbsp;</p>

We could not figure out what the problem is.? Please post it in proper format. Regards, Ravikumar P

Format fixed We have a task that runs a .bat file that takes offline backups of a database for a 3rd party product. We run it daily (except Sunday) so we have the trigger setting as weekly and tick every day except sunday and run it at specified times (or that's our intention);. The .bat file commands have been verified as correct by the 3rd party software provider. If you run the scheduled task manually (i.e right-click and Run) it works and does what we want it to do. What we can't get working consistently is running it to a timed schedule. It runs on time and the first time it does the action successfully, subsequent times it runs at the appointed time but shutsdown almost immediately having, it seems, carried out the first command in the .bat file as the database has been shutdown. We have noticed that when it doesn't do what we want it says it has successfully completed but the status is (0x1) not (0x0) but we can't find any clues in the task history as to why. We have tried two ways of invoking the .bat file: 1. directly by briowsing to the file in the Actions tab Program/Script field and then filling in the path in the Start in field 2. by invoking the cmd.exe file in the C:\Windows\System32 folder and then putting the following command in the /C \D:[path to the bat file] in the Add Arguments field both behave the same way. Its very concerning becuase this task is an out of office task and therefore cannot operationally be run manually, it has to work out of office hours. We have had this task running in W2003 for years and we're trying to move to W2008 as part of an upgrade program. Anyone come across this or know how to diagnose why its happening ? We'd really appreciate help.

The last run result code 0x1 means: An incorrect function was called or an unknown function was called. So, check your script carefully. Use the full UNC path of shared folder instead of mapped drive path. And try switch Configure For option to "Windows Server 2003, XP and 2000". Also tried with "Run with highest privilege" and "Run whether user is logged on or not"?

The last run result code 0x1 means: An incorrect function was called or an unknown function was called. So, check your script carefully. Use the full UNC path of shared folder instead of mapped drive path. And try switch Configure For option to "Windows Server 2003, XP and 2000". Also tried with "Run with highest privilege" and "Run whether user is logged on or not"?

Could the problem be the credential the task is running on? Try change the user credentials.

Could the problem be the credential the task is running on? Try change the user credentials.