Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Linking two vCenter Servers fails with the error: Error 28039.Setup cannot join vCenter Server to the linked mode group (1026087)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 20687Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You cannot link two vCenter Servers.

Linking two vCenter Servers fails.

You see the error:

Error 28039.Setup cannot join vCenter Server to the linked mode group...Check the jointool-0.log for more information

In the JoinTool.log file, you see entries similar to:

[2011-12-08 11:24:15 INFO] JoinTool started
[2011-12-08 11:24:15 INFO] Storage directory for LDAP instance: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS
[2011-12-08 11:24:15 INFO] Operation Mode: join
[2011-12-08 11:24:15 FINEST] All IP addresses for :COR01SRVSVC01.cor.local :
[2011-12-08 11:24:15 INFO] Service 'VMware VirtualCenter Management Webservices' is shutdown
[2011-12-08 11:24:15 INFO] Service 'VMware VirtualCenter Server' is running
[2011-12-08 11:24:15 SEVERE] Operation "Join instance VMwareVCMSDS" failed: : Action: Prepare for Join Problem: Service "VMware VirtualCenter Server" has not been stopped|
[2011-12-08 11:24:15 SEVERE] Recovering from failed Operation "Join instance VMwareVCMSDS"

In the vpxd.log file, you see entries similar to:

[2011-12-08 11:23:41.681 03008 warning 'ProxySvc Req00010'] Error reading from client while waiting for header: class Vmacore::SystemException(The specified network name is no longer available. )
[2011-12-08 11:23:42.150 03564 warning 'App'] Service control manager requested shutdown
[2011-12-08 11:23:42.151 03564 info 'App'] Initiating VMware VirtualCenter shutdown
[2011-12-08 11:23:42.151 03056 info 'App'] Shutting down VMware VirtualCenter...
[2011-12-08 11:23:55.018 03948 error 'App'] SSLStreamImpl::BIOWrite (0000000007e5c3b0) AsyncWrite failed: An existing connection was forcibly closed by the remote host.
[2011-12-08 11:23:55.018 03948 error 'App'] SSLStreamImpl::SSLWrite (0000000007e5c3b0) SSL_write failed with BIO Error
[2011-12-08 11:23:55.018 03948 error 'App'] [VpxVmomi] Exception while sending result: SSL Exception: BIO Error
[2011-12-08 11:24:36.191 03848 info 'App'] [VpxdHostCnx] Host connection reaper thread exiting
[2011-12-08 11:24:36.692 03056 info 'App'] [VpxdServer] Exit done.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Resolution

To be able to link two vCenter Servers, ensure that you meet these requirements:

DNS is set up and configured.

Both vCenter Servers are either in the same domain, or in different domains with a two-way trust relationship set up.

Both vCenter Servers do not have their time settings more than 5 minutes apart (use NTP).

Both vCenter Servers have the correct licensing.

Ensure all vCenter Servers in a Linked Mode group are registered to the same vCenter Single Sign On server.

The installer is run by a domain user who is a local administrator on both the vCenter Server systems.

If your issue persists after meeting these requirements, check the jointool-0.log file located at C:\Documents and Settings\User\Local Settings\Temp\.

If the jointool-0.log file contains the error instance GUID for remote vCenter Server is same as the GUID for this vCenter Server and the databases for both vCenter Servers are on the same remote database server, ensure that you are not using the same SQL user account for both databases unless each ODBC connection specifies which vCenter Server database to use.

The Linked Mode installation verifies the vCenter Server's GUID from the database and each SQL user has a default database. When you use the same SQL user account for both databases, the installation attempts to read from the default database for both users, find them to be the same, and fails with the error.

To resolve this issue:

Create a new SQL user.

Assign DB_owner privileges on the correct database to this user.

Change the ODBC connection on one of the vCenter Server machines andspecify the new SQL user.

Reinstall vCenter Server on one of the vCenter Server machines and specify the new SQL user for the database.

Related Information

For more information, see the Linked Mode Prerequisites for vCenter Server section in the vSphere 5.5 Installation and Setup Guide. 2 台の vCenter Server をリンクしようとすると次のエラーで失敗する： Error 28039.Setup cannot join vCenter Server to the linked mode group（エラー28039。セットアップで vCenter Server がリンク モード グループに参加できません）

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
检查网络设备和设备设置是否为导致 VMware Converter 发生故障的原因 (1004615)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant