AISBackup: User Guide.

Cookie Consent Required

This website uses cookies in the Forum option, the PayPal purchase option and the Affiliate option, these cookies are required to make the website work.

If you agree to our use of cookies please click 'I Agree', for more information click 'Privacy Statement', if you do not wish to proceed please visit another web page or close your web browser.
 
logologo
 The time in Wales is: 25 April 2024 02:58:56

AISBackup: Troubleshoot MS Task Scheduler.

Here are some suggestions for finding out why a scheduled task will not run.

Windows NT, 2000 & XP.

A password protected account name must be used, the password cannot be blank. This is a Microsoft restriction and not AISBackup.

Some Jobs Missed.

Only one copy of AISBackup can run at a time, place multiple backup jobs in the same scheduled task.

AISBackup is running but no files are backed up.

If you are running a backup from a different account from that with which the backup job was created: Log into the account and run the job manually, you may find that the program options in the 'Backup' account have not been set-up correctly.

Reading the Microsoft Task Scheduler log file..

If a job still will not run check the Microsoft Task Scheduler log, and work directly within Microsoft task scheduler to get the job up and running when the next minute ticks over.

  • Launch Microsoft Task Scheduler, This can be done via Control Panel on Windows XP or via Start / Programs / Accessories / System Tools / Scheduled Tasks or via the AISBackup Option Tools / Show MS Task Scheduler.

  • Choose menu option Advanced / View Log or the AISBackup option View / View MS Task Scheduler Log to open Task Scheduler log.

    Look for the line containing "[ ***** Most recent entry is above this line ***** ]"
     
    Here is an example log where things have gone wrong:

    "AISBACKUP - Auto.job" (AISBACKUP.exe)
    Finished 05/05/2003 15:34:59
    Result: The task completed with an exit code of (1).
    "AISBACKUP - Auto.job" (AISBACKUP.exe) 05/05/2003 15:38:00 ** ERROR **
    The attempt to log on to the account associated with the task failed, therefore, the task did not run.
    The specific error is:
    0x8007052e: Logon failure: unknown user name or bad password.
    Verify that the task's Run-as name and password are valid and try again.
    "AISBACKUP - Auto.job" (AISBACKUP.exe) 05/05/2003 15:42:00 ** ERROR **
    The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task.
    The specific error is:
    0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.
    "AISBACKUP1 - Auto.job" (AISBACKUP.exe) 05/05/2003 15:44:00 ** ERROR **
    The attempt to log on to the account associated with the task failed, therefore, the task did not run.
    The specific error is:
    0x8007052f: Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced.
    Verify that the task's Run-as name and password are valid and try again.
    [ ***** Most recent entry is above this line ***** ]

 

  • Most errors will probably relate to invalid account information, it is probably quicker to work with and test the Task Scheduler from within.

    Right click the AISBackup task and choose Properties.

  • To check that the run time parameters are set correctly select, copy and paste the contents of the Run: edit box into the Windows Start / Run option, then click OK to run AISBackup.

  • Make sure that you are logged into the account from which AISBackup is going to run (this makes things much easier to test).

  • Check that the computer name and account name in Run As are set correctly. Then Click Set Password..., enter the password then click OK.

  • Click the Schedule Tab.

  • Ensure the start time is set to the next minute then click Apply.

  • Wait for the minute to tick over. AISBackup should now run okay, if not re-check the account name and password.

Back To Contents