Virtualization, Cloud, Infrastructure and all that stuff in-between

My ramblings on the stuff that holds it all together

Installing vCenter on Windows 2008 R2 x64 – There is No DSN which can be used

4 Comments Posted by on April 5, 2010

 

It’s well documented that if you want to install vCenter on an x64 Windows 2008 OS you need to create a 32-bit DSN rather than he normal x64 DSN, Jason has a post on this over at his site.

image

However – on a clean install of Windows 2008 R2 x64 you don’t get the drivers for the SQL Native Client out of the box so whatever you do, you can’t create a compatible DSN

If you have a separate VC server from the SQL server you need to install the SQL native client on your VC server otherwise it won’t work.

You can download it from this page as part of the SQL 2008 Feature pack; the direct download links are below

Microsoft SQL Server 2008 Native Client

    Microsoft SQL Server 2008 Native Client (SQL Native Client) is a single dynamic-link library (DLL) containing both the SQL OLE DB provider and SQL ODBC driver. It contains run-time support for applications using native-code APIs (ODBC, OLE DB and ADO) to connect to Microsoft SQL Server 2000, 2005, or 2008. SQL Native Client should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2008 features. This redistributable installer for SQL Native Client installs the client components needed during run time to take advantage of new SQL Server 2008 features, and optionally installs the header files needed to develop an application that uses the SQL Native Client API.
    Audience(s): Customer, Partner, Developer

You can then install this package on your vCenter server

image image

You can then follow the steps in Jason’s post to run odbcad32.exe and configure a 32-bit DSN

image

image image

Scroll to the end and select SQL Native Client (not “SQL Server”) and configure the client as required (remember to change the default database setting to the vCenter DB you created (see install guide)

image

Then restart the vCenter installation process and you will be able to select the DSN you created

image

vCenter, Windows 2008 R2 x64

4 responses to “Installing vCenter on Windows 2008 R2 x64 – There is No DSN which can be used”

  1. Steve P April 5, 2010 at 4:23 pm

    It should be noted that vCenter server is not currently supported on Windows 2008 R2. See page 18 here: http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

    I’m sure it works just fine, but you probably wouldn’t want to do that in production until VMware gets around to updating that document. Any day now would be great, guys.

    Reply
  2. Jasper9 April 6, 2010 at 6:32 pm

    it’s very important to note that 2008 R2 is not supported as an OS to run vCenter at this time.

    Reply
    • vinf April 6, 2010 at 7:56 pm

      Ah the perils of scheduled/draft posts! – I wrote this up last week and it must have set it to do a scheduled post by mistake.

      After getting past this I couldn’t get it to complete the installation – will do a follow-up post – in the meantime readers, it’s not supported and probably won’t work.

      Reply

  3. Pingback: Virtualization Short Take #38 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers

Leave a comment