Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Problems encountered in installing vCenter6.0 and their Solutions

2025-02-25 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/02 Report--

Experimental environment:

Install vCenter6.0 on Window Server 2008 R2, using SQL Server2012 for the database

Question 1:

When installing to 50%, it is prompted that the invsvc service cannot be started and vdcpromo cannot be run. Click OK, and the installer rolls back automatically. The error message is as follows:

The reason for these problems in the installation process may be that VMWare Tools is not installed, so these problems will occur in the installation process, but also note that when installing VMWare Tools, you should choose the full installation method.

Question 2:

VCSServiceManager failed with error code 1603

Viewing and reading vSphere6 documents and forum posts, some people have encountered the same problem and the VMware vCenter version notes that they want to reset the IPv4 stack, but it doesn't help. The user rights for my server and domain are correct. As shown in the following figure:

After looking at the SQL Server configuration manager à SQL Server network configuration, I found that my TCP/IP was disabled, so I started it with the IP address enabled, so that after processing, installing vCenter again would not have the above error.

Reference link:

Http://www.virtualization.net/10039-how-to-fix-vcenter-upgrade-to-6-0-vcsservicemanager-failed-with-error-code-1603/

Question 3:

After the vCenter6.0 installation is complete, log in to the vCenter through vSphere Client, create the data center, and add the host to the data center, and the following error occurs:

The solution is as follows:

Check that the network of ESXi and vCenter is open, so the problem does not lie in the network; after careful investigation, it is found that the problem lies in the new compatibility of ESXi and vCenter versions.

Version of vCenter:

Version of ESXi:

It can be found that the version of vCenter (U2) is lower than that of ESXi (U3), so it cannot be managed, and the version of vCenter must be the same or higher than the version of ESXi, so as to avoid the above error when adding ESXi hosts.

Author: SEian.G (hard practice changes in 72, but it is difficult to laugh at 81)

ITPUB: http://blog.itpub.net/31015730/

51CTO: http://seiang.blog.51cto.com/

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report