Export (0) Print
Expand All

Troubleshooting Setup Issues

Updated: July 29, 2010

Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2, Virtual Machine Manager 2008 R2 SP1

This topic provides guidance for troubleshooting issues with installing Virtual Machine Manager 2008 (VMM) and VMM 2008 R2 components.

Possible causes

  1. The SQL Server name that you entered has more than 15 characters.

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

Solutions

  1. Ensure that the SQL Server name does not contain more than 15 characters, and then try the operation again.

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

Possible causes

  1. A default VMM database might already exist on this computer.

  2. Disk quota management might be enabled and enforced.

Solutions

  1. Either delete the existing VMM database files and then run Setup again or run Setup again and use a unique name for the VMM database. By default, the VMM data file is named VirtualManagerDB.mdf and the log file is named VirtualManagerDB_log.ldf. By default, the VMM database files are located in the %SYSTEMDRIVE%\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data folder.

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

Possible causes

  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 trust relationship 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.

Solutions

  1. For causes 1 and 2, log in by using credentials that are on the same domain as the VMM server or with credentials on a domain that has a two-way trust relationship with the domain of the VMM server, and then run Setup again.

  2. For cause 3, purge the Kerberos tickets by using kerbtray.exe, available at http://go.microsoft.com/fwlink/?LinkId=93709. Then reset the SPN for the VMM server by 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 the command 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.

Possible causes

SQL Server Setup fails if you rename the computer after uninstalling VMM and then try to reinstall VMM. For more information about the underlying issue, see http://go.microsoft.com/fwlink/?LinkId=88056.

Solutions

Uninstall SQL Server and the full SQL Server instance from the computer, and then reinstall VMM.

CautionCaution
This will result in the loss of the VMM database and all management and configuration information.

Possible causes

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

Solutions

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 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.

Possible causes

You cannot uninstall the Self-Service Portal if Internet Information Server (IIS) is not enabled.

Solutions

If you receive the error “World Wide Web Publishing Service (W3SVC) is either not installed or disabled. Please make sure that IIS is present on your computer,” enable IIS, and then try uninstalling the VMM Self-Service Portal again.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft