VMware Cloud Community
bg74
Contributor
Contributor
Jump to solution

vCenter connects to SQL Server fine with 64-bit DSN but won't connect with 32-bit DSN

Created a 64-bit and 32-bit System DSN on vCenter server using SQL Server Native Client 11.0 and exact same settings pointing to database on a SQL Server 2012 box.  The 64-bit DSN connects fine and the 32-bit DSN fails to connect.  Can anybody give some pointers as to what the issue might be?  I've never seen this before.  They point to same database and use same local SQL account.

TIA

Reply
0 Kudos
1 Solution

Accepted Solutions
bg74
Contributor
Contributor
Jump to solution

The fix was to turn on the SQL Server Browser service on the SQL box - it is disabled by default in Windows 2012 with SQL Server 2012..  This really should be documented by VMWare.

View solution in original post

Reply
0 Kudos
9 Replies
corvettefisher
Enthusiast
Enthusiast
Jump to solution

32Bit DSN for vCenter hasn't been an option since 4.0 I believe, vCenter 5.x requires a 64Bit DSN, while VUM still resides on a 32Bit DSN

Reply
0 Kudos
bg74
Contributor
Contributor
Jump to solution

Uh, that's all understood.  We're unable to install UM on one of our vCenters (5.5 u1a) because of this issue and that's why I'm asking.  In all the UM installs I've done in the past, I've NEVER seen this before and hoping somebody might have an inkling as to what might be going on.

Reply
0 Kudos
rcporto
Leadership
Leadership
Jump to solution

Check if this KB helps: VMware KB: VMware vSphere Update Manager 5.x fails to start when using SQL Server 2012

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
Reply
0 Kudos
bg74
Contributor
Contributor
Jump to solution

Thanks, but doesn't help.

Reply
0 Kudos
rcporto
Leadership
Leadership
Jump to solution

What is the version of SO running vCenter Update Manager ?

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
Reply
0 Kudos
bg74
Contributor
Contributor
Jump to solution

OS is Windows Server 2012 R2

Reply
0 Kudos
rcporto
Leadership
Leadership
Jump to solution

The KB articles says:

  • With Windows Server 2012 use SQL 2008R2 SQL Native Client 10.0 when connecting against a SQL 2012 Server.


But you told me that you're using Native Client 11.0, do you have tried the Native Client 10.0 ?

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
Reply
0 Kudos
bg74
Contributor
Contributor
Jump to solution

The KB's driver suggestion was meant as a work-around for a problem that was corrected before the current 5.5 u1a

Reply
0 Kudos
bg74
Contributor
Contributor
Jump to solution

The fix was to turn on the SQL Server Browser service on the SQL box - it is disabled by default in Windows 2012 with SQL Server 2012..  This really should be documented by VMWare.

Reply
0 Kudos