Installing VMware Update Manager 4.1 fails with the error: Error 25085

Overview

I ran into this during an upgrade today. If the ESX 3.5 vCenter database was upgraded instead of rebuilt (which it is easy to just rebuild the environment through vCenter anyway), you may run into this issue. Basically, the install goes al the way through, but at the end when the VUM tries to register the service the error 25085 occurs. I bascially had to create the CN=com.vmware.vcIntegrity entry and everything worked.

Below is the details of the link from KB at vmware.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1024795

Installing VMware Update Manager 4.1 fails with the error: Error 25085

Symptoms

• When attempting to install or upgrade VMware Update Manager 4.1 the install nearly finishes but then fails
• You see the error:

Error 25085.Setup failed to register VMware vCenter Update Manager extension to VMware vCenter Server: vcenter.hostname.com

• The vpxd.log (located at C:\Documents and Settings\All Users\Application Data\VMware\VirtualCenter\logs) contains entries similar to:
  [2010-07-20 11:30:01.527 02556 error 'App' opID=b9f6590f] [LDAP Client] Failed to add LDAP entry CN=com.vmware.vcIntegrity,CN=047E1FE0-0B70-4FF6-AE55-3DC
  6F9BC7EC5,OU=ComponentSpecs,OU=Health,dc=virtualcenter,dc=vmware,dc=int: 0x44 (The object already exists.)
  [2010-08-07 12:45:45.667 02432 error 'App' opID=6673de34] [LDAP Client] [LDAP Client] Failed to delete LDAP entryCN=com.vmware.vcIntegrity,CN=24FE3541-40A2-427C-85CA-0069575BA81F,OU=ComponentSpecs,OU=Health,dc=virtualcenter,dc=vmware,dc=int: 0x20 (Object does not exist.)

• The install log vminst.log (located at C:\Users\<username>\AppData\Local\Temp\2 for Windows 2008 or C:\Documents and Settings\<username>\Local Settings\Temp for legacy versions of Windows) contains errors similar to:
  
  VMware Update Manager-build-256596: 07/20/10 11:29:58 --- CA exec: VMRegisterExtension
  VMware Update Manager-build-256596: 07/20/10 11:29:58 INFO: Reg/UnReg extn command: ["-v 10.0.0.1 -p 80 -U "user" -P *** -S "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\extension.xml" -C "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\\" -L "C:\Users\user\AppData\Local\Temp\\" -O extupdate"]
  VMware Update Manager-build-256596: 07/20/10 11:29:58 AppendPath::done Path: C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe
  VMware Update Manager-build-256596: 07/20/10 11:29:58 Found "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe"
  VMware Update Manager-build-256596: 07/20/10 11:30:01 Process returned 199
  VMware Update Manager-build-256596: 07/20/10 11:30:01 Error:: Unknown VC error
  VMware Update Manager-build-256596: 07/20/10 11:30:01 ERROR: VUM registeration with VC failed

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 the correct values.

 

To modify the ADAM database:

1. Connect to the ADAM database.
2. • For Windows 2003 :
     1. Go to Start > Programs > ADAM > ADAM ADSI Edit to open the ADAM editor.
     2. Right-click ADAM ADSI Edit and click Connect to....
     3. Choose Distinguished name (DN) or naming context and type dc=virtualcenter,dc=vmware,dc=int
        
   • For Windows 2008:
   • 1. Go to Start > Administrative Tools > ADSI Edit to open the ADAM editor.
     2. Right-click ADSI Edit at the root level and select Connect to....  The Connection Settings window appears.
     3. For Connection Point, choose 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... then select localhost or type localhost:389 from the dropdown.
     5. Click OK.
        
3. Expand the dc=virtualcenter,dc=vmware,dc=int folder in the left pane.
4. Next expand OU=Health, and then OU=ComponentSpecs. 
5. Finally expand CN=<RANDOM STRING> (for example, from the above vpxd.log error CN=047E1FE0-0B70-4FF6-AE55-3DC6F9BC7EC5).
6. Right-click CN=com.vmware.vcIntegrity and rename it (for example, CN=com.vmware.vcIntegrityold).
   
   This issue can be caused by a non-existent value. If the value is not there, simply create a new value that reads CN=com.vmware.vcIntegrity.
   
7. Close ADSI Edit.

Additional Information

In addition to modifying the ADAM database, the vCenter database may need to be corrected as well.

 

To correct the vCenter database:

1. Go to Start > Run, type services.msc, and click OK.
2. Click VirtualCenter Server Service, then click Stop.
3. Launch SQL Server Management Studio.
4. Click the vCenter Server database, and execute these commands:
   delete from VPX_EXT_TYPE_IDS where EXT_ID = 'com.vmware.vcIntegrity'delete from VPX_EXT_PRIVS where EXT_ID = 'com.vmware.vcIntegrity'delete from VPX_EXT_CLIENT where EXT_ID = 'com.vmware.vcIntegrity'delete from VPX_EXT_SERVER_EMAIL where exists(select 1 from VPX_EXT_SERVER where VPX_EXT_SERVER.EXT_SERVER_ID = VPX_EXT_SERVER_EMAIL.EXT_SERVER_ID
   AND VPX_EXT_SERVER.EXT_ID = 'com.vmware.vcIntegrity')delete from VPX_EXT_SERVER where EXT_ID = 'com.vmware.vcIntegrity'delete from VPX_EXT where EXT_ID = 'com.vmware.vcIntegrity'
   
5. Start the vCenter Server services.

This failure can occur if the vCenter Management Web Service not running:

 

[LDAP Client] Failed to add LDAP entry CN=com.vmware.vcIntegrity,CN=08127EEE-A6FA-43D8-8314-2B9F188D4D38,OU=ComponentSpecs,OU=Health,dc=virtualcenter,dc=vmware,dc=int: 0x20 ( Object does not exist.)

 

Verify that the vCenter Management Web Services is started and functioning properly and run the VMware Update Manager installation.

 

If the above errors are not observed, see VMware Update Manager Plug-In fails to Install (1003468) and Update Manager install or upgrade fails if authentication credentials contain a semicolon (1014119) for additional possible solutions.

 

This error may also be observed with Converter. Instead of renaming CN=com.vmware.vcIntegrity the value is CN=com.vmware.converter.

 

In addition, you may also encounter this error if you have a port conflict on your vCenter Server. Ensure that all required ports are open. For more information on what network ports are required, see vCenter Server 4.1 network port requirements (1022256).