Comments on: Configured DSN is pointing to an unsupported ODBC driver error while upgrading to vCenter 4.0

By: admin

admin — Mon, 13 Dec 2010 20:08:00 +0000

Glad it worked for you Artem.

By: Artem

Artem — Fri, 03 Dec 2010 07:47:02 +0000

Thanks! Also delete old DSN, create new system DSN !warn.! – driver of DSN SQL Native Client!!!!)

By: chuy guizar

chuy guizar — Wed, 09 Jun 2010 18:21:05 +0000

Jack

This issue occurs if the ODBC connection is using an outdated SQL Native Client. download newone , it works for me!!

By: admin

admin — Fri, 14 May 2010 22:23:44 +0000

Thanks for sharing your findings.

By: Michael Chan

Michael Chan — Mon, 03 May 2010 04:15:26 +0000

You have to go into the Registry and change a couple entries as well.

I needed to do this to get the updater and Vcenter service to install correctly. For some odd reason changing the DSN doesnt update the registry settings that Vmware picks up.

Go search for the DSN name in the registry that you are using and you will find the old settings in there

Regards,

Michael

By: admin

admin — Thu, 25 Feb 2010 23:21:28 +0000

Hi Jack,

Are you sure the SQL Native Client service is running on the SQL Server?

Are you sure you are filling your DSN info with the right info as well?

Please update back if you find the solution.

Regards,
Eiad

By: admin

admin — Thu, 25 Feb 2010 23:16:30 +0000

Hi George,

Are you sure you have proper permissions with the user you are trying to run the upgrade with?

By: George V

George V — Wed, 24 Feb 2010 20:49:24 +0000

This link at TechRepublic explains it the best. You have to enable the .NET Framework 3.5.1 Feature when using Server 2008. You do this through Server Manager – Features. But don’t install WCF (which is added by default), or you get IIS too! (These steps are in addition to the 32-bit DSN instructions above, which are correct.)

http://blogs.techrepublic.com.com/datacenter/?p=1791

By: George V

George V — Tue, 23 Feb 2010 22:13:13 +0000

I followed your instructions and got past the ODBC error. However once the install starts I get this error:
Error 28035. Setup failed to copy DSACLS.EXE from System folder to ‘%windir%\ADAM’ folder

I’m not sure what is causing this. If I find out I’ll let you know.

By: Jack Turner

Jack Turner — Tue, 23 Feb 2010 15:22:20 +0000

This solution did not work for me. When I try to create a DSN using the SQL Native Client, I get an error that says:
“Connection failed:
SQL State: ’08001′
SQL Server Error: 87
[Microsoft][SQL Server Native Client 10.0]SQL Server Network
Interfaces: Connection string is not valid [87].
Connection failed:
SQLState: ‘HYT00′
SQL Server Error: 0
[Microsoft][SQL Server Native Client 10.0]Login timeout expired

I’ll do a search on these errors and see if I can figure out what is wrong.