I managed to get a new VC 2.5 installation finished, but the VMware Update Manager won't install. I get the error "Error 25085.Setup VMware Update Manager extension to VMware Virtual Center Server: <server IP>". Then it fails with "Warning 25015.VMware Update Manager could not be installed." There's no indication of why it won't install.
I also can't get the VMware Converter Enterprise for Virtual Center to install. The error is: "Error 25085.Failed to to register the extension."
Anyone know what's wrong here?
Logon as the local administrator and try it.
Don Pomeroy
VMware Communities User Moderator
I would also like to point out that I got the exact same issues.
Of note - having the same issue here. Clean install on a brand new Windows 2003 Server, SP2.
Hi,
It would pay you to check that the account you are using to install the components has rights to log into Virtual Center.
Cheers
I'm using the same credentials I use to log in to Virtual Center, so it should work fine. Yet it does not.
Might sound like a silly question, but are these components installed on your VirtualCenter server? You probably won't be able to install the extension on your client if the component hasn't been installed on the VC server.
It does sound like a silly question because isn't this supposed to install those components?
Running the plugin installs on the VI client only performs the client-side installs of these components. There are also server-side components that need to be installed. The update manager installation is quite extensive, requiring you to choose where you want downloaded updates to be stored, where the SQL database is, etc.
That's what's being installed. It installs an MSDE 2005 database, etc etc. When you run the Virtual Center 2.5 install, it has the option to install these server components. That's what I'm trying to do, and that's what's failing with the above error messages.
I got the same error during the installation of the update manager component. Just before the error I got another message about an invalid command line parameter been passed to the SDK?
The Consolidation part installed fine, and from the Client I can install this component.
I have been using a clean Windows 2003 server.
Everything else is working fine.
If I try to start the installation process again, it tell me that the components are installed.
Also, if you go to the umds sub-directory off the insatllation ZIP, there vmware-UMDS.exe in there that appears to start the installation process as a stand alone process. This appears to complete, but NO update manager.
Anybody have any joy in resolving this
Nope, no luck here. These two components still won't install. I'm surprised this got released with a broken installer -- surely VMware tested this??
Hi,
I got the same error in the first place, but I forgot to include the domain name when entering the username. When logging on to VC this isn't necessary, but apparently with the extensions it is.
Franc.
I tried this too, with no avail. I tried both DOMAIN\username and username@domain.com and neither worked.
Logon as the local administrator and try it.
Don Pomeroy
VMware Communities User Moderator
That did the trick! And I even tried a couple other local admin accounts, but only the local "Administrator" account would do it. Thanks!
Did an upgrade from
"vmware virtual center 2.02 update2" -> "vmware virutal center 2.5"
windows 2003 standard
sql 2000 sp4
Installed -> vmware "virutal center 2.5" everything went ok but the "vmware update manager"
error 1
"Invalid command line argumet. Consult the windows installer SDK for detailed command line help.
press ok
error 2
"Warning 25015. VMware Update Manager could not be installed"
press ok
Well first i rebooted the machine and tried the install which failed.
Then i used a domain admin with virtual center admin rights, but that failed
Then i used the local administrator logged on localy with rdp / console (which is renamed) with virtual center admin rights, but that failed to!
any idears ?
I have resolved this on my system.
I got the SDK and other errors, but continued with the install and the only component that was not installed was the update service.
To resolve this I ran the VMware-UpdateManager.exe program from the vci directory on the installation CD or ZIP.
This installation worked and then I had access to the plugin.
YES great man it works for me too, dquirke resolved it for me
just execute the VMware-UpdateManager.exe installer
I think the normal installer has a little bug in it...
After 2 hours on the phone with Vmware support trying to figure this out, it turned out to be the administrator password used during the VC 2.5 install having special characters in it. Both update manager and the enterprise converter were failing. I tried installing the update manager exe manually but that didn't work either. Vmware confirmed this to be a problem with the VC 2.5 installer. So, change your admin password to just alphanumeric characters, do the install, then change the password back.
Another issue I just found out about while on the phone was apparently there is a CPU problem with DRS in ESX 3.5. Apparently causes high CPU usage, though I haven't seen that myself.
Hope this helps.
I am having a similar problem with Converter. I have both "Update Manager and Converter installed but only the "Update Manager" show up at the top of VC. Should I see both at the top or just the one? I have not added the Converter licenses to the licenses server as of yet, do I need to do that before I can see it?