Corrupt Snapshot Causing View Composer Service Crash

Error during provisioning:Unexpected VC fault from View Composer

The above error might show up in Horizon View, if you try to use a corrupt snapshot for the deployment of new VMs.

How To Identify If  A Corrupt Snapshot Is The Cause?

  • Look at the Microsoft System Event Log on your View Composer
    • You should see something like this:

      The VMware View Composer service terminated unexpectedly. M It has done this 2 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.


  • Search for FATAL messages in the vmware-viewcomposer.log
    • The following message will indicate a corrupt snapshot

      2015-10-06 17:52:53,956 | WFE thread 9 | FATAL | ServiceCore.WorkflowEngine.WorkflowEngine – Unexpected exception occurred.Error reading single property ‘config.hardware.device’ from managed object: snapshot-15587


Read More

Speed Up Your Horizon View Operations

How to speed up your Horizon View operations, you might ask? Well, you don’t have to buy an all-flash storage system or beef up your ESX hosts.

VMware Horizon View Administrator has some settings on max concurrent operations with vCenter and VMware View Composer. Increasing some of those settings can decrease the time of those operations, however when decreasing those settings, you can limit the amount of IOPs pushed to your underlying storage system, too.

Screen Shot 2015-06-26 at 5.22.46 PM

Read More