Can I please request some assistance in resolving this issue? I've been trying to update my Windows Server 2012 R2-based vCenter Server from 6.0 Update 2 to 6.0 Update 2a and it constantly fails when installing the vCenter Server component. I keep getting a 3010 error. I have tried clearing out all temp files on the server, and performed numerous reboots to no avail. I have attached a screenshot below and the log file generated after the rollback procedure.
Finally I have successfully figured out how to upgrade my system! After poking through the logs I found the following info:
vminst.log
2016-12-03 09:04:01.950-05:00| vcsInstUtil-4541944| E: LaunchPkgMgr: Operation on vmware-vpxd.msi appears to have failed: 3010 (0x00000bc2)
2016-12-03 09:04:01.950-05:00| vcsInstUtil-4541944| I: PitCA_MessageBox: Displaying message: "Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details.
pkgmgr-comp-msi.log
MSI (s) (B4:DC) [01:37:54:043]: File: C:\Program Files\VMware\vCenter Server\vpxd\vmeventmsg.dll; Overwrite; Won't patch; Existing file is a lower version
MSI (s) (B4:DC) [01:37:54:043]: Source for file 'vmeventmsg.dll' is compressed
MSI (s) (B4:DC) [01:37:54:043]: Re-applying security from existing file.
MSI (s) (B4:DC) [01:37:54:043]: Note: 1: 2205 2: 3: Error
MSI (s) (B4:DC) [01:37:54:043]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1603
MSI (s) (B4:DC) [01:37:57:152]: Verifying accessibility of file: vmeventmsg.dll
Info 1603.The file C:\Program Files\VMware\vCenter Server\vpxd\vmeventmsg.dll is being held in use. Close that application and retry.
MSI (s) (4C:74) [03:24:09:589]: Product: VMware-vpxd. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time.
MSI (s) (4C:74) [03:24:09:620]: Deferring clean up of packages/files, if any exist
MSI (s) (4C:74) [03:24:09:620]: MainEngineThread is returning 3010
So it looks as though in my case, the vmeventmsg.dll was being locked by a process which prevented it from restarting properly in order to process and complete the upgrade.
I first stopped the "vpxd" service on my server and then opened my SysInternals/Microsoft "Process Explorer" application, and did a search for "vmeventmsg.dll" and it returned a result, which showed me that an svchost.exe process was locking the .dll file. I then killed the thread/process from within the application and attempted run the upgrade again, this time having success.
I hope this helps you all! Please comment below if this helped and give a like!
-Alex
Could you please check any windows update is available on the server if available please update complete and do reboot twice .
Also verify that SSO is working properly or not
Try with simple installation option
I'm getting the same issue.
It isn't showing any windows updates are required and has been rebooted mutiple times.
wminst.log contains: -
wWinMain: MSE result of install of "X:\cVenter-Server\Packages\vmware-vpxd.msi" may have failed: 3010 (0x00000bc2)
and it roll's back from there.
I've look through the other logs, but can't find anything that contains any further details.
Are you trying mount the iso to any cd rom / virtual cd rom .
download a fresh one and please extract the complete folder to c:\ and run the installer from command prompt (cmd run as admin )
Note- Also clear temp and vmware update relared cache and temp from %appdata% do reboot and try
Same here RAJ_RAJ, There are no available updates on the server, it is fully patched. I have tried mounting the ISO to the DVDROM drive, double-clicking the ISO to mount to a new virtual drive, and extracting the ISO first and running the installer as admin. Nothing seems to work.
We already have SRs opened for this issue and team is working on it.
guruswapanvi - thanks, are there any updates yet to this issue on the SR? I am still having issues and would like to upgrade my vCenter ASAP. Please advise. Thanks
Could you please attach the logs
Hello everything
i have the same issue
are there any updates yet to this issue on the SR?
the log files can be uploaded?
Thanks
hi everyone,
we are experiencing the same issue here.
server = windows server 2012 r2
update = vcenter 6.0 u2 to 6.0 u2a
error 3010 while updating the vcenter server component (vpxd).
thanks for a fix or a hint to a solution,
raoul.
Hi Raoul,
Have verified the health of the database,
like proper creds are being used.
test the database.
test the schema is having appropriate permission.
Regards
Basavaraj.R Navalgund
Banavalg@yahoo.com
Hi Raoul,
As error is not taking us to pin point any particular issue, how about reinstalling the windows server,??
However.
Please update if you have already issue has been resolved and how as we are bit curious to know the resolution.Thanks
Regards
Basavaraj.R Navalgund
Please review the pkgmgr-comp-msi.log that's generated in %temp% during installation and it should help in diagnosing the cause of the issue. Please share the log if possible.
Try the following:
1) Reboot Windows prior to the upgrade and see if it works on the next attempt.
2) If it's still failing then on the vCenter Server installation media navigate to D:\vCenter-Server\Packages\ and install vmware-python.msi on it's own. Reboot Windows. Now attempt an upgrade again.
If problems still exist then review pkgmgr-comp-msi.log for messages such as " is being held in use. Close that application and retry" and identify any process holding a lock on a file.
i tried both recommendations:
1) reboot before upgrade --> no success
2) install vmware-python.msi before main upgrade --> no success
then i took a closer look at the log file "pkgmgr-comp-msi.log" and found this:
Action ended 12:00:05: INSTALL. Return value 1.
MSI (s) (CC:98) [12:00:05:481]: Reboots are not supported from a multi-package transaction. A reboot request was suppressed automatically.
MSI (s) (CC:98) [12:00:05:481]: Note: 1: 1707
MSI (s) (CC:98) [12:00:05:481]: Note: 1: 2205 2: 3: Error
MSI (s) (CC:98) [12:00:05:481]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1707
MSI (s) (CC:98) [12:00:05:481]: Note: 1: 2205 2: 3: Error
MSI (s) (CC:98) [12:00:05:481]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (CC:98) [12:00:05:481]: Product: VMware-vpxd -- Installation completed successfully.
MSI (s) (CC:98) [12:00:05:481]: Windows Installer installed the product. Product Name: VMware-vpxd. Product Version: 6.0.0.7882. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 0.
MSI (s) (CC:98) [12:00:05:481]: Value of RebootAction property is
MSI (s) (CC:98) [12:00:05:481]: Windows Installer requires a system restart. Product Name: VMware-vpxd. Product Version: 6.0.0.7882. Product Language: 1033. Manufacturer: VMware, Inc.. Type of System Restart: 2. Reason for Restart: 1.
MSI (s) (CC:98) [12:00:05:481]: Product: VMware-vpxd. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time.
MSI (s) (CC:98) [12:00:05:512]: Deferring clean up of packages/files, if any exist
MSI (s) (CC:98) [12:00:05:512]: MainEngineThread is returning 3010
MSI (s) (CC:D0) [12:00:05:512]: RESTART MANAGER: Session closed.
MSI (s) (CC:D0) [12:00:05:512]: RESTART MANAGER: Session closed.
=== Logging stopped: 19.12.2016 12:00:05 ===
MSI (c) (D0:8C) [12:00:05:512]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D0:8C) [12:00:05:512]: MainEngineThread is returning 3010
MSI (c) (D0:48) [12:00:05:528]: RESTART MANAGER: Session closed.
=== Verbose logging stopped: 19.12.2016 12:00:05 ===
it seems that something is prohibiting a required restart, deferring it to "later" and thus lets the main installer think that the installation went wrong.
do others see the same log entries?
cheers,
raoul.
Raoul, I'm seeing the same exact error.
I have the exact same error.
Hello Raoul
Have the same error.
Are there new findings for troubleshooting?
MSI (s) (1C:18) [09:44:45:532]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1707
MSI (s) (1C:18) [09:44:45:532]: Note: 1: 2205 2: 3: Error
MSI (s) (1C:18) [09:44:45:532]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (1C:18) [09:44:45:532]: Product: VMware-vpxd -- Installation completed successfully.
MSI (s) (1C:18) [09:44:45:532]: Windows Installer installed the product. Product Name: VMware-vpxd. Product Version: 6.0.0.7882. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 0.
MSI (s) (1C:18) [09:44:45:532]: Value of RebootAction property is
MSI (s) (1C:18) [09:44:45:532]: Windows Installer requires a system restart. Product Name: VMware-vpxd. Product Version: 6.0.0.7882. Product Language: 1033. Manufacturer: VMware, Inc.. Type of System Restart: 2. Reason for Restart: 1.
MSI (s) (1C:18) [09:44:45:532]: Product: VMware-vpxd. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time.
MSI (s) (1C:18) [09:44:45:547]: Deferring clean up of packages/files, if any exist
MSI (s) (1C:18) [09:44:45:547]: MainEngineThread is returning 3010
MSI (s) (1C:B0) [09:44:45:547]: RESTART MANAGER: Session closed.
MSI (s) (1C:B0) [09:44:45:547]: RESTART MANAGER: Session closed.
Thank you Heinz
Hello everyone
Found the error.
The new article with the JRE files does not lead to success.
The reason is the "vmeventmsg.dll" as in the logfile "pkgmgr-comp-msi.log".
"C: \ Program Files \ VMware \ vCenter Server \ vpxd \ vmeventmsg.dll is the following:" Close that application and retry. "
Have renamed DLL and created a new copy. Under Security permissions Everyone full control.
Now runs the setup succesfully.
The "vmeventmsg.dll" gets a newer version
From: 10.0.0.6118 - build: 3634793
To: 10.0.0.7882 - build: 4541947
Mfg: Heinz
Hi.
I tried 4 times to install update - and got every times 3010 errors.
Today I rebooted server, I cleaned the Temp folders, disabled UAC in Windows.
I renamed vmeventmsg.dll and copied copy of it into the vmeventmsg.dll.
Then I rebooted Windows again.
After that I could successfully install update.