Hi,

I am configuring a private cloud. I have installed the SCVMM server and App Controller Server separately.

When I am trying to add the VMM server to App Controller, I am getting the following error.

Category: Critical
Description: Connection attempt to the target system failed.
Details: Category: Critical
Message: 1604ConnectServerAuthenticationFailed
Description: You cannot access VMM management server scvmm.corp.usl.in.
Details: Category: Critical
Message: System.ServiceModel.Security.SecurityNegotiationException
Description: A call to SSPI failed, see inner exception.

Category: Critical
Message: System.Security.Authentication.AuthenticationException
Description: A call to SSPI failed, see inner exception.

Category: Critical
Message: System.ComponentModel.Win32Exception
Description: The target principal name is incorrect

I have configured private cloud and installed the SCVMM server and App Controller Server separately.

When I am trying to add the VMM server to App Controller,

I am getting the following error.

Category: Critical
Description: Connection attempt to the target system failed.
Details: Category: Critical
Message: 1604ConnectServerAuthenticationFailed
Description: You cannot access VMM management server scvmm.corp.usl.in.
Details: Category: Critical
Message: System.ServiceModel.Security.SecurityNegotiationException
Description: A call to SSPI failed, see inner exception.

Category: Critical
Message: System.Security.Authentication.AuthenticationException
Description: A call to SSPI failed, see inner exception.

Category: Critical
Message: System.ComponentModel.Win32Exception
Description: The target principal name is incorrect

Regards

Hi Faheem,

If you open the VMM console on the App Controller server are you able to successfully connect to the VMM server?

I am expecting that the VMM console will not be able to connect and you will get an error similar to the one described in this post:

http://social.technet.microsoft.com/forums/en-us/virtualmachinemanager/thread/C3E5FD36-5DE2-413F-87B8-538411D8DC6D

Kind Regards,

Richard 

Hi Richard, I have just had the same issue and after reinstalling VMM, I started having some 1604 errors. Now, I can't register the VMM server from App Controller.

I tested the local console and it works fine on the app controller server. No issues. Other remote consoles also work.

Whenever I try to register the vmm server, I see this on event viewer:

Request Failed By Provider. RequestID: 6540bbdf-5110-405d-baef-8f8c2be797a9 InputUrl: /api/cloudsystems InputVerb: POST User: DOMAIn\USER ProviderUrl: DOMAIn\USER ProviderVerb: http://localhost:18622/system/InternalManagement/cloudsystems HttpStatusCode: POST ExceptionDetails: 400

 

Update to my own Post: I also noticed I couldn't apply UR3 to the machine and decided to rebuild it. The connection now works, but still can't apply UR3 (or UR1 or UR2).

Replying to my post again...just noticed that when SSO is configured, the problem is back.

Still can't apply the patch either.

Error is:

SFXCA: Failed to get requested CLR info. Error code 0x80131700
SFXCA: Ensure that the proper version of the .NET Framework is installed, or that there is a matching supportedRuntime element in CustomAction.config. If you are binding to .NET 4 or greater add useLegacyV2RuntimeActivationPolicy=true to the <startup> element.
CustomAction FixArpRegistryKeyPermissions returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 8:31:39: InstallFinalize. Return value 3.

Couldn't find anything helpful.

I have just run the Configuration Baseline analyzer and it complains about the SPNs...well, big rabbit hole. I have checked and they are supposedly right. I don't want to remove VMM just to fix that. Should be straightforward, no cluster, domain account, all very clear.

Planning to call support tomorrow, just don't know which problem I should look into first...:)

I will keep you posted.

I have fixed the patching issue by adding Framework 3.5, even though it is not a pre-req.

Still have the connection issue. Have a case open with PSS and no luck yet.

Will keep you posted.

Thank you.

Just posted to the other thread. After adding the delegation configuration to the VMM computer account as well, SSO now works like a charm.

Can't pinpoint the root cause, maybe the fact I reinstalled the server (even though I followed all the after-install steps and had PSS looking at the servers).

Hope it helps!

Jose

Thanks for the update.

I'm glad you were able to get this working.

Regards,

Richard

Hello there,

can you explain in detail which delegation you added?

thanks in advance, Marcus

I have tried to detail here at the time. Hope it is good enough to fix it. A comment on that is App Controller has been removed from the System Center technical preview, so, if I were you, I might want to look into alternatives.

http://overcast.fehse.ca/2013/10/a-trippy-experience-with-vmmapp-controller-2012-sp1/

Thank you!