You might see an error, immediately after installation of VUM (VMware Update Manager) and after installing its plugin:
There was an error connecting to VMware vSphere Update Manager –
[Server Name:443]. Database temporarily unavailable or has network problems.Here is a screenshot for reference:
This generally happens to people like me who prefer running programs under specific accounts. I always run this service under Windows Authentication like this:
The issue is that, despite entering a username and password, the service sets up under the “Local System” account as shown in the screenshot:
Effect of this is that the plug-in can’t authenticate and therefore, connect to the database.
Fix to this issue is quite simple. Immediately after installation of VMware Update Manager:
- Fire up the “Services” MMC.
- Locate the “VMware vSphere Update Manager Service”.
- Click on the “Log On” tab.
- Change “Log on as:” from “Local System account” to “This account” and add the service account you chose to run the service under.
- Once done, a dialogue box comes up, telling you about the “Log On As A Service” right being granted to that account.
Remember: You also need to restart the service for this change to take effect.
Once done, you can quite safely go to the plugin install and this time, it should work perfectly as normal!
Hope this helps!
Timely and helpful post. Thanks for sharing!
You’re welcome Frank! 🙂
Thanks!
You’re welcome 🙂
You rock man
thank you
no blog site or website was able to help me resolve this annoying problem which I had for 3 days and could not find a resolution. I tried everything every website suggested. I finally fixed the problem after digging further into the logs and determined that my database VIM_UMDB transaction log file was full. It was set to 2048. To resolve the problem I changed it to 4096 and I finally got to enable the Update Manager plugin. Now I have to resolve the transaction log filling up. I have weekly jobs set to run, however, not sure went wrong. I am still investigating. FYI:
My SQL database resides on a separate server. There were no problems with the ODBC driver connectivity from the vCenter server to the remote SQL server or the update manager service user and password, changing these did nothing to help, the real problem was the transaction log for update manager database. Hope this bit of information helped.
This worked for me thanks!
Thanks! Big !
Thanks man, I happy I found this article. Took me 5 minutes to resolve. With Vmware it would have taken me 2 days
Thank you!!! after five day of research.
Thanks for sharing, life saver
Worked perfectly for me. Good screenshots with ability to enlarge them. Thank you.
[…] checked the ODBC and it connected fine, so something was up. I found a blog post from someone who mentioned that if you are using windows authentication for the DB, then the update […]
[…] this is a “bucket” error for the web client but as I have seen a service issue with vSphere Update Manager soon after installation before, I immediately looked into “Services”. Surely enough, […]
awesome..thanks so much 🙂
This only works if your VCenter server is a Windows box. What if you have this error and you are using an Virtual Appliance?
A very good question! Unfortunately, I can’t answer that one as I haven’t seen that one yet.
Ather
Ahhh. That was the ticket. Over four years on and still a very useful and helpful blog post. You rock sir!
The trick worked for me also. Dusting of me old sandbox and testing upgrade at 6.0 level from U2 to U3J. And then VUM gave the error you have here + inability to upload images and patches. George Harrisons song “All Those Years Ago” jumps to mind as I see your blog is from 2013 but still rocking. Thank you Sir!
Your welcome! Not sure why the problem existed in the first place or why VMware didn’t fix it quickly as it doesn’t seem like a difficult one to get rid of!
Thank you, this is helpful post for me