Windows Scheduled task succeeds but returns result 0x1

Question

I have a scheduled task on a Windows 2008 R2 server   The task includes a Start In directory entry   The task runs  and the batch file it runs does what it is supposed to do   When I run the batch file from a command prompt  I see no errors   The problem is that the  Last run result  is 0x1  incorrect function call      I did get this at one time with an incorrect DOS statement IF EXISTS file txt DO  Copy file txt file1 txt  that was corrected by dropping the DO statement   The current batch file does not show me any errors or warnings   Why am I getting a 0x1 result   Batch file that is run   PUSHD   JUKEBOX4 Archives CallRecording REM only move csv and wma together   wma should be created last  IF NOT EXIST C  CallRecording  MKDIR C  CallRecording  FOR  f   f IN   DIR  b   wma   DO       IF EXIST    nf csv  MOVE  Y    nf   C  CallRecording     POPD CD  D  C  Program Files  x86  Olim  LLC Collybus DR Upload  CollybusUpload exe POPD   Info on scheduled task setup    Program to run  C  Program Files  x86  Olim  LLC Collybus DR Upload CallRecordingUploadFromH cmd Start in  C  Program Files  x86  Olim  LLC Collybus DR Upload Run whether user is logged on or not  highest privileges    History screen  task completed entry      Task Scheduler successfully completed task   Call recording upload to portal from NH    instance   1449ad42-2210-427a-bd69-2c15e35340e6     action  C  Windows SYSTEM32 cmd exe  with return code 1     First screen of Task Scheduler shows  Run Result  of  Success

User · Answer

For Powershell scripts  I have seen this problem multiple times while scheduling Powershell scripts with parameters on multiple Windows servers  The solution has always been to use the -File parameter    Under  Actions  --   Program   Script  Type   Powershell  Under  Add arguments   instead of just typeing  C  script test ps1  use -File  C  script test ps1    Happy scheduling

User · Answer

It seems many users are having issues with this  Here are some fixes    Right click on your task    Properties     Actions     Edit     Put ONLY the file name under  Program Script   no quotes and ONLY the directory under  Start in  as described  again no quotes  Right click on your task    Properties     General    Test with any all of the following     Run with highest privileges   test both options   Run wheter user is logged on or not   test both options  Check that  Configure for  is set to your machine s OS version Make sure the user account running the program has the right permissions

User · Answer

Windows Task scheduler  Windows server 2008r2   Same error for me  last run result  0x1   Tabs   Action  remove quotes double-quotes in      program script   and     start in   even if there is spaces in the path name      General        Run with highest privileges    and      configure for your OS      Now it work   last run result  The operation completed successfully

User · Answer

I found that the problem was to do with Powershell not being able to run scripts  if that s the case for you  here is the solution

User · Answer

It turns out that a FTP download call using winscp as last thing to do in the batch caused the problem  After inserting the echo command it works fine  Guess the problems source could be the winscp exe which do not correctly report the end of the current task to the OS    del  C   ftpcrawler Account Export csv   S  Q   C  Program Files  x86  WinSCP WinSCP exe   console  script  C   isource scripte data txt   echo Download ausgef  hrt am  date  time   gt  gt  C   isource scripte data log

User · Answer

I found that I have ticked  Run whether user is logged on or not  and it returns a silent failure   When I changed tick  Run only when user is logged on  instead it works for me

User · Answer

On our servers it was a problem with the system path  After upgrading PHP runtime  using installation directory whose name includes version number  and updating the path in system variable PATH we were getting status 0x1  System restart corrected the issue  Restarting Task Manager service might have done it  too

User · Answer

I ve had the same problem  It is just a batch-file  working when manually started  but not working as a scheduled task   there were drive-letters in the batch-file like this   put z  folder file ext   seems like you should not use drive-letters  they are bound to the user  who created them - for me this little change made it work again   put   server folder file ext

User · Answer

This answer was originally edited into the question by the asker     The problem was that the batch file WAS throwing a silent error  The final POPD was doing no work and was incorrectly called with no opening PUSHD   Broken code    CD  D  C  Program Files  x86  Olim  LLC Collybus DR Upload  CALL CollybusUpload exe POPD   Correct code    PUSHD  C  Program Files  x86  Olim  LLC Collybus DR Upload  CALL CollybusUpload exe POPD

User · Answer

Just had the same problem here  In my case  the bat files had space     After getting rid of spaces from filename and change into underscore  bat file worked  sample before it wont start      x  Update  amp  pull bat    after rename      x  Update and pull bat

User · Answer

I was running a PowerShell script into the task scheduller but i forgot to enable the execution-policy to unrestricted  in an elevated PowerShell console   Set-ExecutionPolicy Unrestricted   After that  the error disappeared  0x1

[scheduled-tasks] Windows Scheduled task succeeds but returns result 0x1

Examples related to scheduled-tasks