Change Vcenter DSN from SQL 2005 native client to SQL 2008 native client

[fafa24]

Hello All.

I was trying to upgrade our Vsphere 5.5 for Windows VM to Vsphere 6.0 for Windows (latest January build).

The upgrade check failed after entering the credential for Vcenter username. The error is "Unsupported database driver".

In fact the DSN connection is using the SQL 2005.90.2047 native client. On the system is also the SQL native client 10. (Version 2009.100.2500) installed. I think this is the SQL 2008 R2 native client.

The Vcenter SQL database is on a remote SQL 2008 R2 database server.

I was trying to change the DSN to the SQL native client 10. The service started, but I saw a lot of SQL errors in the vpxd.log. I could only resolve it to revert to snapshot and restoring the SQL database.

How do I change the SQL native client for the DSN connection properly?

Thanks a lot in advance?

Edy

[rcporto · Accepted solution]

Have you removed the old DSN entry and created a new one using the new (and correct) driver ? And have you checked the registry if your change reflected there (HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Virtualcenter\DB) ?

[fafa24]

Yes I have removed the old DSN and created a new one. But I didn't check the registry.

However before doing that I only stopped the Virtual Center Server service and not all services of Vcenter. Was this a mistake and might have had an effect to my problems.

As I said I switched back to my snapshot before and also restored the SQL database.

Shall I try it again, but this time stopping all services before?

Thanks,

[fafa24]

It appears to have worked now after I disabled all services and changed the DSN drive to SQL Server Native Client 10.0. I could restart all services and Vcenter can communicate with the SQL database.

Thanks,

Edy