Vmware virtualcenter server не стартует код ошибки 1000
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Cloud & SDDC
- :
- vCenter
- :
- vCenter™ Server Discussions
- :
- vcenter 5.5 service fails
Pascalloz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
since a couple of days our vcenter is reporting the following event:
The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (40001) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Transaction (Process ID 88) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction." is returned when executing SQL statement "SELECT MO_ID, MO_TYPE, TYPE_ID, ARRAY_ID, VALUE FROM VPX_TEXT_ARRAY WHERE MO_TYPE = ? AND MO_ID = ?"
the message resource is present but the message is not found in the string/message table
If i reboot the vcenter server all the services are starting normally also the vcenter server service, and after a x period of time, the service crashes and give us above error message. And we are unable to connect with the client
Alim786
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Have you got latest ESXi updates ?
Are you on ESXi 5.5 Update 1 ?
VCP6-DCV, VCP5, CCNA, MCTS 2008R2, MCSA 2008R2, CCA, ITIL. Please mark answer helpful or correct as appropriate.
Pascalloz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
yes i am, i installed it yesterday. we had the problems before the update, and after the update
Alim786
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Was this a new install of 5.5 or an upgrade ?
VCP6-DCV, VCP5, CCNA, MCTS 2008R2, MCSA 2008R2, CCA, ITIL. Please mark answer helpful or correct as appropriate.
Pascalloz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Everything is build up from scratch 3 months ago. So yes it a new install, on a new system.
And everything was running perfectly till a couple of weeks ago.
Alim786
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
It obviously points to a SQL Server issue. I am not a SQL DB person. I would just check that the ODBC connection is ok. I would look at the SQL server DB and check to see if any obvious errors. As it is 5.5 and not come across this before, logging a case with VMware might be the best course of action unless someone else can contribute.
VCP6-DCV, VCP5, CCNA, MCTS 2008R2, MCSA 2008R2, CCA, ITIL. Please mark answer helpful or correct as appropriate.
Pascalloz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
true, but i saw on the internet that there where people who had simmalir problems only with other versions of vcenter.
but i have look, and like you i am not a sql admin, so i have no idea how to solve the problem. Because from my point of view i also suspect the issue is in the database and not in the application of vcenter. We are running on SQL 2008 R2
And we also have another error message in the event viewer:
Faulting application name: vpxd.exe, version: 5.5.0.40799, time stamp: 0x5307e9e2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0xe06d7363
Fault offset: 0x000000000000940d
Faulting process id: 0x105c
Faulting application start time: 0x01cf4a753a553975
Faulting application path: D:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
rh5592
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
check the vCenter log file location and see if there are vpxd crash dump files. If you are seeing them everytime your vCenter service crashes then you have to open a ticket with Vmware support to have it investigated. I have a few open SR's with support also for vCenter 5.5 crash but the symptoms are not the same as the one you are experiencing.
Pascalloz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Well i have the same problem again. After the first time we had the problem i decided that to re-install vcenter, since i had documented the whole process. I deleted everything from the vcenter vm and re-installed everything with a new database. (i only kept the vum database. )
and for the first two weeks everything was running fine. And then it happens again, in the beginning it happend once, and then a couple of days nothing, and then it started to happen more frequently.at the point that now it happens 10mins after i restarted the vcenter server.
I created a call with vmware, but they only asked me some basic questions (how many hosts and vms, database size, log retention.) and that i should check with my db admin. which we dont have.
And yes there are vpxd cash dump files.
The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (40001) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Transaction (Process ID 81) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction." is returned when executing SQL statement "SELECT MO_ID, MO_TYPE, TYPE_ID, ARRAY_ID, VALUE FROM VPX_TEXT_ARRAY WHERE MO_TYPE = ? AND MO_ID = ?"
the message resource is present but the message is not found in the string/message table
Faulting application name: vpxd.exe, version: 5.5.0.40799, time stamp: 0x5307e9e2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0xe06d7363
Fault offset: 0x000000000000940d
Faulting process id: 0x1538
Faulting application start time: 0x01cf581553472e9b
Faulting application path: D:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Starting VMware VirtualCenter 5.5.0 build-1623101
the message resource is present but the message is not found in the string/message table
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Digital Workspace
- :
- Horizon
- :
- Horizon Desktops and Apps
- :
- Virtual center cannot start:error event id 1000
ify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
The description for Event ID ( 1000 ) in Source cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: age3.exe; 4.105.919.3236; age3.exe; 4.105.919.3236; 00013caf.
Troy_Clavell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
ify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Thanks, but we are using a different database.
SteveR55
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I have also ensured that my ODBC datasource for the VirtualCenter server is using the SQL native client. I have successfully tested this connection. I do have McAfee viruscan installed on the machine, but all related services are set to manual mode and the server has been rebooted with the same results. The SQL server database service starts successfully after the reboot.
Any more suggestions would be appreciated.
mdwasim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Even I am facing the same problem, recently I have updated the vCenter OS windows 2003 completely, along with SQL Express is also updated. while the updates were going on suddenly vcenter service went down..
I do have mcafee antivirus, when i try to restart service manually, I see that mcafee scan engine is getting active and red.. on checking, it shows error on "vpxd.exe could be stopped"..
I dont have IIS installed on vCenter server, SQL is on the same server.
I removed vCenter and reinstalled.. will check if this fix something for me.
nickparrott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I have encountered the same issue, and found that it was simply down to host resources. It may not be THE fix, but certainly fixed my issue!
- W2008 x64 R2, vCenter 4.0 build 4.0.0.7797 with SQL Express locally installed
- Initially, my vCenter VM was running with 2GB RAM (on vSphere 4.0) and upon boot, the vpxd (aka 'VMware VirtualCenter Server) was starting ok.
I reduced RAM to 512Mb (my vCenter is only handling a single ESX host and a handful of VMs. ) and upon reboot, the vpxd service doesn't start and I get an EventID 1000, with no detail about why the service failed to start.
Prior to reviewing logs further, I decided to increase the Windows global service timeout value (initially 30s, increased to 90s) and upon reboot, the service started no problem! See for further details. I've applied this fix on 2003 and 2008, both x86 and x64, for a number of different 'service starting issues'.
Due to a smaller amount of system memory, all services start slower, and I guess that the vpxd service suffered the same issue. Try this before doing anything else, as it's a quick fix and may be the root cause of the issue.
Granted, the vCenter requirements state that you need many more resources available, however on a heavily loaded system (even with 4 or 8Gb of RAM) it's possible that other services are using large chunks of memory, so you could be in a similar position. You will be required to reboot after the change, but you often need to do that to test the fix ayway.
Однажды после перезагрузки сервера vCenter, вы вдруг обнаруживаете, что не можете зайти на сервер vCenter при помощи клиента vSphere. После инспекции открытых портов и запущенных служб вы вдруг замечаете, что служба «VMware VirtualCenter Server» не запущена ( не смотря на то, что тип запуска установлен в автоматический). При попытке запустить ее вручную, служба поднимается и работает нормально, проблема наблюдается только в том что служба не стартует автоматом после перезагрузки сервера.
Event ID 1000 explains in the description, it could not get the configuration from the database:
Event Type: Error
Event Source: VMware VirtualCenter Server
The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error getting configuration info from the database.
Кроме того, в журналах событий вы можете увидеть следующие события:
Event Type: Error
Event Source: MSSQLSERVER
SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.
Event Type: Error
Event Source: Service Control Manager
The VMware VirtualCenter Server service terminated with service-specific error 2 (0x2).
Event Type: Error
Event Source: Service Control Manager
The VMware VirtualCenter Management Webservices service depends on the VMware VirtualCenter Server service which failed to start because of the following error:
The service has returned a service-specific error code.
Причина кроется в том, что база данных vCenter (SQL Server), работает на том же сервере что и сам vCenter.
После того как сервер начал загружаться – запускается служба SQL Server, однако этот процесс занимает некоторое время. И когда служба vCenter пытается автоматически стартовать, она попытает попытку соединится с базой данных SQL Server (которая еще не готова), и как следствие в журнале появляется событие с кодом 17187. И в результате, служба vCenter не запускается автоматически.
Это типичный случай так называемого «race condition» (состояние погони). vCenter пытается запуститься до SQL Server, от которого он зависит. В том случае, если ваш SQL Server установлен на другом сервере, то подобная проблема для вас неактуальна.
На вкладке свойств службы vCenter вы можете удостоверится, что не существует зависимости с SQL Server.
В качестве решения можно создать зависимость для службы «VMware VirtualCenter Server» от следующих служб: MSSQLSERVER и ADAM_VMwareVCMSDS
Тем самым мы обеспечим запуск службы «VMware VirtualCenter Server» только после загрузки всех необходимых для его работы сервисов.
Создаем зависимость службы:
Наберите «services.msc», нажмите кнопку ОК.
Найдите имена служб, от которых будет зависеть сервер vSphere, в нашем случае это MSSQLSERVER и ADAM_VMwareVCMSDS.
Перейдите в ветку HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd.
Найдите и измените ключ «DependOnService». Добавьте в него строки с именами тех служб, с которыми мы хотим создать зависимости.
Закройте редактор реестра.
На вкладке зависимости службы vCenter удостоверьтесь в том, что появились новые службы.
Теперь после перезагрузки сервера служба VMware VirtualCenter будет ждать старта всех служб, от которых она зависит, и вам не придется вручную стартовать ее.
Понадобилось мне перезагрузить сервер «vCenter», но после перезагрузки я обнаружил, что посредством клиента «vSphere Client» не могу подключиться к vCenter’у. Подключившись напрямую к esxi (на нем развернута виртуальная машина на базе «Windows Server 2008 R2 Ent» и на ней поднят vCenter) и уже оттуда подключившись к системе, обнаружил, что служба «VMware VirtualCenter Server» имеет состояние «Остановлена», хотя должна запускаться в автоматическом режиме….
Для дальнейшего анализа решил проанализировать проблему на уровне логов системы, что они говорят.
«Пуск» – «Панель управления» – «Администрирование» – «Диспетчер сервера» – «Диагностика» – «Просмотр событий» – «Журналы Windows» – «Приложения» ошибки с кодом «Event ID» = «1000» ниже следующего вида:
Если же запустить службу вручную, то она поднимается и работает нормально, проблема воспроизводится, если я перезагружаю сервер. В ходе анализа и поиска решений на просторах интернета был выведен результат, не дающий появлению такого рода ошибок.
В эго основе лежит запустить службу «SQL Server», а уже потом запускать службу «VMware VirtualCenter Server» (а было по другому), т.е. сделать зависимость.
Открываем оснастку управления службами на сервере :
«Пуск» – «Панель управления» – «Администрирование» – «Диспетчер сервера» – «Конфигурация» – «Службы».
Для службы «SQL Server (MSSQLSERVER)» открываем «Свойства» и копируем в буфер обмена поле «Имя службы»
Теперь открываем редактор реестра:
«HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd»
В значении «DependOnService» вписываем то значение которое у нас находится в буфере обмена («MSSQLSERVER»)
В итоге у службы «VMware VirtualCenter Server» во вкладке «Зависимости» появилась зависимость от службы «SQL Server (MSSQLSERVER)».
- Агент SQL Server (MSSQLSERVER)
- SQL Server (MSSQLSERVER)
- Службы SQL Server Analysis Services (MSSQLSERVER)
- Службы SQL Server Integration Services 10.0
Теперь после перезагрузки сервера служба «VMware VirtualCenter» будет ждать старта всех служб, от которых она зависит, и вам не придется вручную стартовать ее. На этом всё, удачи.
Используйте прокси ((заблокировано роскомнадзором, используйте vpn или proxy)) при использовании Telegram клиента:
Поблагодари автора и новые статьи
будут появляться чаще :)
Карта МКБ: 4432-7300-2472-8059
Большое спасибо тем кто благодарит автора за практические заметки небольшими пожертвованиями. С уважением, Олло Александр aka ekzorchik.
Tackling the daily challenges of technology. one project at a time.
Thursday, July 22, 2010
vCenter / Virtual Center Service fails to start with event ID: 1000, 7024, 7001, 18456
After having all the issues with distributed network switches and Nexus 1000v switches and vCenter / Virtual Center’s database on a SQL instance that’s on a different server, I decided to recommend to the client that we proceed with installing SQL onto the vCenter server’s operating system and use that to host the database. Since we’ve moved to this configuration, we noticed that the VirtualCenter and VirtualCenter Management Webservices services would never start upon a reboot:
I went ahead to review the logs and found the following:
Event ID: 1000
The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Failed to intialize VMware VirtualCenter. Shutting down.
the message resource is present but the message is not found in the string/message table
Event ID: 7001
The VMware VirtualCenter Management Webservices service depends on the VMware VirtualCenter Server service which failed to start because of the following error:
The service has returned a service-specific error code.
Event ID: 7024
The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified..
Event ID: 18456
Login failed for user ‘blah/svc_vmvc’. Reason: Failed to open the explicitly specified database.
Through reviewing the logs, it’s obvious that the database isn’t ready when the services are trying to start and therefore fails to do so. After having experienced something similar before with another client, I decided to simply set the VirtualCenter service to depend on the MSSQLServer service and since the VirtualCenter Management Webservices service depends on the VirtualCenter service, it will wait till until it has started before starting itself.
I went ahead to reboot the server after I modified the registry and added the dependencies only to find that the problem still continued to happen. I’m unsure as to why but I decided to try and change the service from Automatic:
…to Automatic (Delayed Start):
Once I completed this and restarted the server, the services began to start properly. There was one caveat though, and it was the VirtualCenter service starting properly 2 to 3 minutes after the server is reachable. In case the person reading this doesn’t know, the reason for this is because setting a service to Automatic (Delayed Start) means that it will wait till all of the other Automatic services are completed started before it will start and the Service Control manager also sets the priority of the initial thread for these delayed services to THREAD_PRIORITY_LOWEST.
Pages
Читайте также: