What 32 bit DSN utility to use?

[mchenpdx]

I'm kind of lost here.

I'm trying to install vCenter onto a 32 bit Windows 2008 VM with remote 2008 MS SQL DB on another 32 bit Windows 2008 VM. Why? Because my HW (Power Edge 2850) does not support 64 bit VM.

I created a DSN using the 32 bit DSN utility and it can connect to the remote 2008 MS SQL DB fine; however, the vCenter can't find the 32 bit DSN I created.

I read a lot of postings talking about creating DSN using 32 bit DSN from a 64 bit OS but havn't heard anything related to my scenario.

Can any one give me some pointers?

Thanks!!

[admin]

If a DSN has been set up through Start > Administrative Tools > Data Sources (ODBC) the vSphere installer won’t be able to use this DSN.

The 64-bit ODBC Administrator tool can be invoked from Control Panel

to manage user DSNs and system DSNs that are used by 64-bit processes,

but for 32-bit datasources, the 32-bit ODBC Administrator tool is used

for Windows on Windows 64 (WOW64) processes.

To set up a 32-bit DSN launch the 32-bit version of the Data Source Administrator. It is located at:

%systemdrive%\Windows\SysWoW64\Odbcad32.exe

The vSphere installer will then be able to detect the DSN and continue the installation.

Please see Microsoft KB article for more information.

Rick Blythe

Social Media Specialist

VMware Inc.

[mchenpdx]

The problem is that I'm not installing vCenter on a 64 bit VM, so, there is no %systemdrive%\Windows\SysWoW64 folder at all.

I don't know what vCenter installer expects when installing on a 32 bit VM? Shouldn't the 32 bit ODBC administrator tool created DSN be sufficient?

[admin]

Did you make sure to use a System DSN?

Rick Blythe

Social Media Specialist

VMware Inc.

[mchenpdx]

Yes, I sure did.

[maxel]

You have to use the native Sql driver

driver is part of Sql 2005 Feature Pack

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=536fd7d5-013f-49bc-9fc7-77de...

[Texiwill]

Hello,

Moved to the vCenter Server Forum.

Best regards,

Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]

[mpolz]

Did the post have a resolution? I am also having a similar problem.

[mchenpdx]

Well, my problem has been resolved.

The reasone the DSN I created can't be found by vCenter installer is because I created DSN with 'SQL Server' driver specified instead of 'SQL Native Client' driver. Why? Because I didn't have the MS SQL Native Client installed on my vcenter node (I'm using remote 2008 MS SQL DB instead the bundled 2005 MS SQL Express).

I have to install the MS SQL native client first before I can create a DSN that vCenter installer is looking for. Once done, I was able to install vCenter without issue.