Skip to main content

VMware Virtual Center Service failed to start due the error “Failed to add LDAP entry”

This post is going to share a resolution for one of the issue which i have faced yesterday. My Virtual center server windows virtual machine was hung  but it was reachable via network with ping. Even RDP it is not accessible. We tried rebooting multiple times. Finally after uninstalling some of the security software, vCenter came up. I tried to start the VMware Virtual center server service but it was failed and throwing an general windows service start failed error. To troubleshoot the Virtual Center Service. You should always to use vpxd.log logfile stored on the below location
vCenter Server 5.x and windows server 2000, 2003: %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\
vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:\ProgramData\VMware\VMware VirtualCenter\Logs\
When i have analyzed the vpxd.log, I found the below error messages in the vpxd.log
 [03852 error 'win32vpxLdap_win32'] [LDAP Client] Failed to add LDAP entry cn=76c0e73g-0bd2-56ba-c706-g449de069520,ou=Instances,dc=virtualcenter,dc=vmware,dc=int: 0×68 (The object already exists.)
 [03852 error 'vpxservicesMoServiceDirectory'] [ServiceDirectory::AddService] Error while adding service-instance entry cn=76c0e73g-0bd2-56ba-c706-g449de069520,ou=Instances,dc=virtualcenter,dc=vmware,dc=int
 [03852 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init] Init failed: Ldap error
 [03852 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down..
How to Resolve this Failed to add LDAP entry issue.
This issue may occur due to a stale ADAM database entry. We need delete the stale ADAM entry using the below procedure. It is recommended to take a backup of your ADAM instance data before deleting the Stale ADAM database entry.
1. Login to your vCenter Server using Administrative Credentials
2.Click on Start -> Administrative Tools ->ADSIEdit
3. Right click the ADSiEdit and click on Connect To
4.For the Connection Point, Type the below Distinguished Name or Naming Context
dc=virtualcenter,dc=vmware,dc=int
5. Under Computer, Type the localhost in the below format and click on Ok.
 localhost:389
VCenter_LDAP issue
6. Expand the  OU=Instances, find the CN which is found in your vpxd.log which is CN=76c0e73g-0bd2-56ba-c706-g449de069520
Vcenter_LDAP_2
7. Right click on the above CN  and Select Delete to delete the Stale ADAM database entry.
After deleting the Stale ADAM database entry, I tried starting the VMware virtual center Service, It started like a gem. I found this troubleshooting solution from the VMware KB Article 1029864. That’s it, All up and life is smooth. I hope this is informative for you. Thanks for Reading!!!

Comments

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
  "Cloud zone insights not available yet, please check after some time" message on Aria Automation https://knowledge.broadcom.com/external/article?articleNumber=314894 Products VMware Aria Suite Issue/Introduction Symptoms: The certificate for Aria operations has been replaced since it was initially added to Aria Automation as an integration. When accessing the Insights pane under  Cloud Assembly  ->  Infrastructure  ->  Cloud Zone  ->  Insights  the following message is displayed:   "Cloud zone insights not available yet, please check after some time." The  /var/log/services-logs/prelude/hcmp-service-app/file-logs/hcmp-service-app.log  file contains ssl errors similar to:   2022-08-25T20:06:43.989Z ERROR hcmp-service [host='hcmp-service-app-xxxxxxx-xxxx' thread='Thread-56' user='' org='<org_id>' trace='<trace_id>' parent='<parent_id>' span='<span_id>'] c.v.a.h.a.common.AlertEnu...