įor more information, see Help and Support Center at. Marcus indicated that the SQL server that housed the VMware DB was getting repetitive errors in it’s Event Logs that read as:ĭescription: Login failed for user ‘sa’. A few minutes later, our DBA, Marcus, was at my desk. So not knowing what else to do initially, I decided to put in a Change Management to reboot the server. I checked over the ODBC settings, and everything look correct and tested OK. The following information is part of the event: Failed to obtain database connection. You may be able to use the /AUXSOURCE= flag to retrieve this description see Help and Support for details. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. A close examination of the event logs showed that the following error was occurring every time I attempted to start the service.ĭescription: The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. It’s not too big of a deal since it usually starts right up again and all’s right with the world… except for yesterday.Īttempting to restart the service yielded nothing.
This is nothing new as (for some unknown reason I have yet to fathom) the VMware VirtualCenter Server service on my VCenter server will crash about once a month. Yesterday afternoon, I was minding my own business and working through a CBT, when I noticed that my personal VMware Infrastructure Client was suddenly disconnected. VMware VirtualCenter Server service won’t Start NovemPosted by General Zod in Storytime, Tech, VMware.
0 kommentar(er)
