VMWare Vsphere update manager - error 1067 - won't start
Hi guys
My VCenter 5.0 server has gone a bit mad and the VMWare Vsphere update manager service will not start at all, it keeps giving me a 1067 error. Anyway I've been through the various KB's on the VMWare web site and a few other blogs and can't figure it out at all.
What I am wondering is would it be simpler to just scrap the current VCenter essential server and create a new one from scratch or will this cause issues and also is the install really as easy as the below VMware Youtube video?
https://www.youtube.com/watch?v=J0pQ2dKFLbg
Many thanks in advance
My VCenter 5.0 server has gone a bit mad and the VMWare Vsphere update manager service will not start at all, it keeps giving me a 1067 error. Anyway I've been through the various KB's on the VMWare web site and a few other blogs and can't figure it out at all.
What I am wondering is would it be simpler to just scrap the current VCenter essential server and create a new one from scratch or will this cause issues and also is the install really as easy as the below VMware Youtube video?
https://www.youtube.com/watch?v=J0pQ2dKFLbg
Many thanks in advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
did you check the connectivity from vc center to database.
see if you can restart the database service where the update database manager you kept.
and pls confirm if this is stopped from starting..then its better to install fresh setup and before proceeding take back.
what credentials you choose to connect with update manager database. ?
please share the output
see if you can restart the database service where the update database manager you kept.
and pls confirm if this is stopped from starting..then its better to install fresh setup and before proceeding take back.
what credentials you choose to connect with update manager database. ?
please share the output
ASKER
Thanks for all the advice.
In answer to the questions;
I've had a look through the logs and there were a few windows updates installed prior to the issue so I'm looking into them
The ODBC connection is working fine. Also my passwords for the Vcenter to host (another KB from VMware) are 345 characters in length so should be good.
My plan;
Plan A
Try un-installing the windows updates to see if they are at fault (I don't think this will fix it, call me sceptical)
Plan B
I've taken a backup of the SQL DB's and will also take an off-line copy of the mdf and ldf files just to be sure.
I'm then going to restore the VCenter from a bare metal backup
Then restore the SQL DB's
In answer to the questions;
I've had a look through the logs and there were a few windows updates installed prior to the issue so I'm looking into them
The ODBC connection is working fine. Also my passwords for the Vcenter to host (another KB from VMware) are 345 characters in length so should be good.
My plan;
Plan A
Try un-installing the windows updates to see if they are at fault (I don't think this will fix it, call me sceptical)
Plan B
I've taken a backup of the SQL DB's and will also take an off-line copy of the mdf and ldf files just to be sure.
I'm then going to restore the VCenter from a bare metal backup
Then restore the SQL DB's
ASKER
OK, as I though, Plan A didn't work... Onto Plan A.5 - try an install of Vcenter Server over the current install to see if that repairs it
Failing that Plan B
Failing that Plan B
ASKER
OK so Plan A.5 worked, I uninstalled the VCenter Server stuff and reinstalled it all and she's alive. I did have a moment when I couldn't remember some of the authentication settings, but a few attempts later and I nailed it.
Now I'm going to leave it for a few days and see if it holds together, it's running sweet as a nut right now, and then install some of those lovely Windows updates.
Now I'm going to leave it for a few days and see if it holds together, it's running sweet as a nut right now, and then install some of those lovely Windows updates.
so your issue solved ?
ASKER
Yes the uninstall/reinstall fixed the issue
It's often much easier to quickly uninstall and re-install, to fix and issue, rather than try to recover a broken installation.
ASKER
So true. In fact I've now build out a brand new VCenter 5.5.0 Update 1a server, transferred the DB's and updated the ESXi's.
Have your checked your Vmware Update Manager ODBC connection?