Failed to determine SCVMM Server version, The target princip

[yorick.r]

When we try to backup or try to add the machine in the virtual machine console of Veeam then we are getting the error Failed to determine SCVMM Server version, The target principal name is incorrect
.
Does anyone has a suggestion? I cannot find anything about it, I even logged a call a few weeks back but nobody is respoding to the call

[foggy]

Yorick, could you please describe your setup in more detail? And what is your support case ID?

[yorick.r]

My Case id is 00150504, its an setup with scvmm when i try to make the setup it fails, I had it running for a few days but it stopped so I deleted the server from the virtual machine tab and tried te rrecreate it to schedule backups...but I am getting the error Failed to determine SCVMM Server version, The target principal name is incorrect

[yorick.r]

Veam Version 6.1.0.205 64bit

[foggy]

As I can see from your case, it was closed due to no response from your side. There's a chance that you just haven't seen notifications from Veeam Support for some reason (I recommend you to check your spam folder). Anyway, logs review is required here, so please reopen the case (or create a new one) to continue investigating the issue with support.

[yorick.r]

Id logged a new case already... so i am waiting for support

[tsjeff]

What was the resolution for this problem?

I'm having the same issue with a new installation of 6.5 B&R when trying to add an SCVMM server. I've verified the domain name of the SCVMM server is aptly named SCVMM.domain.com, and the service account with local admin access to the SCVMM is named aptily (DOMAIN\scvmm).

I've verified the account is allowed in AD to logon to on all computers, and I've tried this with local firewalls completely disabled on the Veeam B&R server and the SCVMM server. The Veam B&R server and the SCVMM server are on the same subnet.

I've also opened a Case on this: 00208439

Thanks in advance!

[veremin]

Unfortunately, two cases opened by Yorick were closed and didn’t contain any relevant information regarding this issue.

Thus, let's wait and see what support has to say about the aforesaid problem.

[Modaly_IT]

I had the same issue with version 7.0.0.690. The issue stemmed from the run as account used to connect to the SCVMM server. I added another account with local admin rights to the SCVMM server and SCVMM servers to resolve the problem.

[haslund]

Just for future reference, I had this issue with a customer today.

It seems two items helped solve the issue:
#1 The user, connecting from Veeam to SCVMM had correct permissions in SCVMM and on the hosts. However it was missing permissions on the Hyper-V cluster itself.
#2 We changed the user format in Veeam, for the user connecting to SCVMM, from domain\user to user@domain.local

Some log dump for easier search:
Error [hypvcls.domain.local] Disks and volumes discovery failed Error: Failed to determine SCVMM Server version:

The target principal name is incorrect

A call to SSPI failed, see inner exception.

You cannot access VMM management server scvmm02.domain.local.
Contact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again.

You cannot access VMM management server scvmm02.domain.local. (Error ID: 1604)

[Yorick.r1]

Hi, I was able to fix the issue. I can`t provide a solution because it`s a while ago ..