Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Recreate vCenter Server Machine Account in Platform Services Controller after Failed Convergence (68132)

Last Updated: 4/12/2023Categories: TroubleshootingTotal Views: 17016Language:
Chinese (Simplified)JapaneseEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Symptoms

After a failed attempt to converge a vCenter Server and external PSC, vCenter services won't start and you see the following in the VMDIR log /var/log/vmware/vmdird/vmdird-syslog.log on the PSC:

19-05-15T20:27:41.456363+00:00 err vmdird  t@140166960015104: VmDirSRPGetIdentityData ([email-masked]) failed, (9611)
19-05-15T20:27:41.456744+00:00 err vmdird  t@140166960015104: VmDirSRPGetIdentityData ([email-masked]) failed, (9611)
19-05-15T20:27:41.457011+00:00 err vmdird  t@140166960015104: SASLSessionStart: sasl error (-20)(SASL(-13): user not found: no secret in database)
19-05-15T20:27:41.457268+00:00 err vmdird  t@140166960015104: VmDirSendLdapResult: Request (Bind), Error (49), Message ((49)(SASL start failed.)), (0) socket (192.168.0.71)
19-05-15T20:27:41.457582+00:00 err vmdird  t@140166960015104: Bind Request Failed (192.168.0.71) error 49: Protocol version: 3, Bind DN: "", Method: SASL
19-05-15T20:27:42.466907+00:00 err vmdird  t@140166960015104: VmDirSRPGetIdentityData ([email-masked]) failed, (9611)
19-05-15T20:27:42.467344+00:00 err vmdird  t@140166960015104: VmDirSRPGetIdentityData ([email-masked]) failed, (9611)
19-05-15T20:27:42.467596+00:00 err vmdird  t@140166960015104: SASLSessionStart: sasl error (-20)(SASL(-13): user not found: no secret in database)
19-05-15T20:27:42.467823+00:00 err vmdird  t@140166960015104: VmDirSendLdapResult: Request (Bind), Error (49), Message ((49)(SASL start failed.)), (0) socket (192.168.0.71)

There are no backups or powered-off snapshots of all PSC's and VC's in the environment.  No formal recovery option is available.

Purpose

This article will help to recreate the vCenter Server Machine account on a failed Convergence environment

Cause

As part of the converge process, the VC computer account is removed is removed from PSC, and a domain controller account is created (for the new embedded PSC).  If the converge fails after this point, the rollback will not recreate the computer account.

Impact / Risks

The article assumes you have taken powered off snapshots of all PSCs and vCenter Servers in ELM prior to attempting the fix (per the instructions set forth in the resolution section of this article). Should something go wrong, you will have to restore to the snapshots taken before the attempted fix.

Resolution

NOTE:  Please take offline (powered off) snapshots of all PSC's and VC's before attempting.  This is standard best practice before making any manual changes to the PSC VMDIR database.

Copy the script attached to this article on the vCenter Server where converge operation failed.

Make the script executable:

chmod +x recreate_machine.sh

Execute the script.  You will be prompted for the Administrator@<sso.domain> password.

Example output :

root@vc1 [ ~ ]# ./recreate_machine.sh
==================================
Computer object creation for vc1.gsslabs.org started on Fri May 17 18:18:53 UTC 2019

Detected site GUID: 51903a36-7c19-4f9a-bb59-d013d4865bce
Detected machine GUID: 7572d0d2-f5d2-4d35-a8eb-fe93ea0c4739
Detected DN: cn=vc1.gsslabs.org,ou=Computers,dc=vsphere,dc=local
Detected CN: vc1.gsslabs.org
Detected SSO domain: vsphere.local
Detected principal name: [email-masked]
Detected PSC name: psc1.gsslabs.org

Enter SSO admin password:
Creating computer account object...
adding new entry "cn=vc1.gsslabs.org,ou=Computers,dc=vsphere,dc=local"

Generated password: 0KlgH#bdbm97_XDcVuZ7
Applying password to registry.
Applying password to vmdir.
modifying entry "cn=vc1.gsslabs.org,ou=Computers,dc=vsphere,dc=local"

Adding cn=vc1.gsslabs.org,ou=Computers,dc=vsphere,dc=local to DCClients group...
modifying entry "cn=DCClients,cn=Builtin,dc=vsphere,dc=local"

Done on Fri May 17 18:18:57 UTC 2019.  You may need to restart services...

Note:  You may receive an error when you try to run the script:
bash:  ./recreate_machine.sh: /bin/bash^M: bad interpreter: No such file or directory
This error is caused by DOS carriage returns added to the script when copying from a Windows based text editor.  To resolve this problem, run the following command and rerun the script:

sed -i -e 's/\r$//' recreate_machine.sh

Related Information

If you encounter any issues during the script execution, contact VMware Support and note this Article ID (68132) in the problem description. For more information, see How to file a Support Request in Customer Connect

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

recreate_machine

Additional Resources

KB
•
"ERROR_TOO_MANY_NAMES" soluser_firstboot fails when joining an Appliance-based PSC or vCenter Server to a vSphere domain (2114233)

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

KB
•
Dell PERC H330 RAID コントローラを仮想マシンにパススルーすると AMD EPYC ベースのホストでは機能しない (68068)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

VMware vCenter Server 6.x

Take Our Survey

Support Assistant