Troubleshooting Installation Issues

  • Article

This topic provides guidance for troubleshooting issues that may occur when you are installing System Center Virtual Machine Manager (VMM), prerequisite software, and tools. The precise wording of an error message that you observe may differ from this catalog if your VMM installation has been updated with any hotfixes or service packs.

Some error messages contain placeholder text, such as <specified server>. The placeholder text indicates a value that VMM provides in the error message.

VMM Installation Issues

Issue Possible cause Solution

VMM Administrator Console does not open after uninstalling, followed by reinstalling.

This can happen if there is a pending restart after you uninstall. Uninstalling the VMM Administrator Console does not force a restart.
  1. Uninstall the VMMAdministrator Console.
  2. Restart the server.
  3. Reinstall the VMM Administrator Console.

Cannot open Help when running Setup remotely.

Microsoft Windows Server 2003 SP1 with security updates 896358 and 840315 includes changes to the InfoTech protocol. These changes were introduced to reduce security vulnerabilities in HTML Help and prevent opening Help remotely.

Copy the Help CHM file to the local computer, or implement the fix described at https://go.microsoft.com/fwlink/?LinkId=96640.

VMM Server installation fails with error 205: "Microsoft System Center Virtual Machine Manager 2007 installation did not complete successfully."

The computer name you entered has more than 15 characters.

Enter a computer name with 15 characters or less, and try again.

Connection to the VMM database after installation fails with error 334: "Setup could not configure the database <database name>."

There is a VMM server role already in the database. For example, if you uninstall VMM when the remote SQL service is stopped or using credentials of a non-admin, the VMM server role is not removed from the database.

Reinstall using a new database name. Alternatively, uninstall, and then reinstall to clean up the database entry.

VMM server installation fails with error 319: "The Virtual Machine Manager database was not created."

There are several reasons why database creation may fail.

1. Delete <DatabaseName>.mdf (VirtualManagerDB.mdf by default) and <DatabaseName>_log.ldf (VirtualManagerDB_log.ldf by default) if they exist. Use (C:\Program Files\Microsoft System Center Virtual Machine Manager 2007\db by default) or use a unique name for the database.

2. Ensure that disk quota management is not enabled for the drive where the database is being created.

VMM server installation fails with error 322: "Cannot locate the file SqlCmd.exe."

A previous SQL Server installation did not complete, and the registry entry is corrupted.

If you do not have SQL Server on the computer, delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server, and then reinstall VMM server.

VMM server installation using remote SQL Server fails with error 2600: "Unable to connect to the database because of a fatal database error. It is unlikely that the database itself has been damaged."

The account used to run setup does not have the sysadmin SQL role on the remote SQL Server.
  1. Uninstall VMM using Add or Remove Programs.
  2. Reinstall VMM using credentials that have the sysadmin SQL role on the remote SQL Server.

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 https://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 https://go.microsoft.com/fwlink/?LinkId=93710. To start a local system process, use at.exe. For example:

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.

Cannot open the VMM Administrator Console installed on a Domain Controller.

If you install both VMM server and the VMM Administrator Console on the same computer, the account you use to run the VMM Administrator Console must be a member of the Virtual Machine Manager Administrators group. By default, VMM server setup adds the Administrators group as a member of the Virtual Machine Manager Administrators group.

Add the account you use to run the VMM Administrator Console to the Virtual Machine Manager Administrators group on the VMM server.

Cannot uninstall Self-Service Portal with error:

"World Wide Web Publishing Service (W3SVC) is either not installed or disabled. Please make sure that IIS is present on your computer."

You cannot uninstall the Self-Service Portal if IIS is not enabled.

Enable IIS, and try uninstalling again.

Cannot install VMM Self-Service Portal with error: "An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately."

ASP.NET is not installed or is not registered correctly.

Install ASP.NET or unregister and reinstall ASP.NET and run VMM Self-Service Portal installation again.

To unregister ASP.NET from the command prompt, type

aspnet_regiis –u

To enable ASP.NET 2.0, run the following commands:

Cd\%windir%\Microsoft.NET\Framework\v2.0.50727
aspnet_regiis -i -enable

To check if ASP.NET is an allowed Web extension, follow these steps:

  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Expand the left pane, and click the Web Server Extensions node.
  3. In the right pane, verify that ASP.NET v2.0.50727 is allowed. If not, click Allow to change the status.

Cannot install VMM Self-Service Portal with error 205: "Microsoft System Center Virtual Machine Manager 2007 installation did not complete successfully."

The 32-bit version of ASP.NET is installed on a 64-bit computer.

Switch from the 32-bit version of ASP.NET to the 64-bit version of ASP.NET 2.0 according to the instructions at https://go.microsoft.com/fwlink/?LinkId=98566.

Re-installing VMM after renaming the computer fails with error 257: "An error has occurred while trying to configure Virtual Machine Manager."

SQL Server Setup will fail if you rename the computer after uninstalling VMM and then try to reinstall VMM. For details on the underlying issue, see https://go.microsoft.com/fwlink/?LinkId=88056.
  1. Uninstall SQL Server and the full SQL Server instance from the computer.
  2. Reinstall Virtual Machine Manager.
> [!WARNING] > This will result in the loss of the VMM database and all the management and configuration information. >

Remote SQL Server installation fails with error 404: "<computer name> cannot resolve with DNS."

You entered the remote SQL Server location as an IP address during setup.

To connect to the VMM database, you must manually modify the connection string using the following steps:

  1. In the registry, navigate to the following subkey: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager 2007 Server\Settings\Sql.
  2. Right-click ConnectionString, click Modify, and then change the Server= value data by deleting the IP address and replacing it with the computer name for the remote SQL Server.

Additional Resources