Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Updating VMware vCenter Server 5.5 to vCenter Server 5.5 U2e fails to start the VMware Identity Management Service, VMware vCenter Inventory Service or VMware VirtualCenter Management Webservices. Updating vCenter Server 5.5 U2d using the VIMPatch-5.5.0-2646481-20150401 displays an error similar to: Error 29139. Could not start services. Several *.mdmp files are generated potentially filling the file system. These have been seen to be generated at the following locations. C:\Program Files\Common Files\VMware\VMware vCenter Server - tc Server\bin\winx86_64\C:\Program Files\VMware\Infrastructure\Inventory Service\Wrapper\bin\ The wrapper.log for the VMware VirtualCenter Management Webservices or VMware vCenter Inventory Service reports an error similar to the following: STATUS | wrapper | 2015/06/25 11:38:04 | Launching a JVM...INFO | jvm 5 | 2015/06/25 11:38:07 | #INFO | jvm 5 | 2015/06/25 11:38:07 | # A fatal error has been detected by the Java Runtime Environment:INFO | jvm 5 | 2015/06/25 11:38:07 | #INFO | jvm 5 | 2015/06/25 11:38:07 | # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006c7a2880, pid=10052, tid=4996INFO | jvm 5 | 2015/06/25 11:38:07 | #INFO | jvm 5 | 2015/06/25 11:38:07 | # JRE version: Java(TM) SE Runtime Environment (7.0_76-b13) (build 1.7.0_55-b32)INFO | jvm 5 | 2015/06/25 11:38:07 | # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.76-b04 mixed mode windows-amd64 compressed oops)INFO | jvm 5 | 2015/06/25 11:38:07 | # Problematic frame:INFO | jvm 5 | 2015/06/25 11:38:07 | # V [jvm.dll+0x52880]INFO | jvm 5 | 2015/06/25 11:38:07 | #INFO | jvm 5 | 2015/06/25 11:38:07 | # Core dump written. Default location: C:\Program Files\Common Files\VMware\VMware vCenter Server - tc Server\bin\winx86_64\hs_err_pid10052.mdmpINFO | jvm 5 | 2015/06/25 11:38:07 | #INFO | jvm 5 | 2015/06/25 11:38:07 | # An error report file with more information is saved as:INFO | jvm 5 | 2015/06/25 11:38:07 | # C:\Program Files\Common Files\VMware\VMware vCenter Server - tc Server\bin\winx86_64\hs_err_pid10052.logINFO | jvm 5 | 2015/06/25 11:38:07 | #INFO | jvm 5 | 2015/06/25 11:38:07 | # If you would like to submit a bug report, please visit:INFO | jvm 5 | 2015/06/25 11:38:07 | # http://bugreport.java.com/bugreport/crash.jspINFO | jvm 5 | 2015/06/25 11:38:07 | #ERROR | wrapper | 2015/06/25 11:38:07 | JVM exited while loading the application.FATAL | wrapper | 2015/06/25 11:38:07 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.FATAL | wrapper | 2015/06/25 11:38:07 | There may be a configuration problem: please check the logs.STATUS | wrapper | 2015/06/25 11:38:07 | A hs_err_pid_XXXXX.log referenced in the wrapper.log error may also be present and report similar to the following: ## A fatal error has been detected by the Java Runtime Environment:## EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006c7a2880, pid=10052, tid=4996## JRE version: Java(TM) SE Runtime Environment (7.0_76-b13) (build 1.7.0_55-b32)# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.76-b04 mixed mode windows-amd64 compressed oops)# Problematic frame:# V [jvm.dll+0x52880]## Core dump written. Default location: C:\Program Files\Common Files\VMware\VMware vCenter Server - tc Server\bin\winx86_64\hs_err_pid10052.mdmp## If you would like to submit a bug report, please visit:# http://bugreport.java.com/bugreport/crash.jsp#--------------- T H R E A D ---------------Current thread (0x0000000000b2f000): JavaThread "main" [_thread_in_vm, id=4996, stack(0x0000000000e40000,0x0000000000f40000)]siginfo: ExceptionCode=0xc0000005, reading address 0xffffffffffffffffRegisters:RAX=0x0000000000000054, RBX=0x0000000000000000, RCX=0xf045c748f0658b48, RDX=0x0000000008743360RSP=0x0000000000f3f3a8, RBP=0x0000000000b2f000, RSI=0x00000000d004b760, RDI=0x0000000008743360R8 =0x0000000000000029, R9 =0xfffffffff87fc0e0, R10=0x0000000008743360, R11=0x8101010101010100R12=0x0000000000000000, R13=0x0000000000b2f1e8, R14=0x0000000000000001, R15=0x0000000000f462d3RIP=0x000000006c7a2880, EFLAGS=0x0000000000010202
This is a known issue affecting VMware vCenter Server 5.5 Update 2e. Currently, there is no resolution. The following workaround can be implemented to update a vCenter Server 5.5 U2d system with the latest JRE version. If you are currently running a version of vCenter Server 5.5 prior to 5.5 U2d, it is required that you update to vCenter Server 5.5 U2d first and then apply the following workaround.Important: The only update between vCenter Server 5.5 U2d and vCenter Server 5.5 U2e is an updated JRE Build to patch JRE security vulnerabilities. Using the following workaround will not change the vCenter Server 5.5 Build Number. It will continue to display Build 2442329. The same would occur if you successfully applied VIMPatch-5.5.0-2646481-20150401. This is by design as the vCenter Server binaries are not changing.1. Backup or take a snapshot of the vCenter Server Machine.2. Stop the following VMware Services VMware vSphere Web ClientVMware Log BrowserVMware vSphere Update Manager ServiceVMware Profile-Driven Storage ServiceVMware VirtualCenter ServerVMware VirtualCenter Management WebservicesVMware vCenter Orchestrator ServerVMware vCenter Inventory ServiceVMware Secure Token ServiceVMware Identity Management Service 3. Confirm that no java.exe process is running via an elevated command prompt tasklist | findstr java 4. From the Windows Control Panel > Programs and Features, uninstall the VMware vCenter Server - Java Components5. Confirm that the directory C:\Program Files\Common Files\VMware\VMware vCenter Server - Java Components is completely removed. Rename the folder if it still remains.6. Mount the vCenter Server 5.5 U2e installation media7. Browse the Media to "Media\vJRE\"8. Launch the VMware-jre.exe and complete the installation accepting all defaults. Note: The VMware vCenter services will be started automatically by the VMware-jre installer.