Robocopy fails in Scheduled task with ERROR 1326 Logon failure

16,631

When I was doing something similar, I was unable to get it to work without first mapping the drive.

Action 1 in Task Scheduler:

net use z: \\MY.IP\DatabaseBackupsShare mypass /user:myuser

Action 2 in Task Scheduler:

robocopy "C:\MylocalDirBackup" z:  /mir /z /log:"C:\MyLocalDIR\RobocopyTestLog.txt"

Because you're storing the password--ew--use an unprivileged account rather than an admin and give that account a strong password, the least possible privileges for the task, etc.

Share:
16,631

Related videos on Youtube

reticentKoala
Author by

reticentKoala

Updated on September 18, 2022

Comments

  • reticentKoala
    reticentKoala about 1 year

    My aim: To simply mirror a database backup directory onto another server

    Approach: Use Robocopy statement contained in a scheduled task

    robocopy "C:\MylocalDirBackup" "\\MY.IP\DatabaseBackupsShare"  /mir /z /log:"C:\MyLocalDIR\RobocopyTestLog.txt"
    

    Environment:

    • Windows Server 2008R2
    • Scheduled task user "MylocalUser": Local adminon local machine
    • Network config: Both servers on workgroup

    Tests:

    • navigate to share \MY.IP\DatabaseBackupsShare as "MylocalUser" - success, no prompt for credentials
    • Run robocopy command from command line when logged on as "MyLocalUser" - success

    The Problem!: When running Robocopy command from a scheduled task the following error is raised:

    2013/10/22 20:04:57 ERROR 1326 (0x0000052E) Accessing Destination Directory \\MY.IP\DatabaseBackupsShare\ Logon failure: unknown user name or bad password.
    

    I found several other people who are having similar problems, and followed suggestions here: http://social.technet.microsoft.com/Forums/scriptcenter/en-US/b591346e-3ed0-4ed1-9453-24851ebe1bb1/scheduling-robocopy-to-run-at-system-startup?forum=ITCG

    Any help gratefully received. I thought this was going to be a quick task...

  • reticentKoala
    reticentKoala about 10 years
    Thanks for your input. In my first attempt I used the scheduled task to execute a Powershell script, which I'd imagine to behave similarly to the batch file approach
  • Techie Joe
    Techie Joe about 10 years
    Agreed. You don't need a privelaged account if all you're doing is copying from point A to point B. Just make sure that the account can write to point B. This is just a copy job not a program that interacts with the operating system.
  • MikeAWood
    MikeAWood about 10 years
    The GUI doesn't expose the password and without said credentials will not let you modify the task setup. Though a simple workaround is to modify the action file it is pointing to. Also, the password is stored in the registry as a hash, not as a password. Or maybe there is another way to expose the password that I am not aware?
  • MikeAWood
    MikeAWood about 10 years
    @KatherineVillyard is correct (well, sorta). The credentials can be forcibly decrypted, but it requires more than a working knowledge of Credentials Manager, the locally logged in user used to create the task's key and the necessary processes to decrypt it. ie... not easily stolen, but still a possibility, but certainly better than plaintext in the script.. This was an actual question on SF already serverfault.com/questions/342084/…
  • reticentKoala
    reticentKoala about 10 years
    The account specified in the scheduled task is the same one I've been testing with at the command line - "MylocalUser", hence the suprise at a permissions issue.
  • reticentKoala
    reticentKoala about 10 years
    I've seen other people make this suggestion, so I tried explicilty mapping a drive specifying credentials. I come across another problem: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. This despite no other connections (tried net use * /del)
  • Katherine Villyard
    Katherine Villyard about 10 years
    Navigating to \\MY.IP\DatabaseBackupsShare in Windows Explorer counts as a connection to the server, alas. That's probably what you have.