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
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.
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
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.
Check if this KB helps: VMware KB: VMware vSphere Update Manager 5.x fails to start when using SQL Server 2012
Thanks, but doesn't help.
What is the version of SO running vCenter Update Manager ?
OS is Windows Server 2012 R2
The KB articles says:
But you told me that you're using Native Client 11.0, do you have tried the Native Client 10.0 ?
The KB's driver suggestion was meant as a work-around for a problem that was corrected before the current 5.5 u1a
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.
