Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

vCenter Single Sign On fails to connect to a Microsoft SQL instance (2039092)

Symptoms

  • During the installation vCenter Single Sign On fails to access a remote Microsoft SQL 2008 R2 database.
  • You may see the errors:
    • Login failed for user 'xxx'
    • No Database Name provided

  • Multiple instances are running on the same Microsoft SQL Server

Cause

By default, the installer tries to access default MS SQL port 1433. However, only the default instance of SQL Server uses this port. By default, all SQL named instances use a dynamic port.

Resolution

To resolve this issue, set the port for the instance to a static port.
 
To set the port for the instance to a static port:
  1. Open the Microsoft SQL Server Configuration Manager.
  2. Navigate to SQL Server Network Configuration > Protocols for the instance name.
  3. Double-click TCP/IP.
  4. Click the IP address tab and scroll to the bottom where you see the dynamic port used by the instance.
  5. Change the port to a static port.

    Note: If it is a dynamic port, it may change if the server is rebooted or if the service is restarted. VMware recommends manually setting a static port number for the instance.

  6. Restart the SQL instance to apply the change.

    Note: From the SSO installer, you do not to specify the port anywhere. The instance accesses the database located in the instance using the configured port.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 4 Ratings
Actions
KB: