Veeam uses wrong credentials

[chivo243]

Greetings Fellow Spiceheads,

I have an odd issue with Veeam. I’ve added a new stand alone server to our network, and Veeam attempts to back it up, and I get a warning:

Failed to prepare guest for hot backup. Details: Failed to connect to guest agent. Errors: 'Cannot connect to the host’s administrative share. Host: [xxx.xxx.xxx.xxx]. Account: [my.domain\xxxxxx]. Win32 error:Logon failure: unknown user name or bad password. Code: 1326 ’

I have many stand alone servers successfully backed up by Veeam, those credentials are in credential manager in Veeam as well as the correct credentials for the new VM. I’ve compared this VM to others that are successful, and see no difference. I can connect from the Veeam server to the client’s admin share with the credentials provided to Veaam credential manager.

Any thoughts from the brain trust here in SW?

Many Thanks in advance!

[alexgaft]

Try to use credentials COMPNAME\USERNAME not USERNAME alone

[chivo243]

That is what is being used. example: web01\administrator and the correct password, as I can connect to the admin share with that credential.

[alexgaft]

Do you use Application Aware backup? Are there any VMs running special MS applications (like SharePoint, SQL, Exchange, DC, etc.) within the backup job? If there are none, then, it stands to reason to disable Application Aware Image Processing and see whether it helps

[alexgaft]

Additionally this may help:

http://www.tecfused.com/2013/02/veeam-failed-to-prepare-guest-for-hot-backup-cannot-connect-to-the-hosts-administrative-share/

Good Luck,

Alex.

[chivo243]

@alexgaft

Do you use Application Aware backup? Are there any VMs running special MS applications (like SharePoint, SQL, Exchange, DC, etc.) within the backup job? If there are none, then, it stands to reason to disable Application Aware Image Processing and see whether it helps

Hi Alex,

Yes, we have SQL, Oracle, and DC’s being backed up without issues. This new addition is only running IIS, and is not yet committed to production.

Many thanks for your ideas!

[tomijuvonen2812 (ita-tomi)]

Possibly UAC issue? You could check if this DWORD exists:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ LocalAccountTokenFilterPolicy

If it does not exists, create it and set value to 1 and reboot. If it exists, change value to 1.

[chivo243]

I will give this a shot. I’m happy to have the issue just go away, but the larger question is why did this happen, I have a handful of stand alone VM’s that back up fine using the same method?

@tomijuvonen2812

Possibly UAC issue? You could check if this DWORD exists:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ LocalAccountTokenFilterPolicy

If it does not exists, create it and set value to 1 and reboot. If it exists, change value to 1.

many thanks for taking the time to reply!

[andrew-veeam]

Dunno, looks really strange. Can you try to add used account to local admins groups on that server and/or reenter credentials to Veeam?

[chivo243]

@andrew-veeam

Dunno, looks really strange. Can you try to add used account to local admins groups on that server and/or reenter credentials to Veeam?

Hi Andrew,

I’ve re-entered the credentials two times now, still no joy. I will look at the other suggestion when I can access the system.

[chivo243]

Gents,

I’ve added the registry key, we’ll have to wait for tonight’s backup to run and see I guess.

Many thanks for your replies!

@andrew-veeam @alexgaft

[alexgaft]

Good Luck, buddy!

[shanevallance (shane_av)]

Also if you have multiple servers in the same backup job with different credentials, look at the Job Properties > Guest Processing > Credentials > Guest OS Credentials to make sure the correct account credentials are specified for each VM.

[chivo243]

@shanevallance

Also if you have multiple servers in the same backup job with different credentials, look at the Job Properties > Guest Processing > Credentials > Guest OS Credentials to make sure the correct account credentials are specified for each VM.

I having difficulties finding the starting point of your path. Would it fall under Right click on backup job-> edit, then start the wizard? If so, I’m missing the step where I can assign a VM credentials. I can find the list, 11 in all, and test “one” set of credentials against the whole job, but not an individual VM. I didn’t set up this installation, and am not having an “Uh Oh moment” as I write this…

Let me know what you think.

[shanevallance (shane_av)]

Yes, Right click job and edit.
Then go to the Guest Processing tab, and click Credentials…

Then select the VM you added, and choose Set User… then credential type,

From there you can choose credentials already in the credential manager or add new credentials. Then OK. Now when you choose the option to Test Now it will attempt connections with those VMs with the credentials you specified through that menu.

[chivo243]

shane_av,

Great info, I’ll be testing it tomorrow! It’s already end of the day where I’m at…

[chivo243]

@shanevallance

Yes, Right click job and edit.
Then go to the Guest Processing tab, and click Credentials…

Then select the VM you added, and choose Set User… then credential type,

From there you can choose credentials already in the credential manager or add new credentials. Then OK. Now when you choose the option to Test Now it will attempt connections with those VMs with the credentials you specified through that menu.

Shane_av,Thanks for the info! The error is gone👍

Thanks

[chamroeunrithchin]

it work if we are using SERVERNAME\USERNAME

[alexfogerty]

I had the same issue after creating a new Server 2016 Hyper-V Host. It turned out that when I created a backup job it has assigned the Host administrator login to the VMs, which have a different administrator login. Going into Guest Processing > Credentials > Set User and assigning a username and password to the individual VMs has fixed this!