VMware Cloud Community
MRoushdy
Hot Shot
Hot Shot
Jump to solution

Upgrading WIN vCenter 6.0 to 6.7U1 fails

Hello,

I get the following error in phase 2 of migrating vCenter on Windows to VCSA 6.7 U1. My current setup is as following:

  • vCenter Server on Windows server 2012.
  • external database on MS SQL 2012
  • both vcenter and MS SQL DB VMs are on the same host.
  • the new vcenter is being deployed on another host in the same cluster, but on a standard switch, not a distributed switch as the current vCenter. Connectivity is fine and tested.
  • local Windows admin accounts are used.
  • Migration tool is run using the elevated mode.
  • I run the installation from the SQL server, it's the appropriate VM to be used for the deployment for now.

I ran the setup for four times till now, same result. VMware support couldn't help me yet, The error message says somethigna bout a denied access, and unable to stop vpxd serviice on the current vCenter, I'm sorry I'm unable to copy and paste the whole message here.

pastedImage_0.png

vEXPERT - VCAP-DCV - Blog: arabitnetwork.com | YouTube: youtube.com/c/MohamedRoushdy
1 Solution

Accepted Solutions
Sreejesh_D
Virtuoso
Virtuoso
Jump to solution

can you please try the following workaround mentioned in the thread vCenter Windows 6.0U3 to VCSA 6.5U1 failure .

As for me, I removed vpxd(VMware vCenter Virtual Server) as a dependency from all Windows services and migration tool successfully shutdown source machine to continue migration.

Basically, I did "sc config SERVICE_NAME depend=/" for every service that required vpxd as a parent. It messes with other dependencies the service might have, but the Windows server wouldn't be needed anyway.

-SD [vExpert 14-19,VCIX6-NV&DCV,RHCE]

https://pingforinfo.com

https://twitter.com/sreejeshd

View solution in original post

5 Replies
birend1988
Hot Shot
Hot Shot
Jump to solution

Stop all the VC services and start the migration. You can perform the migration by stopping the services.

VCIX, NCAP
0 Kudos
Sreejesh_D
Virtuoso
Virtuoso
Jump to solution

can you please try the following workaround mentioned in the thread vCenter Windows 6.0U3 to VCSA 6.5U1 failure .

As for me, I removed vpxd(VMware vCenter Virtual Server) as a dependency from all Windows services and migration tool successfully shutdown source machine to continue migration.

Basically, I did "sc config SERVICE_NAME depend=/" for every service that required vpxd as a parent. It messes with other dependencies the service might have, but the Windows server wouldn't be needed anyway.

-SD [vExpert 14-19,VCIX6-NV&DCV,RHCE]

https://pingforinfo.com

https://twitter.com/sreejeshd

MRoushdy
Hot Shot
Hot Shot
Jump to solution

Hi, thanks for this. I've already gone through this article today, but thought of making it the last resort. Could you please tell me how to know the Win services that needs to be modified? Are those appear in the list when I try to stop the VCenter server service?  I guess they are all just VMware services.

vEXPERT - VCAP-DCV - Blog: arabitnetwork.com | YouTube: youtube.com/c/MohamedRoushdy
0 Kudos
Raj1988
Enthusiast
Enthusiast
Jump to solution

Please check the image on how to find service dependencies

MRoushdy
Hot Shot
Hot Shot
Jump to solution

This did the trick, detaching the Windows services did the trick, and the upgraded finished successfully.

I'd like to thank you all.

Good day,

vEXPERT - VCAP-DCV - Blog: arabitnetwork.com | YouTube: youtube.com/c/MohamedRoushdy
0 Kudos