Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 119
  • Last Modified:

Scheduled task not running

I get a very descriptive 0x1 (typical Microsoft bull****).

Anyone have any idea what that would mean?  Is it beyond server 2008 to run a batch files now?
0
classnet
Asked:
classnet
2 Solutions
 
Todd NelsonSystems EngineerCommented:
Does the event log provide you more information?

I run batch files with scheduled tasks all the time on Windows 2008-2016 servers.
0
 
classnetAuthor Commented:
That's probably the most irritating part... no clues left behind.
0
 
QlemoC++ DeveloperCommented:
Each task has its own log, so that is the first to look for. But it will only show generic stuff, like a batch file not found, or the executable not able to be run because of privilege issues, and such.

For more details you indeed need to do your own logging, like echoing debug/progress info into a file ...
0
 
Bill PrewCommented:
I always like to capture all output from the batch job that I schedule to a text file for reading after execution.  This can be especially helpful during the debugging process if the bat file is not executing at all do to a syntax error, etc.  Try adding the following to the end of the command line you are invoking from the tash scheduler, run a test, and then see what's in the text file.

>c:\temp\debug.txt 2>&1


~bp
0
 
classnetAuthor Commented:
Thanks folks... I created my own log which lead to the issue.  All is well now.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now