Update Manager Error after Migrating Database to different instance.

[portlandjoe]

Hey everyone,

I migrated the SQL Express databases to the named instance of SQL Standard.  It's all 2008 R2.  The three databases migrated were VCenter, VirtualManagerDB, and VSphereUpdateManager.  The domain accounts in SQL were migrated to the new box instance.

Now I am receiving this error trying to open VSphere:

Call "ServiceDirectory.QueryServiceEndpointList" for object "ServiceDirectory" on vCenter Server "192.168.123.160" failed.

Can anyone help me figure this one out?  This is a VCenter 5.0 installation on a Windows 2008R2 Server that is also running SQL Server 2008 R2 standard with an express instance and an named instance.  I've migrated from the express instance in order to overcome the 4GB limit on the express instance.

Thanks,

Joe

[Troy_Clavell]

by any chance do you have the Routing and Remote Acess Service running on your vCenter Host OS?

[portlandjoe]

Nope, it is disabled.

[portlandjoe]

I rebooted the VCenter server, and tried again to connect. (I restarted the server previously with a different result).  Now the VSphere client opens, but I get this error:  There was an error connecting to VMware vSphere Update Manager - [ip.address:443].  Database temporarily unavailable or has network problems.

So now at least we can get to the VCenter server, but it's having a hard time finding the update manager database.  I did move that database.  There wasn't a ODBC entry for that one, while there were ODBC entries for the other two.

Any ideas how I can direct VCenter to the new location for the db?

Thanks,

Joe

[Troy_Clavell]

There wasn't a ODBC entry for that one, while there were ODBC entries for the other two.

you'll need to create an ODBC connection for VUM too.

[portlandjoe]

How do I know the exact name and settings I should use?

[Troy_Clavell]

a system DSN will need to be created using the SQL Native Driver.  For use the DB Name for the Name: and Description: fields.  For Server point to your SQL DB Depending on you authentication method use SQL or Windows. follow the prompts and test connection.

[portlandjoe]

Okay so I was wrong, it must not be ODBC.  The two OSDB connections I have are for Vcenter and VSphereUpdateManager, and both test succesfully.

Thanks,

Joe

[kjb007 · Accepted solution]

Upd Mgr is using a 32 bit DSN, so you'll need to use C:\Windows\SysWOW64\odbcad32.exe to access/view/modify the correct DSN on Win2k8

-KjB

[Troy_Clavell]

see also, http://kb.vmware.com/kb/1039089

[portlandjoe]

Thanks everyone.  This was an issue with the 32-bit ODBC missing.  Thanks so much!