Skip to content
Rorymon Logo
  • Blogroll
  • About
  • Contact
Menu
  • Blogroll
  • About
  • Contact
Twitter
Linkedin
Rss
  • All Articles
  • Applications
    • App Compatibility
    • App Deployment
    • App Virtualization
      • App-V
        • Decision Matrix
        • App-V 4.x Recipes
        • App-V 5.x Recipes
        • App-V Videos
      • AppSense StrataApps
      • Cameyo
      • Evalaze
      • Frame
      • Numecent CloudPaging
      • P-Apps
      • ThinApp
      • Turbo
      • Workspace Streaming
      • XenApp Profiling
    • Containers
    • Layering
      • App Volumes
      • Citrix App Layering
      • FlexApp
      • Unidesk
  • Citrix
    • AppDNA
    • Citrix App Layering
    • Citrix Monitoring
    • Citrix Profiling
    • Citrix XenApp
  • Microsoft
    • ACT
    • Azure
    • BitLocker
    • Hyper-V
    • inTune
    • MDOP
      • AGPM
      • APP-V
      • DaRT
      • MBAM
      • MED-V
    • RDS
    • System Center
      • SCCM
      • SCOM
    • WDS
    • Windows
      • Windows 7
      • Windows 8
      • Windows 10
      • Windows Server 2012
  • VMware
    • App Volumes
    • ThinApp
  • Downloads
  • Podcast

VMware VirtualCenter Server Service Failing to Start

  • Rory Monaghan
  • January 8, 2020
Share on reddit
Share on facebook
Share on twitter
Share on linkedin
VMware

The Issue

This one likely won’t be useful to many out there. It’s an issue I encountered with vCenter 5.x which manifested itself after the install of Windows Updates and caused a down time for my VMware Horizon environment.

We could see something was wrong due to the vCenter Server showing down in the VMware Horizon Admin Console. When checking on the vCenter service itself, it looked like the VMware VirtualCenter Server service was not started. When trying to manually start the service, it was getting stuck on starting the service for several minutes and failed. You may also see event errors with ID: 1000.

The Cause

It turns out, a Windows Update enabled the built in Windows BranchCache feature. By going to the Non-Plug and Play Drivers in Device Manager and going into HTTP as seen above, we could see what was trying to use the HTTP protocol. (I was a little surprised as our environment uses HTTPS but it looks like vCenter still relies on port 80 when starting). Checking in here showed that BranchCache was butting in and taking over port 80 which was causing vCenter to fail to start. (Thank you VMware support for showing me!)

The Workaround

Simple. Disable BranchCache again. Chances are it was already disabled in your older vCenter before the update re-enabled it anyway.

unsplash-logoNijwam Swargiary

 

vCenter Service Not Starting,VMware VirtualCenter Server service not starting
PrevPreviousEpisode 105 – 2 Year Anniversary, The Week’s News, 2019 Review & More
NextEpisode 106 – Chrome 80 Could Break Sites, Ransomware Closes a Company, New NUC & MoreNext
Rory Monaghan

Rory Monaghan

Microsoft MVP. Citrix CTA. IGEL Insider. VMware EUC Champion & vExpert.
Twitter
Linkedin
Rss
Vimeo
Youtube
Soundcloud

Get the App-V Decison Matrix and Interactive Tool.

See what the right deployment option for your applications is.
Let's Go!
FREE TOOL
Further Reading

Windows 10 Migration Checklist

Application packaging and virtualization services.
Learn More

Let's make virtualization EASIER!

Be amongst the first to know when I publish new reviews, guides and tools to simplify your virtualization projects.

Categories
  • All Articles
  • Application Compatibility
  • Application Virtualization
  • Containers
  • Citrix XenApp
  • Application Layering
Connect
  • Blogroll
  • About
  • Contact
Twitter
Linkedin
Rss
Vimeo
Youtube
Soundcloud
© Copyright Rorymon.com. All rights reserved 2021.
Privacy   |   Cookies
Marketing Services by Riabro.