Home > vCenter Server, vSphere > HOWTO: Fix pbm.fault.pbmfault.summary when cloning

HOWTO: Fix pbm.fault.pbmfault.summary when cloning

Let’s suppose you’re cloning some VM’s from a template, and you receive a “pbm.fault.pbmfault.summary” error and it fails. 

A very quick google search will find you the following VMware KB article. 


While it references the vCenter Server Appliance, and a DNS issue, the key portion is that it comments on the vCenter Server Inventory Service.


Which should certainly not be STOPPED, never mind what type of server it’s on or if DNS is working. 

Get that started, and there’s a good chance you won’t have to worry about if you’re on the appliance or have DNS issues. 

This is also probably a good time to look at your service failure handling:


Perhaps you want to automatically restart the service, send an e-mail, or restart the computer.  In any event, give some thought to how you’ll make this more self-healing in the future!

Categories: vCenter Server, vSphere
  1. Charlie
    October 9, 2015 at 8:17 AM

    Wonderful find. I wasn’t running the Virtual Center Appliance and DNS resolution looked to be fine through nslookup. You really helped me out in a bind. After starting the VMware vCenter Inventory Service, I was able to fire up VCenter and start the deployment without the error coming up.

  2. pat lav
    March 8, 2016 at 6:18 AM

    Thank you, this article really helped me out this morning.

    • March 8, 2016 at 7:10 AM

      Awesome. That’s always good to hear!

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: