VMware Cloud Community
jer0nim0
Contributor
Contributor

vCenter Update Manager (VUM) migration and upgrade

Hi there,

I am upgrading vCenter 4.0 to 4.1.

This means I am migrating it from a Windows 2003 Server 32-bit machine to a Windows 2008 Server (64-bit).

The problem is vCenter Update Manager (VUM).

Previously, I had the VUM data AND the vCenter data in one single DB.

Now, obviously, we have to split, since Update Manager only supports a 32-bit DSN, whereas vCenter Server requires a 64-bit DSN.

After successfully migrating vCenter 4.1, I am trying to set up VUM again.

I have created a 32-bit DSN pointing to an empty DB (doesn't matter since we didn't actually use it), however during installation there is an error:

If I look at vminst.log it says:

VMware Update Manager-build-256596: 07/28/10 11:21:13 ---------- Begin Logging ----------
VMware Update Manager-build-256596: 07/28/10 11:21:13 --- CA exec: VMRegisterExtension
VMware Update Manager-build-256596: 07/28/10 11:21:13 INFO: Reg/UnReg extn command: ["-v vcenterip -p 80 -U "Administrator" -P *** -S "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\extension.xml" -C "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\\" -L "C:\Users\ADMINI~1\AppData\Local\Temp\\" -O extupdate"]
VMware Update Manager-build-256596: 07/28/10 11:21:13 AppendPath::done Path: C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe
VMware Update Manager-build-256596: 07/28/10 11:21:13 Found "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe"
VMware Update Manager-build-256596: 07/28/10 11:21:23 Process returned 199
VMware Update Manager-build-256596: 07/28/10 11:21:23 Error:: Unknown VC error
VMware Update Manager-build-256596: 07/28/10 11:21:23 ERROR: VUM registeration with VC failed
VMware Update Manager-build-256596: 07/28/10 11:21:23 Posting error message 25085
VMware Update Manager-build-256596: 07/28/10 11:21:33 MsiProcessMessage returned: 1
VMware Update Manager-build-256596: 07/28/10 11:21:33 ---------- End Logging----------

Running vciInstallUtils.exe manually to see a more specific error gives:

C:\Program Files (x86)\VMware\Infrastructure\Update Manager>"C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe" "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe" -v vcenterip -p 80 -U "Administrator" -P *** -S "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\extension.xml" -C "C:\Program Files (x86)\VMware\Infrastructure\Update Manager\\" -L "C:\Users\ADMINI~1\AppData\Local\Temp\\" -O extupdate

[2010-07-28 13:30:16.015 02796 info 'App'] Current working directory: C:\Program Files (x86)\VMware\
Infrastructure\Update Manager
[2010-07-28 13:30:16.025 02796 info 'Libs'] Using system libcrypto, version 9080CF
[2010-07-28 13:30:17.063 02796 info 'App'] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeout
Us = 120000000
  [logUtil, 252] Product = VMware Update Manager, Version = 4
.1.0, Build = 256596
  [main, 330] Successfully configured logger
  [main, 349] command line arguments:
argv 0 = C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe
argv 1 = C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe
argv 2 = -v
argv 3 = vcenterip
argv 4 = -p
argv 5 = 80
argv 6 = -U
argv 7 = Administrator
argv 8 = -P
argv 9 = xxxx(user password)
argv 10 = -S
argv 11 = C:\Program Files (x86)\VMware\Infrastructure\Update Manager\extension.xml
argv 12 = -C
argv 13 = C:\Program Files (x86)\VMware\Infrastructure\Update Manager\
argv 14 = -L
argv 15 = C:\Users\ADMINI~1\AppData\Local\Temp\
argv 16 = -O
argv 17 = extupdate

  [installerRunVCCommand, 79]  [VCSERVER] op name = extupdate

  [installerRunVCCommand, 106]  [VCSERVER] logging into vc.
  [installerRunVCCommand, 110]  [VCSERVER] host = vcenterip, port = 80, user = Administrator
  [installerRunVCCommand, 356]  [VCSERVER] Set the current wor
king directory to: C:/Program Files (x86)/VMware/Infrastructure/Update Manager/
  [logUtil, 252] Product = VMware Update Manager, Version = 4
.1.0, Build = 256596
 VC server URL: http://vcenterip:80
[2010-07-28 13:30:17.559 02796 info 'Extension'] Connecting to host vcenterip on port 80 using p
rotocol http
----SSL ERRORS----
[2010-07-28 13:32:13.004 01184 info 'Extension'] Logged in!
[2010-07-28 13:32:13.835 01184 info 'vmomi.soapStub Resetting stub adapter for server TCP:vcenterip:80 : Closed
[2010-07-28 13:32:13.844 01184 warning 'vmomi.soapStub Canceling invocation: server=TCP:vcenterip:80, moref=vim.SessionManager:SessionManager, method=logout
 MethodFault error: vim.fault.DatabaseError
  [installerRunVCCommand, 382]  [VCSERVER] The extension regis
tration failed
  [installerRunVCCommand, 385]  [VCSERVER] Register extension
 failed 1066

(Yes, I have used the correct password I only Xed it out here.)

(I have excluded any special characters (that W2008 would love to have in the password) from the password.)

I guess vim.fault.DatabaseError must have to do with the fact that the new vCenter still looks for the old VUM at the old IP or something like that.

Also, vSphere Clients still show the VUM plugin at version 4.0.0 trying to contact vCenter at the old IP address.

How am I supposed to proceed?

Thanks

JM

Reply
0 Kudos
25 Replies
schepp
Leadership
Leadership

You don't need to split the databases, you only need to create a 64 and a 32 Bit DSN for the one database.

Regards

Reply
0 Kudos
jer0nim0
Contributor
Contributor

Doing it that way still yields the same error.

Reply
0 Kudos
admin
Immortal
Immortal

Hi,

You don't need to change the database. All you need to do is create a 32bit DSN for VUM and a 64bit DSN for VC. Both DSNs should point to old database.

The logs show that registration of VUM to VC failed. Is VC service up?

Please answer few questions:

1. Are VC-VUM 4.0 installed on same machine? Are you planning to install VC-VUM 4.1 on a single machine?

2. Have you successfully created both 32bit and 64bit DSNs on the 64-bit machine? Tested the DSNs?

3. Was VC upgrade successful? Are you able to login to the VC server?

4. Which DB are you using?

5. Have you used any custom ports during VC-VUM 4.0 installation or during VC upgrade?

Please remove any traces of VUM 4.1 from the new machine and start upgrading VUM using VMware-UpdateManager.exe and point to the old DB. Make sure that you give the new IP address of VC server during VUM install.

Please attach following logs if possible:

vmware-vum-server-1.log

vmware-vum-server-log4cpp.log

vmware-rdevServer-log4cpp.log

vim-um-msi.log

Thanks.

*if you found this or any other answer useful, please consider allocating points for helpful or correct answers*

Reply
0 Kudos
FIM
Contributor
Contributor

We have the same problem:

1. Are VC-VUM 4.0 installed on same machine? Are you planning to install VC-VUM 4.1 on a single machine?

yes, 4.0 and 4.1 are installed on the same machine.

2. Have you successfully created both 32bit and 64bit DSNs on the 64-bit machine? Tested the DSNs?

Yes, connection works fine.

3. Was VC upgrade successful? Are you able to login to the VC server?

VC is working fine, login is possible

4. Which DB are you using?

MS SQL Express 2005

5. Have you used any custom ports during VC-VUM 4.0 installation or during VC upgrade?

No

In the vim-um-msi.log I found this error message:

MSI (s) (1C:70) : Executing op: CustomActionSchedule(Action=VM_RollbackRemoveVStor2Driver,ActionType=3329,Source=BinaryData,Target=LegacyDrv_Remove,CustomActionData=vstor2-vci10;Vstor2 Update Manager Virtual Storage Driver;1)

MSI (s) (1C:70) : Executing op: ActionStart(Name=VM_RegisterExtension,Description=Update Manager-Erweiterung wird bei VMware vCenter Server ( swdvmw02:80) registriert,)

Aktion 13:38:43: VM_RegisterExtension. Update Manager-Erweiterung wird bei VMware vCenter Server ( servername:80) registriert

MSI (s) (1C:70) : Executing op: CustomActionSchedule(Action=VM_RegisterExtension,ActionType=11265,Source=BinaryData,Target=*********,CustomActionData=*********)

MSI (s) (1C:24) : Invoking remote custom action. DLL: C:\Windows\Installer\MSI4517.tmp, Entrypoint: VMRegisterExtension

MSI (s) (1C!80) : Transforming table Error.

Does anyone have an idea?

Thanks

Reply
0 Kudos
jer0nim0
Contributor
Contributor

I am in touch with support concerning this matter.

After all it can't be that hard to reinstall VUM on the new 64-bit OS that was required to migrate vCenter to.

1. Are VC-VUM 4.0 installed on same machine?

No (it's a migration 32-bit -> 64-bit) since VC 4.1 only runs on 64-bit OS.

1. Are you planning to install VC-VUM 4.1 on a single machine?

Yes, they should both run on the same new 64-bit OS.

2. Have you successfully created both 32bit and 64bit DSNs on the 64-bit machine? Tested the DSNs?

Yes. Both.

3. Was VC upgrade successful? Are you able to login to the VC server?

Yes. Works flawlessly, except for the VUM plugin.

4. Which DB are you using?

SQL Express 2008 R2

5. Have you used any custom ports during VC-VUM 4.0 installation or during VC upgrade?

No

Additionally in the corresponding vpxd log I now found

[2010-07-28 13:18:31.729 01152 info 'App' opID=6f0ea3f3] [VpxLRO] -- BEGIN task-internal-6091 --  -- vim.ExtensionManager.updateExtension -- 57F18B7B-80F7-40BC-B332-CDEFF7CDC58B(D051BE2E-7D41-4D22-AFBF-8D3D71ACBE12)
[2010-07-28 13:18:31.754 01152 error 'App' opID=6f0ea3f3] [LDAP Client] [LDAP Client] Failed to delete LDAP entryCN=com.vmware.vcIntegrity,CN=AB6FD5FE-7306-4577-907B-21A769F55FC1,OU=ComponentSpecs,OU=Health,dc=virtualcenter,dc=vmware,dc=int: 0x20 (Object does not exist.)
[2010-07-28 13:18:31.754 01152 error 'App' opID=6f0ea3f3] [VpxdHealth::UnregisterHealthUrl] LDAP problem. Unable to unregister health spec for com.vmware.vcIntegrity
[2010-07-28 13:18:31.754 01152 error 'App' opID=6f0ea3f3] vim.fault.DatabaseError

Apparently there's some KB entry that's unavailable that deals with a similar but not identical error:

[LDAP Client] Failed to add LDAP 

However, as I said, that does not apply here.

JM

Reply
0 Kudos
jer0nim0
Contributor
Contributor

Here it seems to help to use ADSI Edit (Start Menu)

Connect to localhost DN=dc=virtualcenter,dc=vmware,dc=int

Goto OU=Health OU=ComponentSpec CN=RANDOM STRING

Create a container called CN=com.vmware.vcIntegrity

Reply
0 Kudos
allencrawford
Enthusiast
Enthusiast

Same exact issue here. I actually upgraded VUM, but as usual, the VUM upgrade completed successfully for me but then weird things started happening (patches not being downloaded, not being able to upload ESX host upgrade files, etc.). Since VUM is on a separate DB for us already, I did the usual and uninstalled, cleaned up the appropriate reg entries and files, rebooted, then reinstalled and started over (blowing the database away). Then of course it fails to install. The logs do mention a bad password, but I know the password is not bad.

In addition to this, do you also get the following ADAM error in the event log upon a reboot?

Event Type:	Error
Event Source:	ADAM [VMwareVCMSDS] Database
Event Category:	Backup 
Event ID:	2524
Date:		8/4/2010
Time:		5:35:39 PM
User:		NT AUTHORITY\ANONYMOUS LOGON
Computer:	SERVERNAME
Description:
The Directory Server detected that the database has been replaced.  This is an unsafe and unsupported operation.
 
 User Action:
 None. The Active Directory was able to recover the database in this instance, but this is not guaranteed in all circumstances. Replacing the database is strongly discouraged.  The user is strongly encouraged to use the backup and restore facility to rollback the database.

We get this and some corresponding errors in the vpxd.log file below:

[2010-08-04 17:28:44.828 01832 info 'App'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running
[2010-08-04 17:28:44.828 01832 info 'App'] [LdapBackup] Attempting to start service ADAM_VMwareVCMSDS...
[2010-08-04 17:28:44.859 01832 info 'App'] [LdapBackup] Service stopped, starting
[2010-08-04 17:35:10.472 01832 error 'App'] [LdapBackup] Timed out waiting for service.
[2010-08-04 17:35:11.784 01832 error 'App'] [LDAP Client] Failed to connect to LDAP: 0x51 (Cannot contact the LDAP server.)
[2010-08-04 17:35:11.988 01832 error 'App'] [VpxdLdap] Failed to create LDAP client
[2010-08-04 17:35:11.988 01832 info 'App'] [VpxdLdap] Attempting recovery
[2010-08-04 17:35:12.050 01832 info 'App'] [VpxdLdap] Loading LDAP backup 284 created at 2010-08-04 20:24:09.282
[2010-08-04 17:35:34.082 01832 info 'App'] [VpxdLdap] Backup data loaded.
[2010-08-04 17:35:34.082 01832 info 'App'] [LdapBackup] Starting LDAP data restore
[2010-08-04 17:35:34.082 01832 info 'App'] [LdapBackup] Target directory: E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\
[2010-08-04 17:35:34.082 01832 info 'App'] [LdapBackup] Restore data integrity check successful.
[2010-08-04 17:35:34.082 01832 info 'App'] [LdapBackup] Attempting to stop service ADAM_VMwareVCMSDS...
[2010-08-04 17:35:34.082 01832 info 'App'] [LdapBackup] Service running, stopping
[2010-08-04 17:35:34.082 01832 info 'App'] [LdapBackup] Service in pending state, waiting...
[2010-08-04 17:35:36.082 01832 info 'App'] [LdapBackup] Service stopped
[2010-08-04 17:35:36.082 01832 info 'App'] [LdapBackup] Restoring file E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\adamntds.dit
[2010-08-04 17:35:36.113 01832 info 'App'] [LdapBackup] Restoring file E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\edb.chk
[2010-08-04 17:35:36.129 01832 info 'App'] [LdapBackup] Restoring file E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\edb.log
[2010-08-04 17:35:36.301 01832 info 'App'] [LdapBackup] Restoring file E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\edb00001.log
[2010-08-04 17:35:36.504 01832 info 'App'] [LdapBackup] Restoring file E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\res1.log
[2010-08-04 17:35:36.676 01832 info 'App'] [LdapBackup] Restoring file E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\res2.log
[2010-08-04 17:35:36.879 01832 info 'App'] [LdapBackup] Restoring file E:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\temp.edb
[2010-08-04 17:35:36.910 01832 info 'App'] [LdapBackup] Attempting to start service ADAM_VMwareVCMSDS...
[2010-08-04 17:35:36.910 01832 info 'App'] [LdapBackup] Service stopped, starting
[2010-08-04 17:35:37.176 01832 info 'App'] [LdapBackup] Service in pending state, waiting...
[2010-08-04 17:35:39.177 01832 info 'App'] [LdapBackup] Service in pending state, waiting...
[2010-08-04 17:35:41.177 01832 info 'App'] [LdapBackup] Service started
[2010-08-04 17:35:41.177 01832 info 'App'] [LdapBackup] LDAP data restore completed successfully.

On top of all this, the "VMware VirtualCenter Management Webservices" service fails to start, presumably because of the above issues. After waiting the six minutes or so it takes for all of the above to happen and I finally get the login prompt, I can log in and start this service manually with no issues.

Just curious if you too are experiencing any of these issues? OS for me is Server 2003 EE 64-bit, so not quite the same exact situation is you, but same VUM problems for sure.

Anyway, curious how your support case is going. I'll be opening one first thing tomorrow morning.

Reply
0 Kudos
jer0nim0
Contributor
Contributor

Same exact issue here.

I'm afraid but I don't think so. In my case the update did NOT work.

(I also searched for the errors you mentioned and didn't find any.)

It might be worthwhile to start a new thread for your new problem.

Reply
0 Kudos
RickMRA
Contributor
Contributor

Wow, jer0nim0 thanks a million for posting the solution! This totally worked. I've been strugling with installing VUM due to the "unable to register plugin" error message in a similar scenario (upgraded to vCenter 4.1).

Thanks again!!

Reply
0 Kudos
jer0nim0
Contributor
Contributor

sure no prob

meanwhile this seems to have found its way into the KB too: article 1024795

Reply
0 Kudos
dizel247
Contributor
Contributor

Hello,

Your suggestion did the trick thanks a lot. I was pulling my hair away.

I am using WIN 2k8 R2

ADSI Edit worked in following:

Connection Point > dc=virtualcenter,dc=vmware,dc=int

Computer > localhost.

Regards,

Roman

Reply
0 Kudos
allencrawford
Enthusiast
Enthusiast

Sorry for being late to the party, but I wanted to get this added in case someone else runs into these problems and this thread...

I didn't even notice the ADSI Edit info you supplied initially, but it turns out the solution to my initial problem (where a fresh VUM install was not able to register the plugin with vCenter) was to do the opposite of what you said regarding the ADSI Edit steps. Instead of creating that OU, you have to delete it to fix my issue of the failed install (this is assuming you previously had a VUM install and have removed it like I did). For whatever reason, my VUM uninstall did not remove that OU and when the fresh install attempted to create it, it already existed and it was throwing an error, which led to the VUM plugin to not get registered with vCenter, which seems similar to what you saw in one of your vpxd logs. For whatever reason, in future removes/reinstalls my VUM instance cleanly removed that OU from ADAM, so it seems somewhat random on how successful it is at properly uninstalling itself.

Once I got past this, I still had issues where each time I rebooted my vCenter/VUM server, the ADAM database would act as if it were corrupt or something and have to perform a restore from a previous ADAM backup (see my vpxd logs earlier in this thread). This caused a good six minute startup delay before vCenter would start running and each time it did this, it also broke VUM because apparently VUM uses something in the ADAM database and when my database was restored from a backup, it didn't have the VUM data yet (because I always reboot after installing a vCenter component so it never had time to back up the ADAM database that contained the VUM info).

Anyway, each time my ADAM database got restored, everything would work fine with vCenter, but parts of VUM broke--namely the ability to import offline bundle zip files or the host upgrade patch files. Those buttons/links were just grayed out whereas they were fine before the reboot that caused the ADAM restore.

In the end, this problem was caused by me having the VMware ADAM service set to Manual instead of Automatic. There's a long story why we had it that way, but the short of it was that I swear it used to be set to Manual by default, so that's why we had it that way. I've still got an SR open with VMware and the final two pieces of data I'm trying to get out of them is what exactly does VUM use ADAM for and why in the world would having the service set to Manual cause ADAM to go nuts and have to restore itself--and then subsequently PERMANENTLY break VUM (forcing a reinstall unless there's some other fix/workaround I'm not aware of). Seems like a bit of an issue if something that simple can break VUM considering that at times admins may decide to temporarily disable a service by setting it to Manual (as opposed to Disabled). It seems that vpxd.exe would've just started the ADAM service when needed (it certainly started it when set to Manual) and all would be well.

Sorry for the extended description, but hopefully it saves someone the pain I had to deal with (and still am since I'm waiting on answers from VMware support).

Reply
0 Kudos
chadlang
Contributor
Contributor

Thanks jer0nim0, silly that this has to be done, but whatever.

Reply
0 Kudos
madsrs
Contributor
Contributor

This might be a silly question, but what if your server isn't in a domain, so it does not have any ad structure to edit in ADSI???

Any help is appreciated.

BTW, i get the same error as the above posts.

Reply
0 Kudos
allencrawford
Enthusiast
Enthusiast

The ADSI Edit that we are using is for the local ADAM instance that VMware installs. So, you will definitely be able to edit it as necessary. It is separate from any Active Directory domain you may or may not be using.

Reply
0 Kudos
JeanK
Contributor
Contributor

We had the same Problem.

All solutions didn't solve our Problem.

we worked through the articles:

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

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1003468&sl... 0 117278604

Nothing solved the Problem.

After deleting, on the vCenter Server, the directory c:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vcIntegrity

VUM was able to Install and register the extension

Regards

Jean

Reply
0 Kudos
Hiney
Enthusiast
Enthusiast

Just upgraded from vc 4.1 to vc4.1upd01.

previously i had followed this instruction to cope with the VUM upgrade.

Unfortunately, i got the same error with the 4.1upd01 VUM upgrade.

so i ran adsi and sure enough, the com.vmware.vcIntegrity entry was present. So i removed it (i could always put it back). AND LO !!! it worked.

so for 4.0 to 4.1, put it in, and for 4.1 to 4.1upd01, take it out.

the VUM install recreated the needed entry, but the coders obviously forgot that "entry already exists" is an OK error. Dumb a**es. No wonder OVM is getting such a foothold.

P

"I have an inferiority complex, it's just not a very good one."
Reply
0 Kudos
Hiney
Enthusiast
Enthusiast

ok, further update, i just ran the client, all my hosts and DataCentres are gone.

luck this is DEV and i snapshotted the VM.

In Production, for the 3.5 -> 4.0 migration we built a new VM, and installed the new VC and tranferred the hosts over, cluster by cluster. Checking on my previous notes, it happened then too 🙂

Sweet Product guys.

bizarre

p

"I have an inferiority complex, it's just not a very good one."
Reply
0 Kudos
Hiney
Enthusiast
Enthusiast

Now. The definition of insanity is doing the same thing over and over and expecting a different result.

it worked second time round. huh ????

p

"I have an inferiority complex, it's just not a very good one."
Reply
0 Kudos