Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 448
  • Last Modified:

Logon to vcenter failed after p to v

Hi All

        I have a physical vcenter server, and recently p to v to a esx 5.5 server, after converted to esx 5.5 server, when i try to logon to vcenter server in vsphere client , below screenshot message pop up, and i checked the vm services, some of the services was not started, and i tried to start one of the services, it pop up an error message (see bottom screenshot), any idea ?



1

2
0
piaakit
Asked:
piaakit
2 Solutions
 
Jon CCommented:
Hi

You won't be able to connect to vCenter if the services it requires aren't running.

Have you tried starting " VMware VirtualCenter Server" ?

Thanks Jon
0
 
Mohammed KhawajaManager - Infrastructure: Information TechnologyCommented:
Could you validate that you can see the network.  I think it could be TCP/IP related.
0
 
Paul SolovyovskySenior IT AdvisorCommented:
Had the same thing happen last week.  Wound up upgrading in place to vCenter 5.5 and worked great.  If you're already running 5.5 may want try a repair.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
piaakitAuthor Commented:
Sorry is 5.1, it works well on the physical vcenter server, once p to v to esx 5.1 , and try to login vcenter in vsphere client, it can not login and some of the vm services won't be able to start, see the second screenshot for specific services, or as above mention I can in place upgrade to 5.5 ? But the two vm hosts added to vcenter is still running 5.1, is there any problem to upgrade to 5.5 on vcenter ?
0
 
Paul SolovyovskySenior IT AdvisorCommented:
Running vCenter 5.5 and ESXi 5.1 hosts will work, this is the normal way to upgrade..vCenter comes first.  In place upgrade SSO and Infrastructure Service, then vCenter.  Once you finish with that upgrade Update Manager and then the ESXi 5.1 hosts.  That's exactly what I did with a customer last week and had no problems.
0
 
compdigit44Commented:
As other have stated earlier have you check you network settings? Is the Vm able to access  the network?

Is the vCenter DB local on the server or remote? If vCenter cannot access the DB server the vcenter services will not start.

If DB is local make sure your DB services are running
0
 
piaakitAuthor Commented:
the vCenter DB is on local server, just after p to v, it wont starts, which DB services i need to start ?
0
 
Paul SolovyovskySenior IT AdvisorCommented:
vCenter Server service is what you want to try.  It has failed for one of our customer when we tried to do this.  An upgrade to 5.5 fixed this and allowed us to upgrade hosts to 5.5 as well
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now