Symptom:

Virtual Machine Manager cannot process the request because an error occurred while authenticating <YourServerName>. Possible causes are:
1) The specified user name or password are not valid.
2) The Service Principal Name (SPN) for the remote computer name and port does not exist.
3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains. Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available at http://go.microsoft.com/fwlink/?LinkId=93709. Then, reset the SPN for <YourServerName> by using setspn.exe available from http://go.microsoft.com/fwlink/?LinkId=93710. If this still does not fix the problem, make <YourServerName> a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again.
ID: 2917. Details: The network path was not found (0x80070035)

ID: 2917

 

Root Cause:

2-way trust is required for cross-domain during the installation. It is flowing through a VMM->SQL->DC path authentication verification.

Solutions:

  • Have a 2-way domain trust. Most of time this could be an issue due to the nature of setting up these non-2-way trust domains. If this is the case, you can have the following 2 workarounds
  • Use a user from the same domain as the server to do the installation
  • Change SQL server’s service account to the (other) domain account from “Network Service”
Advertisements