VMware Update Manager not getting started on the windows machine
Article ID: 312006
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
The Update Manager service is not getting started on 6.5 and 6.7 releases for windows machines, if Update Manager and vCenter Server are running on different machines.
Symptoms:
If Update Manager and vCenter Server are running on different machine, then Update Manager service crashes during start.
The stack trace from vum core dump generated -
STACK_TEXT:
00000065`97dfc9b0 00007ffb`82a79fd1 vmacore!Vmacore::System::DoCoreDump+0x91
00000065`97dfd000 00007ffb`82a7a5af vmacore!Vmacore::System::GenerateCore DumpImpl+0x41f
00000065`97dfd2b0 00007ffb`82a7a17a vmacore!Vmacore::System::GenerateCoreDump+0x3a
00000065`97dfd2f0 00007ffb`82a812ae vmacore!Vmacore::PanicExit+0x2e
00000065`97dfd350 00007ffb`82a890ed vmacore!Vmacore::System::SETranslator+0x3fd
00000065`97dfd450 00007ffb`9852f2e5 msvcr120!_CallSETranslator+0x3d
00000065`97dfd4c0 00007ffb`9852dbc7 msvcr120!FindHandlerForForeignException+0x9f
00000065`97dfd570 00007ffb`9852dadc msvcr120!FindHandler+0x468
00000065`97dfd660 00007ffb`9852ed64 msvcr120!__InternalCxxFrameHandler+0x208
00000065`97dfd6c0 00007ffb`9852f5d7 msvcr120!__CxxFrameHandler3+0x77
00000065`97dfd710 00007ffb`80aff156 vci_vcIntegrity!__GSHandlerCheck_EH+0x6e
00000065`97dfd740 00007ffb`b5402f2d ntdll!RtlpExecuteHandlerForException+0xd
00000065`97dfd770 00007ffb`b53c4547 ntdll!RtlDispatchException+0x197
00000065`97dfde40 00007ffb`b54020ba ntdll!KiUserExceptionDispatch+0x3a
00000065`97dfe540 00007ffb`806d9991 vci_vcIntegrity!Integrity::ManagedJetty::Start+0x9d1
00000065`97dfe8c0 00007ffb`80613864 vci_vcIntegrity!Integrity::VcIntegrityImpl::GetManagedProcesses+0x8c4
00000065`97dff180 00007ffb`8060f00c vci_vcIntegrity!Integrity::VcIntegrityImpl::VcIntegrityImpl+0x72c
00000065`97dff4c0 00007ffb`80612627 vci_vcIntegrity!Integrity::CreateVcIntegrity+0x37
00000065`97dff500 00007ffb`805ad18b vci_vcIntegrity!Integrity::VcIntegrityPlugin::Init+0x2eb
00000065`97dff950 00007ffb`82897b9c vmacore!Vmacore::Service::AppImpl::InitPlugins+0x5c
00000065`97dff990 00007ff6`a9833099 vmware_updatemgr!Vmacore::Service::LoadPlugins+0x49
00000065`97dff9d0 00007ff6`a983475b vmware_updatemgr!Sysimage::UfadRun+0x59b
00000065`97dffc00 00007ff6`a983a129 vmware_updatemgr!Sysimage::CService::ServiceMain+0x3c9
00000065`97dffed0 00007ffb`b2e27aca sechost!ScSvcctrlThreadA+0x3a
00000065`97dfff00 00007ffb`b4bd13d2 kernel32+0x13d2
00000065`97dfff08 00007ffb`b2e27a8f sechost!ScRemoveDispatchEntry+0x5e
00000065`97dfff38 00007ffb`b4bd13b0 kernel32+0x13b0
Symptoms:
If Update Manager and vCenter Server are running on different machine, then Update Manager service crashes during start.
The stack trace from vum core dump generated -
STACK_TEXT:
00000065`97dfc9b0 00007ffb`82a79fd1 vmacore!Vmacore::System::DoCoreDump+0x91
00000065`97dfd000 00007ffb`82a7a5af vmacore!Vmacore::System::GenerateCore DumpImpl+0x41f
00000065`97dfd2b0 00007ffb`82a7a17a vmacore!Vmacore::System::GenerateCoreDump+0x3a
00000065`97dfd2f0 00007ffb`82a812ae vmacore!Vmacore::PanicExit+0x2e
00000065`97dfd350 00007ffb`82a890ed vmacore!Vmacore::System::SETranslator+0x3fd
00000065`97dfd450 00007ffb`9852f2e5 msvcr120!_CallSETranslator+0x3d
00000065`97dfd4c0 00007ffb`9852dbc7 msvcr120!FindHandlerForForeignException+0x9f
00000065`97dfd570 00007ffb`9852dadc msvcr120!FindHandler+0x468
00000065`97dfd660 00007ffb`9852ed64 msvcr120!__InternalCxxFrameHandler+0x208
00000065`97dfd6c0 00007ffb`9852f5d7 msvcr120!__CxxFrameHandler3+0x77
00000065`97dfd710 00007ffb`80aff156 vci_vcIntegrity!__GSHandlerCheck_EH+0x6e
00000065`97dfd740 00007ffb`b5402f2d ntdll!RtlpExecuteHandlerForException+0xd
00000065`97dfd770 00007ffb`b53c4547 ntdll!RtlDispatchException+0x197
00000065`97dfde40 00007ffb`b54020ba ntdll!KiUserExceptionDispatch+0x3a
00000065`97dfe540 00007ffb`806d9991 vci_vcIntegrity!Integrity::ManagedJetty::Start+0x9d1
00000065`97dfe8c0 00007ffb`80613864 vci_vcIntegrity!Integrity::VcIntegrityImpl::GetManagedProcesses+0x8c4
00000065`97dff180 00007ffb`8060f00c vci_vcIntegrity!Integrity::VcIntegrityImpl::VcIntegrityImpl+0x72c
00000065`97dff4c0 00007ffb`80612627 vci_vcIntegrity!Integrity::CreateVcIntegrity+0x37
00000065`97dff500 00007ffb`805ad18b vci_vcIntegrity!Integrity::VcIntegrityPlugin::Init+0x2eb
00000065`97dff950 00007ffb`82897b9c vmacore!Vmacore::Service::AppImpl::InitPlugins+0x5c
00000065`97dff990 00007ff6`a9833099 vmware_updatemgr!Vmacore::Service::LoadPlugins+0x49
00000065`97dff9d0 00007ff6`a983475b vmware_updatemgr!Sysimage::UfadRun+0x59b
00000065`97dffc00 00007ff6`a983a129 vmware_updatemgr!Sysimage::CService::ServiceMain+0x3c9
00000065`97dffed0 00007ffb`b2e27aca sechost!ScSvcctrlThreadA+0x3a
00000065`97dfff00 00007ffb`b4bd13d2 kernel32+0x13d2
00000065`97dfff08 00007ffb`b2e27a8f sechost!ScRemoveDispatchEntry+0x5e
00000065`97dfff38 00007ffb`b4bd13b0 kernel32+0x13b0
Environment
VMware vSphere 6.5.x
VMware vSphere 6.7.x
VMware vSphere 6.7.x
Cause
The issue exists because vmware-override-java.security file and its file path environment variable are missing in Update Manager machine.
Resolution
Currently there is no resolution for this issue.
Workaround:
1. Create a directory named 'java' in the VUM installed directory.
The likely location is "C:\Program Files\VMware\Infrastructure\Update Manager"
2. Create a file 'vmware-override-java.security' in the newly created 'java' directory with the
following content.
security.provider.10=com.vmware.provider.VMwareSecurityProvider
jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, \
DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
include jdk.disabled.namedCurves
3. Create a new system environment variable 'VMWARE_CFG_DIR' and set it to the VUM installed
location. Example: "C:\Program Files\VMware\Infrastructure\Update Manager".
4. Start VUM.
5. Restarted vsphereclient service as follows in VC machine
1. Go to --> C:\Program Files\VMware\vCenter Server\bin
2. Stop the "vsphere-client" service --> service-control --stop vsphere-client
3. Start "vsphere-client" service --> service-control --start vsphere-client
Workaround:
1. Create a directory named 'java' in the VUM installed directory.
The likely location is "C:\Program Files\VMware\Infrastructure\Update Manager"
2. Create a file 'vmware-override-java.security' in the newly created 'java' directory with the
following content.
security.provider.10=com.vmware.provider.VMwareSecurityProvider
jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, \
DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
include jdk.disabled.namedCurves
3. Create a new system environment variable 'VMWARE_CFG_DIR' and set it to the VUM installed
location. Example: "C:\Program Files\VMware\Infrastructure\Update Manager".
4. Start VUM.
5. Restarted vsphereclient service as follows in VC machine
1. Go to --> C:\Program Files\VMware\vCenter Server\bin
2. Stop the "vsphere-client" service --> service-control --stop vsphere-client
3. Start "vsphere-client" service --> service-control --start vsphere-client
Feedback
Yes
No
Powered by
