Warning 25098 when installing VirtualCenter 2.5
My attempt to perform a fresh VirtualCenter (VC) 2.5 Update 3 installation on Windows 2003 R2 failed with the following error:
“Warning 25098. Setup has detected that the VirtualCenter Service is not running on this system. Please wait for the service to start and then try installing VMware Update Manager and/or VMware converter again.”
Troubleshooting the ODBC connection using the SQL Native Client to the remote SQL 2005 Server and removing and reinstalling without Update Manager or VMware Converter did not help. Turns out the problem was
that the database configured on the remote SQL 2005 server was set up to use Windows NT Authentication, and as soon as a switch to SQL Authentication was made the install completed successfully.
Granted, most of my installs in the past have used SQL Authentication. This customer wanted to use domain authentication so we headed down that path. Honestly, I can’t remember if I ever knew about this requirement, but the point has become crystal clear for me now. Later, after resolving the trouble I did some research to see if I missed this important configuration information.
I could not find any mention of the necessary database authentication in the VirtualCenter 2.5 Update 3 Release Notes.
After checking the VI3.5 VC 2.5 Quick Start Guide I found on page 25 it says in a one sentence paragraph all by itself:
“Microsoft Windows NT authentication is not supported with SQL Server”.
There is not a warning sign or even a bold NOTE indication. You would think special emphasis would be made about this requirement.
It is specially noted in the VI 3.5 VC 2.5 Installation Guide on page 68:
“NOTE Microsoft Windows NT authentication is not supported with remote SQL Server.”
Finally, there is a thread on the VMTN Communities Forum that discusses the Warning 25098 and the resolution.