Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.Login to AccountCreate an Account

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Tripredacus

Posted 30 November 2011 - 09:11 AM

You should add some error handling/logging into your script, such as creating a token somewhere (easiest copying a text file) or even writing to the Application Event Log. Basically, if a .cmd fails, you won't see it as a fail in the job history, because a .cmd will always just do a successful exit under most circumstances, since cmd doesn't really pay attention to what you are having it do. If the programs themselves are failing, they would be the one to generate the error, not cmd, which is why it doesn't "fail" in the log.

zeezam

Posted 01 December 2011 - 01:47 AM

zeezam

Member

Member

146 posts

Joined 28-March 08

You should add some error handling/logging into your script, such as creating a token somewhere (easiest copying a text file) or even writing to the Application Event Log. Basically, if a .cmd fails, you won't see it as a fail in the job history, because a .cmd will always just do a successful exit under most circumstances, since cmd doesn't really pay attention to what you are having it do. If the programs themselves are failing, they would be the one to generate the error, not cmd, which is why it doesn't "fail" in the log.

Ok.

This must have something to do with how windows 2008 start the script or something, because if I run it manually it works.The same script did work on a windows 2003 as a schedule task.

Tripredacus

Posted 01 December 2011 - 09:10 AM

Its more likely to do with permissions. When you run it "manually" you run it under your user account. When it is run by Task Scheduler, it is run under an OS account. Try changing the account that is used to run the task.