Skip to main content

Error 1067 unable to start the VMware Virtual center Server Service

Error 1067  unable to start the VMware Virtual center Server Service
I got a call that our Vcenter server  is not working. and I felt ohh thats it….let me start the Vcenter service. I noticed vcenter service was not started and i tried to start the service, it is throwing the below error.
“Windows Could not start the VMware VirtualCenter service on local computer. Error 1067: the process terminated unexpectedly”


I wont say the below is the standard to follow to troubleshoot the issue. It was the approach which i used to resolve the above issue.
Troubleshooting Step 1:
 My first place to troubleshoot the Vcenter service failure is “vpxd.log” on the below location
Windows 2003 – C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs
Windows 2008 – C:\ProgramData\VMware\VMware VirtualCenter\Logs”
In VPXD logs, i found the below error

[2012-06-05 03:57:53.047 08104 error 'App'] Failed reading C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg. Line 33. class Vmacore::Xml::XMLParseException(mismatched tag)
[ 2012-06-05  03:57:53.047 08104 error 'App'] [VpxdMain] Failed to init vmacore
From the above Log, I noticed the line telling me something about the cause for this issue.
Failed reading C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg. Line 33. class Vmacore::Xml::XMLParseException(mismatched tag)
There is a  tag mismatched on the “vpxd.cfg” file. which is not allowing to start my vcenter service.

Troubleshooting Step 2:
I have started my investigation into my Vcenter server configuration file “Vpxd.cfg” and the error messge telling me that Line 33 is culprit so, I started targetting my line towards 30 to 35 in “vpxd.cfg” file.
===========================================================
==============================================================     
First, it looks like the culprit is the below line.
Tried to start the service But no luck again failed and the error message in the vpxd log is different this time
“the Duplicate loop error”
Troubleshhoting Step 3:
Again  my target is Vcenter configuration file “Vpxd.cfg”
===========================================================
==============================================================  
This time found the issue  and the issue is because of the loop # and # appears twice in Vcenter configuration file.Removed the extra loop and started the service. It started sucessfully and i am safe.
The issue appeared because of the configuration file of vcenter  was edited as part of standard hardening but edited with the wrong format sometime before and my server was rebooted as part of patching process.Configuration changes takes effect if you restart the Virtual center service. After the reboot, My Vcenter server service was not started.
Thanks for reading this article

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 ðŸ”¹ Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...