![event id 1000 vmware virtualcenter server event id 1000 vmware virtualcenter server](https://communities.vmware.com/wbsdv95928/attachments/wbsdv95928/2511/71977/2/SNAG-0006.png)
Now we just have to figure out why the VM rebooted but that’s another story. When finished i could copy files to my C: drive again and the vCenter Server started again so everything is back to normal. However, during the reboot the check disk ran for a very very short time and didn’t solve my problem so i ran check disk again using the scan option: Would you like to schedule this volume to beĬhecked the next time the system restarts? (Y/N)
![event id 1000 vmware virtualcenter server event id 1000 vmware virtualcenter server](https://mikeglinski.com/images/7a203a4244008b72ab337657f29c0781.png)
This command requires a reboot based on the following command output:Ĭhkdsk cannot run because the volume is in use by another The first action taken to solve the problem was running check disk using the following command:
![event id 1000 vmware virtualcenter server event id 1000 vmware virtualcenter server](https://www.rorymon.com/blog/wp-content/uploads/2020/01/Services-480x260.png)
17415, time stamp: 0x54505737įaulting application start time: 0x01d0bc80dd30a512įaulting application path: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exeįaulting module path: C:\Windows\system32\KERNELBASE.dll
#Event id 1000 vmware virtualcenter server windows#
I also found a lot of entries in the Windows Server Event Log e.g.:įaulting application name: vpxd.exe, version: 5.9, time stamp: 0x54b90698įaulting module name: KERNELBASE.dll, version. vCenter Server, log files could be created:) So it was obvious that we had problem with the C: drive but at least some, e.g.
![event id 1000 vmware virtualcenter server event id 1000 vmware virtualcenter server](http://www.adventuresinvmware.co.uk/wp-content/uploads/2013/01/VMware_EventID_1000.jpg)