I've had this happen when using the vSphere client locally on the vc server and connecting to localhost/127.0.0.1.
In my case, just connecting to the public vc name or ip helped. -Anders On Tue, Feb 2, 2010 at 9:29 PM, Michael Leone <[email protected]> wrote: > On Tue, Feb 2, 2010 at 2:56 PM, Garcia-Moran, Carlos > <[email protected]> wrote: > > YES VC is backwards compatible the most current will manage your hosts. > > Hrm. Must have done something wrong. I found my 2.5 Update 4 > installation media, and ran the Update Manager install from there. I > created a new database, and a new login, and configured the DSN, all > according to the Update Manager installation PDF. It all seemed to > work. The "Test Connection" was successful. > > I then saw the plugin available in the VI Client (yay!), downloaded > it, and told it to enable. And then it says: > > The VMware Update Manager cannot accept requests now because > VirtualCenter server cannot be reached, or the database cannot be > reached, or it is in the process of stopping > > Obviously, it can reach the VCenter. The Update Manager service says > "Started". So that only leaves me with database can not be reached ... > > I created the SQL user as "domain/loginname", gave it "public" and > "db_owner" for the "VMwareUpdateManager" DB I created. Has the same 2 > rights for the msdb DB (under "User Mapping"). > > Dunno where I went wrong, or where to go from here ... > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
