[Company Logo Image] 

Home Up Contents Coffee Break Credits Glossary Links Search

 
ODBC Error Installing VMware vSphere

 

 

Home
Analysis Services
Azure
CLR Integration
High Availability
Open Source
Security
SQL Server 2008
SQL Server 2012
SQL Server 2014
SQL Server 2016
SQL Server 2017
SQL Server 2019
Tips
Troubleshooting
Tuning

ODBC Error Installing VMware vSphere.


Applies to: SQL Server 2005 Enterprise Edition, VMware vSphere 4.0, Windows Server 2008 R2.

 

Problem Description.
 

While installing VMware vSphere 4.0 on Windows Server 2008 R2, the following error appeared on screen:

VMware vCenter Server
The DSN, 'vcenter' does not exist or is not a 32 bit system DSN. vCenter Server requires a 32 bit system DSN.






We created a user DSN and a system DSN using Control panel -> Administrative Tools -> Data Sources(ODBC) but vSphere could not see those newly created DSNs.


Cause.

vSphere is requiring a 32-bit DSN to be introduced on the "Database Options" page of vSphere setup, but the application "Data Sources (ODBC)" in Administrative Tools only creates 64-bit DSNs.
 

Solution.


Please create your 32-bit DSN for vSphere using the following 32-bit ODBC Administrator Tool:

%windir%\SysWOW64\odbcad32.exe


Suggestions.

Before running vSphere setup change the recovery model of the SQL Server database you created for vSphere to be "simple".


References.

The 32-bit version of the ODBC Administrator tool and the 64-bit version of the ODBC Administrator tool display both the 32-bit user DSNs and the 64-bit user DSNs in a 64-bit version of the Windows operating system.
 



 

 

.Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.