Cannot create a 64 Bit DSN on Windows Server 2008 64bit SP2

[jaturley]

I am attempting to install vCenter server 4.1 on a Windows Server 2008 64bit SP2 server. When I get to the step in the installation where it asks for the DSN the installer can not find the DSN I have created and tells me to create a 64bit DSN. I am using the ODBC data sources utility in adminstrative tools to create the DSN. I have also attempted to create the DSN with the ODBC utility availiable inside the sysWOW64 directory. During the DSN creation I am only given one choice for a driver:

Name: SQL Server Version:6.00.6002.18005 Company: Microsoft Corporation File: SQLSRV32.DLL DATE: 4/11/2009

With the 32 in the file name that looks like it is a 32 bit driver. Any ideas? Thanks

[RParker · Accepted solution]

You might try install the SQL NATIVE version of the drivers that ARE 64-bit. That might help.

[RvdNieuwendijk]

From the VMware ESX 4.1 and vCenter 4.1 Installation Guide:

Create a 64-Bit DSN

The vCenter Server system must have a 64-bit DSN. This requirement applies to all supported databases. By default, any DSN created on a 64-bit system is 64 bit.

Procedure

1 Install the 64-bit database ODBC drivers on your Microsoft Windows system. The default installation location is C:\Program Files\VMware\Infrastructure\VirtualCenter Server.

2 Click Control Panel > Administrative Tools > Data Sources (ODBC).

3 Use the application to create a system DSN and test the connectivity.

The system now has a DSN that is compatible with vCenter Server. When the vCenter Server installer prompts you for a DSN, select the 64-bit DSN.

Did you create a system DSN?

Regards, Robert

[jaturley]

Where can I get these drivers?

[RvdNieuwendijk]

You can download the Microsoft SQL Server 2008 Native Client from Microsoft SQL Server 2008 Feature Pack, August 2008. Somewhere in the middle of the page there is a section "Microsoft SQL Server 2008 Native Client" with links to the msi installer files.

[RLX]

I thought I had this down but apparently not. I downloaded the x64 version of the SQL Native client and installed it.

I opened c:\windows\syswow64\odbcad32.exe

I created a DSN using the native client.

VCenter 4.1 still complains that I do not have a valid 64bit DSN. Any suggestions?

[RvdNieuwendijk]

With c:\windows\syswow64\odbcad32.exe you create a 32-bits DSN. You should use c:\windows\system32\odbcad32.exe to create a 64-bit DSN.

[RLX]

That's counter-intuitive to me but it did work. Thank you much.

[RvdNieuwendijk]

WOW64 stands for "Windows 32 on Windows 64", and it contains all the 32-bit binary files required for compatibility. If you need a 32 bit Windows application you have to run it from the C:\Windows\SysWOW64 directory. If you need a 64 bit Windows application you have to run it from the C:\Windows\system32 directory which is the default on 64 bits Windows. I think it also a bit confusing but this is the way it is.

[ArildS]

I have the same problem. My problem may be that I have hazarded the use of SQL Server 2008 R2 which is not yet supported. The installer should however see the DSN? Or is the driver unsupported too? Anyone tried this yet?

The SQL server driver I create the DSN with is: V6.01.7600.16385. Optionally I can use the SQL Server Native Client V10.0 (V2009.100.1600.01)

I create the System DSN with c:\windows\system32\odbsad32.exe

Btw: The reason I use the SQL 2008 R2 is that the SQL 2008 media does not install on Win 2008 R2 unless I slipstream in a service pack, which I prefer not to do unless I really have to.

[imsochobo]

Hi

I just installed a fresh sql server instance.

windows server 2008 R2 datacenter (don't ask about the licence, was around) sql server 2008 R2
created DB.

vcenter.
sqlncli.msi from link above. installed. (for 2008 -> 2008R2 = http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52 )

created system DSN

running vcenter 4.1 fully up and running, did it just not with the help of that native client, not a huge mssql guy so i always forget it, and only set it up for lab purposes.

But bottom line, it works without any tinkering other than installing native client.

[sheredia12]

This thread was super helpful. I'm performing the migration myself and ran into the same problem on a Windows Server 2008 R2. My solution was to download the 64bit native SQL client for SQL Server 2005 and configure the system DSN using this specific driver. Our vCenter Server database is currently on a Windows Server 2003 32bit and hope to migrate that as well in the near future.

[JesterJeff69]

side note... while all this is good... a little note to keep in the back of the mind.. you must exit the vcenter install if you started it and got the message..

i recreated the dsn about 6 times... and clicked the dropdown in vcenter install and the dsn wasnt there..

so i closed out of the installer.. ran it again and wooooot... sql native listed....

so thanks guys.. im up and running due to this thread too...

[jp83]

Guys,

Here is the solution.

2008 R2 needs to install  the "Microsoft® SQL Server 2008 R2 Native Client" . You can download it from below link.

http://www.microsoft.com/download/en/confirmation.aspx?id=16978

Once you open the link  search "Microsoft® SQL Server® 2008 R2 Native Client" and download the exe (X64 Package (sqlncli.msi)
and  install it. Now you will able to see SQL Server 2008 R2 Native Client drivers in ODBC - System DSN. Create your DSN and Install your VC.

thanks,

Jagdish