Suggestions for fixing scvmm error 2917

Table of Contents

It appears that some users have encountered the scvmm 2917 error message. This problem can occur due to a number of factors. We will discuss this below.

Updated

1. Download ASR Pro

2. Run the program

3. Click "Scan Now" to find and remove any viruses on your computer

Speed up your computer today with this simple download.

The Virtual Machine Manager process could not process the request because an account error occurred while authenticating . Possible sources:
1) The username or password provided by the user is usually invalid.
2) The Service Principal Name (SPN) for the remote computer name and city does not exist.
3) The client and one console are in different areas. Therefore, both domains do not have full two-way trust with a specific account in a domain that has good two-way trust with the domain associated with the VMM server, and then try again. If this works, be sure to remove the Kerberos tickets on VMM through the server using kerbtray.exe available at http://go.microsoft.com/fwlink/?LinkId=93709. Then reset the SPN for using the setspn.exe file available at http://go.microsoft.com/fwlink/?LinkId=93710. If this still doesn’t resolve the issue, is a member of a workgroup that joined the domain instead, restart your computer, join the current domain, and try to resolve the issue again.
ID: 2917. Details: Network path never e was (0x80070035)

scvmm error 2917

Two-way trust is required during installation in order to be cross-domain. Everything is authenticated by the VMM->SQL->DC path.

Based on a two-way domain. In most cases, this can be a private issue due to the nature of most of these non-bidirectional trusted domains. If it’s awesome, you can use one of the following workarounds

Use a user from the same primary domain as the server to start the installation

Change the SQL Server service account from “Network Service” to a (different) domain account

This Is An Ecosystem. Let The Community Learn, Work And Collaborate Together.

If you try to update or install the SCVMM agent, contact your HyperV hosts managed by System Virtual Center Machine Manager and you may encounter the following error.

Error (410)
Failed to install agent
Unknown (0x80041003)

Recommended action on error
Please try again. If the critical situation persists, install the agent locally or add a managed one tocomputer.

To resolve this issue, your company must add BOTH the hostname (computer) of the SCVMM server and the login of the account you want to use to log in to the agent to the ADMINISTRATORS group of the intended use of the HyperV host.

For example, if your SCVMM server is named MyCo-VMM and you use a friend account named BigAdmin to deploy the SCVMM agent on a Hyper-V host named YYC-HyperHost1, you:

Connecting to YYC HyperHost1

< li>Start COMPUTER MANAGEMENT

Expand LOCAL USERS AND GROUPS > GROUPS
Double-click ADMINISTRATORS
Click the ADD button

< li>Type BIGADMIN and click OK

Click the ADD button
Click the OBJECT TYPES button
Click COMPUTER and check OK
Enter MYCO -VMM and click OK.
Click OK
Toback up your SCVMM server (MyCo-VMM for this test only) and try to install and update the agent again

Another note about hosting the SCVMM agent:

Be sure to migrate all your VMs from the host in question as the agent loads a network adapter driver that can remove personal VMs during installation
In the host settings, the HyperV server runs Kerberos as the AUTH PROTOCOL for live migration.
Make sure the DCOM service is running
Give the deployment user (BigAdmin in this example) full control over WMI and DCOM see the following errors:
- VMM does not have proper access to read/write to resource C:Windowssystem32vmguest.iso, this is ode r;
- V MM does not have proper access rights to resource C:Windowssystem32q mgr.dll
Fixed Fixed and re-patched host servers

BUT”

Home Virtualization » Microsoft Hyper-V » Unable to addDevelop a Hyper-V host in Virtual Machine Manager? Do it

Adding a Hyper-V host to System Center Virtual Machine Manager should be easy. However, sometimes things don’t work as they should and the process of adding hosts fails. In that case, I wanted to show you some possible roots over time. Typically, when VMM cannot add the Hyper-V host, the Tasks window displays a message similar to the following figure. As you can see, this window can display the main error message, the error code, and your own short description of the error.

At first glance, this particular problem seems relatively simple to you. Finally, the error set (2940) is the file transfer error code. In addition, the description of the error indicates which of them failed to transfer the file and which should be checked to ensure that the HTTP service is running and that non-firewall rules are blocking traffic. HTTP.

Mistakes Can Be Misleading

However, over time, I got used to the fact that VMM error messages can be misleadingnie. If you don’t take the time to fully understand what’s going on, you can spend a lot of time looking for the wrong problem. So let me show you what I mean.

The error message displayed in the screenshot above seems to indicate that an HTTP connection could not be established against the Virtual Machine Manager server and I would say that the Hyper-V host is being added. However, if you look at the Details tab, we can see the actual steps that were trying to add the Hyper-V host part to VMM. Step 1.2 dealt with installing the agent in the Hyper-V group. This step has been completed successfully.

In fact, a quick look at checking the Hyper-V host shows the presence of the agent because it was installed. Installed. The date indicates that this is a new instance pointing to the agent and that the agent was no longer there. So, is this all happening?

If we take a close look at the task window, we can see that the details panel indicates that a problem occurred while adding the main Extensions per Hyper-V host. Hence, this is an area where they will be required to focus our troubleshooting efforts.

Updated

Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!