VMware Virtual Center service won't start after upgrading to 5.5
no issues during install- everythingelse seems fine
ASKER
i did not see a message as such- did not get any error messages during the install- everything went smooth.
Yes, it does, and then does not work!
Complete a new installation.
Complete a new installation.
Check the following
1) Check if SSO and vCenter Inventory services are running fine
2) Check for the database connectivity
3) Check vpxd logs and see if you find any message related to error
1) Check if SSO and vCenter Inventory services are running fine
2) Check for the database connectivity
3) Check vpxd logs and see if you find any message related to error
Since vSphere's dissemination, the main reason for vCenter services to not start is typically issues with the vCenter DB connectivity - either bad or mistyped user pwd, SQL Native Client is not used or not correct version, or a simple incompatibility due to some version not being on VMware's HCL.
~coolsport00
~coolsport00
or VMware vSphere 5.x upgrade breaks your installation!
ASKER
I heard that last comment in a big way- so I am trying to roll back at this point-
anybody have any ideads on how to rollback from esxi 5.5 to 5.1- I have done a lot of vmware upgrades starting from 4.7 and I have never had a problem until this one. Sometimes it aint broke so dont fix it- vsphere clinet worked great why change it to web interface? every app taht has done this has made the app worst- not better
anybody have any ideads on how to rollback from esxi 5.5 to 5.1- I have done a lot of vmware upgrades starting from 4.7 and I have never had a problem until this one. Sometimes it aint broke so dont fix it- vsphere clinet worked great why change it to web interface? every app taht has done this has made the app worst- not better
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok- I am close to being here. I have oen host that would not upgrade and one host that was new. They are both back at 5.1. I have reinstalled 5.1 Vcenter server. I have it up and running. I have those 2 hosts added. The 3rd host had 5.5. When I tried to change it said it would repartition the disk. Wouldnt this wipe out the VM's taht are on that host? How can I get those VM's off the host? This is a replication site so all of the VM's but one are standbys andcan be recreated. My concern is my AppAssure5 backup server. If I lost that I will have to recreate all of my replication jobs- app. 2TB. There must be a way to do this- HELP!?!?
ASKER
oh- I thought I exported the vcenter server DB- but I can't find it
if you re-install ESXi, it should allow you to preserve the current VMFS.
but I would always recommend a backup of VMs, before any change to production server.
but I would always recommend a backup of VMs, before any change to production server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys - back up and running. Not sure if I would try upgrading to 5.5 any time in the very near future
I wouldn't either there are terrible issues with 5.5!
I would wait for U1 at least, unless you desperately need the new features!
But Computer Administrators always want the latest......and you cannot stop them experimenting!
I would wait for U1 at least, unless you desperately need the new features!
But Computer Administrators always want the latest......and you cannot stop them experimenting!
My rule of thumb for ANY software upgrade is to wait for U1 or SP1 (whatever a vendor calls it), whether it be OS, App, other. I don't trust GA versions...
~coolsport00
~coolsport00
ASKER
Guys- I agree with you both- truly I had the 5.1 software at my home office and I left it- when I got to Jacksonville I realized I left it and when I when to download - there was new version. Decided to try ti out- wightout research or anything. First time in a 20 year IT career.
Make a mistake once- will never make it again. Theres a reason why I have always waited to a second release and always done research prior to- cost me and extra day to rebuild the whole thing as well as day trying to make it work.
Make a mistake once- will never make it again. Theres a reason why I have always waited to a second release and always done research prior to- cost me and extra day to rebuild the whole thing as well as day trying to make it work.
We do not move versions of vSphere, unless really necessary, we are fortunate, we may many labs, R&D Areas, and Production.
We still run, ESX 2.53, 2.54, ESXi 4.1, ESXi 5.0 in Production.
New Clients may decide to take version 5.5, if this is there first time with vSphere, others are very cautious, and take many months to upgrade.
Uprgades of 2.53, 3.x, 4.1 and 5.0 (server and vCenter Server) used to upgrade seamlessly, with as much as taking 30-60 minutes to complete an upgrade, but since the introduction of SSO (which we blame alot!), upgrades now seem to be breaking weekly at many client sites...
We seem to spend more time, defending VMware for upgrade disasters, and rollback. than actually doing the upgrades at present!
We still run, ESX 2.53, 2.54, ESXi 4.1, ESXi 5.0 in Production.
New Clients may decide to take version 5.5, if this is there first time with vSphere, others are very cautious, and take many months to upgrade.
Uprgades of 2.53, 3.x, 4.1 and 5.0 (server and vCenter Server) used to upgrade seamlessly, with as much as taking 30-60 minutes to complete an upgrade, but since the introduction of SSO (which we blame alot!), upgrades now seem to be breaking weekly at many client sites...
We seem to spend more time, defending VMware for upgrade disasters, and rollback. than actually doing the upgrades at present!
I would recommend
1. Complete a fresh installation.
2. Call VMware Support and log a support call.
Did the upgrade state it upgraded your database?