Reply to Message

View discussion in a popup

Replying to:
stanj
Enthusiast
Enthusiast

I am having the same problem (I think).

I am upgrading to vSphere 4.

We are using a remote DB for vCenter and Update Manager that is SQL Server 2005.

I have upgraded the vCenter to 4.0 and installed the new 4.0 client.

I also installed Converter Enterprise 4.0 and enabled the plugin.

I created a new DSN connection to our SQL Server 2005 DB using SQL Native Client driver that

matched the old Upd Mgr connection that used the SQL Server driver. The test connect works to the SQL Server 2005 DB connecting with Windows NT authentication using the network login ID.

I installed Update Manager 4.0 from the CD and the service is running.

When I go to install Update Manager the plug-in in vCenter, I get an error –

There was an error connection to VMware vCenter Update Manager Database temporarily unavailable or network problems.

This is the same SQL Server database that vCetner is using and the DSNs are configured the same.

It appears during the plug-in installation, Update Manager is trying to connect to the SQL Server DB but fails..

I have tried uninstalling Update Manager and client and reinstalling.

When I reconfigured the DSN to use SQL Authentication, I entered the SQL Server DB User and the password.

The test connect works. I saved it. But, if I go back and do a reconfigure, the password field is blank, so I am not sure what is going on.

Any ides what may be happening or a suggestion to try?

thanks

Stan

Reply
0 Kudos