Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The VMware vSphere Update Manager service fails to start. Each time you try to start the service, vmware-updatemgr-XX.dmp files are created. The %temp%vmware-vci-vciInstallUtils-log4cpp.log file contains entries similar to:3196 DEBUG] [installerRunXMLCommand, 435] [ConfigInfoFileManager] name = db_type, value = SQL Server Native Client 11.0 The C:\ProgramData\VMware\VMware Update Manager\Logsvmware-vum-server-log4cpp.log file contains entries similar to:'ProcessMonitor' 10296 WARN] [processMonitor, 127] Failed to open handle for process 8128. Error: 5. Ignoring the process'ProcessMonitor' 10296 INFO] [processMonitor, 472] Starting managed process java.exe'ProcessMonitor' 2076 INFO] [processMonitor, 245] Process monitoring started'SessionMgr' 10296 INFO] [sessionMgr, 80] GetSessionLocale: Initialized server locale object'InternalScheduledTasksMgr' 10296 INFO] [internalScheduledTasksMgr, 103] Internal Scheduled Task Manager created...'EmailAlertMgr' 10296 INFO] [emailAlertMgr, 278] Email alert manager created...'ConfigurationMgr' 10296 INFO] [configurationMgr, 152] Configuration manager created...'EntityLockingMgr' 10296 INFO] [entityLockingMgr, 62] Entity locking manager created...'vaCrypto' 10296 INFO] [vaCryptoSupport, 262] vaCrypto Initializing....'vaCrypto' 10296 INFO] [vaCryptoSupport, 243] Loaded VALM key C:\Program Files (x86)\VMware\Infrastructure\Update Manager\ssl\valm.key'HealthServiceMgr' 10296 INFO] [healthServiceMgr, 102] Health service manager created...'TaskStatsCollector' 10296 INFO] [taskStatsCollector, 74] Task statistics collector created...'Activation.trace' 10296 INFO] [activationValidator, 1263] Trace objects loaded.'VcIntegrityPlugin' 10296 INFO] [plugin, 252] VcIntegrityPlugin Init'VcIntegrityPlugin' 10296 INFO] [plugin, 282] Add callback to Ufa Shutdown manager.'VcIntegrity' 10296 INFO] [vcIntegrity, 809] Initializing database The C:\ProgramData\VMware\VMware Update Manager\Logsvmware-vum-server.log file contains entries similar to: <YYYY-MM-DD><time> [05032 error 'Default'] Unable to allocate memory: 4294967294 bytes</time><YYYY-MM-DD><time></time> [05032 info 'Default'] CoreDump: Writing minidump<YYYY-MM-DD><time></time> [05032 panic 'Default']Panic: Unable to allocate memoryBacktrace:backtrace[00] rip 68d93a7dbacktrace[01] rip 68c9fa5ebacktrace[02] rip 68ca1001backtrace[03] rip 68da5973backtrace[04] rip 68da5a6dbacktrace[05] rip 68da79e6backtrace[06] rip 6c321b1ebacktrace[07] rip 6c363e05backtrace[08] rip 6c363eb8backtrace[09] rip 6c3bfe93backtrace[10] rip 6c3c048fbacktrace[11] rip 6c3c6245backtrace[12] rip 6c3c62fdbacktrace[13] rip 6c3c6c86backtrace[14] rip 6c3c8d38backtrace[15] rip 669756ebbacktrace[16] rip 66975f16backtrace[17] rip 6695e75abacktrace[18] rip 667cf0c8backtrace[19] rip 667d95bdbacktrace[20] rip 667d9ea2backtrace[21] rip 667dbdc3backtrace[22] rip 666cc555backtrace[23] rip 68d58bacbacktrace[24] rip 68daac59backtrace[25] rip 68dad4e2backtrace[26] rip 68d58bacbacktrace[27] rip 68da1956backtrace[28] rip 6c323433backtrace[29] rip 6c3234c7backtrace[30] rip 76a08543backtrace[31] rip 77c7ac69backtrace[32] rip 77c7ac3c<YYYY-MM-DD><time></time> [05032 panic 'Default'] (Log recursion level 2) Unable to allocate memory Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue is resolved in: vSphere Update Manager 5.1 Update 2. For more information, see VMware vSphere Update Manager 5.1 Update 2 Release Notes. Download the latest version at VMware Downloads. vSphere Update Manager 5.5 Update 3. For more information, see VMware vSphere Update Manager 5.5 Update 3 Release Notes. Download the latest version at VMware Downloads. This is a known issue affecting vSphere Update Manager 5.0. Currently, there is no resolution. To work around this issue: Confirm the DSN for Update Manager is 32-bit. For more information, see Creating a 32bit DSN on a 64bit Windows machine (1010401). Use the SQL 2008 R2 Native Client 10 driver when creating the DSN to the Update Manager database if installing on Windows Server 2008 (SP1 or SP2) or Windows Server 2008 R2. Use the SQL Driver package pre-installed on Windows Server 2012 if you are installing on Windows Server 2012. With Windows Server 2012 use SQL 2008R2 SQL Native Client 10.0 when connecting against a SQL 2012 Server.
To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.Creating a 32bit DSN on a 64bit Windows machineSQL Server 2012 を使用している場合に VMware vSphere Update Manager 5.x の起動が失敗する使用 SQL Server 2012 时 VMware vSphere Update Manager 5.x 无法启动