Search the VMware Knowledge Base (KB)
View by Article ID

Installing VMware Converter 4.2 fails with the error: Error 29454 Setup failed to register VMware vCenter Converter extension (1025351)

  • 20 Ratings

Symptoms

  • Installing or upgrading VMware vCenter Converter 4.2 fails
  • You see one of these errors:

    • Error 29454.Setup failed to register VMware vCenter Converter extension to VMware vCenter Server: vcenter.hostname.com
    • Error 29454 Unable to register/unregister vCenter Server extensions.

  • In the vminst.log file located at C:\Document and Settings\<logged user>\Local Settings\Temp, you see entries similar to:
vieInstUtil: 07/03/2010 16:19:55 VMInstError::LogErrorLast::Error: 1066 (The service has returned a service-specific error code. )
vieInstUtil: 07/03/2010 16:19:55 VMInstSystem::ShellExecuteWait::done (wait) Res: 1066
vieInstUtil: 07/03/2010 16:19:55 ExecuteConverter::Execute Index: 0 Res: 1066
vieInstUtil: 07/03/2010 16:19:55 ExecuteConverter::done Res: 1066
vieInstUtil: 07/03/2010 16:19:55 GetVCRegisterError::Unable to register(unregister) extension Res: 1066
vieInstUtil: 07/03/2010 16:19:55 RegisterVCServerData::done Res: 29454
vieInstUtil: 07/03/2010 16:19:55 RegisterVCServer::Error: 29454
vieInstUtil: 07/03/2010 16:19:55 RegisterVCServer::done Res: 29454
vieInstUtil: 07/03/2010 16:19:55 VMRegisterVCServer::Error: 29454
vieInstUtil: 07/03/2010 16:19:55 PostMsg::Type: 16777264 Error: 29454 Value:
vieInstUtil: 07/03/2010 16:19:55 ProcessMessage::MessageType: 16777264
vieInstUtil: 07/03/2010 16:20:16 ProcessMessage::done Res: 1
vieInstUtil: 07/03/2010 16:20:16 PostMsg::done Res: 1
vieInstUtil: 07/03/2010 16:20:16 VMRegisterVCServer::Server NOT REGISTERED
vieInstUtil: 07/03/2010 16:20:16 VMRegisterVCServer::done Res: 29454
vieInstUtil: 07/03/2010 16:20:17 --------------- CA exec: VMRollbackRegisterVCServer
vieInstUtil: 07/03/2010 16:20:17 VMRollbackRegisterVCServer
vieInstUtil: 07/03/2010 16:20:17 UnRegisterVCServer
  • In the vpxd.log file located at C:\Documents and Settings\All Users\Application Data\VMware\VirtualCenter\logs, you see entries similar to:
[2010-07-03 11:30:01.527 02556 error 'App' opID=b9f6590f] [LDAP Client] Failed to add LDAP entry CN=com.vmware.converter, CN=047E1FE0-0B70-4FF6-AE55-3DC6F9BC7EC5,OU=ComponentSpecs,OU=Health,dc=virtualcenter,dc=vmware,dc=int: 0x44 (The object already exists.)
[2010-07-03 11:30:45.667 02432 error 'App' opID=6673de34] [LDAP Client] [LDAP Client] Failed to delete LDAP entryCN=com.vmware.converter, CN=047E1FE0-0B70-4FF6-AE55-3DC6F9BC7EC5,OU=ComponentSpecs,OU=Health,dc=virtualcenter,dc=vmware,dc=int: 0x20 (Object does not exist.)
[2011-04-27 09:00:11.672 06184 info 'App' opID=2666e753] [VpxLRO] -- ERROR task-internal-170 --  -- vim.SessionManager.loginExtensionByCertificate: vim.fault.InvalidLogin:Result:(vim.fault.InvalidLogin)
Ensure the acount being used to install has local admin rights on the vCenter server.

Resolution

This issue occurs if there are incorrect values in the ADAM database.
 
To resolve this issue, modify the ADAM database on the vCenter Server with correct values.
 
To modify the ADAM database:
  1. Connect to the ADAM database.
    • In Windows 2003 :
      1. Go to Start > Programs > ADAM > ADAM ADSI Edit. The ADAM editor opens.
      2. Right-click ADAM ADSI Edit and click Connect to....
      3. Click Distinguished name (DN) or naming context and type dc=virtualcenter,dc=vmware,dc=int.

    • In Windows 2008:
      1. Go to Start > Administrative Tools > ADSI Edit. The ADAM editor opens.
      2. Right-click ADSI Edit at the root level and select Connect to.... The Connection Settings window appears.
      3. For Connection Point, click Select or type a Distinguished Name or Naming Context and type dc=virtualcenter,dc=vmware,dc=int.
      4. Under Computer, click Select or type a domain or server and then select localhost from the dropdown or type localhost:389 .
      5. Click OK.

  2. Expand the dc=virtualcenter,dc=vmware,dc=int folder in the left pane.
  3. Expand OU=Health, and then OU=ComponentSpecs .
  4. Expand CN=<RANDOM STRING>. For example, for the vpxd.log error in the Symptoms section, <RANDOM STRING> is CN=047E1FE0-0B70-4FF6-AE55-3DC6F9BC7EC5.
  5. Right-click CN=com.vmware.converter and rename it. For example, rename it as CN=com.vmware.converterold .

    Note: If a value for CN does not exist, create a new value that reads as CN=com.vmware.converter.

  6. Close ADSI Edit.
  7. Retry the VMware vCenter Converter 4.2 installation.

Note: This issue may also occur when you use an account without administrator privileges. Ensure to use an account, preferably a local administrator account, that has local administrator rights and is not constrained by group policies.

Additional Information

It may also be necessary to uninstall all versions of the product, as older stale versions of Update Manager and Converter may cause this error.
 
This issue can also occur if port 80 is blocked or is in use.  To troubleshoot this issue, see Determining if a port is in use (1003971).

Tags

converter-plugin-issue

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

  • 20 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)




Please enter the Captcha code before clicking Submit.
  • 20 Ratings
Actions
KB: