Michael Michael's Blog on dealing with VMM error 2917 : "The network path was not found" - Virtual Machine Management - Site Home - TechNet Blogs

Virtual Machine Management

Managing Virtual & Physical Computers in the Datacenter and in the Cloud

dealing with VMM error 2917 : "The network path was not found"

dealing with VMM error 2917 : "The network path was not found"

  • Comments 1
  • Likes

This error is one of the most difficult to diagnose errors in a customer environment. If you are hitting this issue when trying to install the VMM server component, here are a few things to try out.

-First, run "gpupdate /force" on your VMM server and reboot and try this again
-If that does not work, can you remove the machine from the domain, reboot, and join again. Then try installing VMM again.

If the above do not work and you are still getting the same error, try the steps from the VMM troubleshooting guide for this error message. (highlight the table below to see the message if it does not display correctly in your screen)

VMM server setup fails with error 2917: "The network path <file name> was not found on the <server name> server."

Or WinRM error: "The network path was not found."

1.     The user name or password specified is not valid.

2.     The credentials used to set up VMM do not belong to a domain with a two-way full trust with the domain of the VMM server.

3.     There are issues with either the Kerberos tickets or the Service Principal Name (SPN) for the computer.

For causes 1 and 2, log in with credentials on the same domain as the VMM server, or with credentials on a domain that has a full two-way trust with the domain of the VMM server, and then try setup again.

For cause 3, purge the Kerberos tickets using kerbtray.exe, available at http://go.microsoft.com/fwlink/?LinkId=93709. Then reset the SPN for the VMM server using setspn.exe with local system credentials. Setspn.exe is available from http://go.microsoft.com/fwlink/?LinkId=93710. To start a local system process, use at.exe. For example:

Copy Code

At.exe <time in the future, such as 10:26> /interactive cmd.exe

If this does not work, make the computer a member of a workgroup instead of a domain, restart the computer, and then join the computer to the domain again.

If nothing so far works, and if the machine you are trying to install VMM is also a domain controller, try the following:

-First, create a new domain admin account and name it VMMAdmin.

-Now, log in into the VMM server using that account and try to install VMM.

good luck - if everything fails up to here, try posting your specific issue to the VMM Forums or open a case with Microsoft Product Support (CSS or PSS)

 

 

Comments
  • SCVMM must be installed on a system in the domain. This isn’t a big deal in most environments, but if