Just another standard maintenance, upgrading vCenter from 5.0 U2 to U3. Nothing special to see here. Oh wait, it failed? CRAP. Restore database, try again. Can't build vCenter Repository?! Crap, restore database, try again. AGAIN!!? Long story short, SQL Authentication specified in the ODBC connection was experiencing intermittent connection issues. Windows integrated was much more stable.
Opened ODBC --> Configure ODBC connection --> Enter SQL Credentials --> Next... wait --> Error (See below for errors) --> Click OK --> Select Next again --> successfully connects and tests successfully. Repeat...
This problem was likely due to the firewall in-between the vCenter server and SQL server. As to what that problem was exactly, I have no clue.
Changed ODBC connection from SQL Authenticated User to Windows Integrated. For this to work, you have to change the following:
- Change the following services to start as a windows service account that has dbo control over the vCenter database.
- VMware VirtualCenter Server
- VMware VirtualCenter Management Webservices
- VMware vSphere Profile-Driven Storage Service
- Change ODBC connection from SQL authenticated to Windows Integrated.
- Open Registry and go this path: HKLM/Software/VMware, Inc/VMware VirtualCenter/DB
- Blank out entries for 2 and 3 (SQL username and crypted password)
- Modify vcdb.properties file to enable integrated authentication. (Assuming you are using MSSQL)
- vcdb.properties file is normally located under C:\programdata\VMware\VMware VirtualCenter\
- By not changing the vcdb.properties, you may end up w/ errors for the License Services and vCenter Storage Monitoring Service.
- vCenter Storage Monitoring Service: Service initialization failed.
- License Services: Unable to get license usage data
sqlstate 08001 Server Error 0
Microsoft SQL Server Native Client Version 10.50.1600
Running connectivity tests...
[Microsoft][SQL Server Native Client 10.0]Unable to complete login process due to delay in opening server connection