Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Adding ESX hosts to a vCenter Server Appliance fails with the error: not enough licenses (2045032)

Symptoms

  • You are unable to add hosts to the vCenter Server Appliance.
  • You are unable to add hosts even though you have valid licenses with additional capacity.
  • When adding hosts to the vCenter Server Appliance, you see the error:

    not enough licenses

  • In the vpxd log file, you see errors similar to:

    2013-02-02T09:21:10.979Z [7F6A85B39700 error 'commonvpxLdap' opID=31D1BA0B-000000B3-10] [LDAP Client] Failed to execute search: LDAP error 0x50: Other (e.g., implementation specific) error
    2013-02-02T09:21:10.980Z [7F6A85B39700 error 'licenseldapStorage' opID=31D1BA0B-000000B3-10] [LicMgr] Failed to execute ldap query for entities
    2013-02-02T09:21:10.980Z [7F6A85B39700 error 'linuxvpxLdap_linux' opID=31D1BA0B-000000B3-10] [LDAP Client] Failed to perform paged search for search base DN = ou=LicenseEntities,ou=Licensing,dc=virtualcenter,dc=vmware,dc=int: 0x80 (Other (e.g., implementation specific) error)


  • In the /var/log/ldapmessages file, you see errors similar to:

    Feb 2 09:48:59 sample-system-name slapd[32564]: conn=1002 op=2361 SRCH base="ou=LicenseEntities,ou=Licensing,dc=virtualcenter,dc=vmware,dc=int" scope=1 deref=0 filter="(objectClass=*)"
    Feb 2 09:48:59 sample-system-name slapd[32564]: conn=1002 op=2361 SRCH attr=cn revision isDeleted modifyTimestamp entryUUID lastKnownParent
    Feb 2 09:48:59 sample-system-name slapd[32564]: bdb(dc=virtualcenter,dc=vmware,dc=int): PANIC: fatal region error detected; run recovery
    Feb 2 09:48:59 sample-system-name slapd[32564]: conn=1002 op=2361 SEARCH RESULT tag=101 err=80 nentries=0 text=internal error
    Feb 2 09:48:59 sample-system-name slapd[32564]: conn=1002 op=2362 SRCH base="ou=Licenses,ou=Licensing,dc=virtualcenter,dc=vmware,dc=int" scope=1 deref=0 filter="(objectClass=*)"
    Feb 2 09:48:59 sample-system-name slapd[32564]: conn=1002 op=2362 SRCH attr=cn vmw-vc-LicenseFileContent vmw-vc-LicenseFileName objectClass isDeleted modifyTimestamp entryUUID lastKnownParent
    Feb 2 09:48:59 sample-system-name slapd[32564]: bdb(dc=virtualcenter,dc=vmware,dc=int): PANIC: fatal region error detected; run recovery
    Feb 2 09:48:59 sample-system-name slapd[32564]: conn=1002 op=2362 SEARCH RESULT tag=101 err=80 nentries=0 text=internal error

Resolution

This is a known issue affecting vCenter Server Appliance 5.0 and 5.1.

To resolve this issue, you must recover the LDAP database.

To recover the LDAP database:

  1. Log into the vCenter Server Virtual Appliance as root. The default root password is vmware.

  2. On the command line, log into the database instance and back up the configuration by running these commands:

    su - db2inst1
    db2cfexp db_config
    exit


  3. Stop the LDAP service by running the command:

    service ldap stop

  4. Export the LDAP data by running the command:

    slapcat -l ldap.ldif

  5. Delete the LDAP files by running the command:

    rm -rf /var/lib/ldap/*

  6. Import the LDAP data by running the command:

    slapadd -l ldap.ldif

  7. Log into the database instance again and restore the configuration by running the commands:

    su - db2inst
    db2cfimp db_config
    exit


  8. Set the correct file permissions for the LDAP directory by running the command:

    chown -R ldap:ldap /var/lib/ldap

  9. Start the LDAP service by running the command:

    service ldap start

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 2 Ratings
Actions
KB: