Search the VMware Knowledge Base (KB)
View by Article ID

View Composer service fails to start with the error: The process terminated unexpectedly (1038380)

  • 6 Ratings


  • Cannot start VMware View Composer service.
  • View Composer service fails to start.
  • You see one of these errors:

    • Error 1067: The process terminated unexpectedly
    • Internal View Composer error

  • The Event Viewer reports the error:

    Failed to perform vmware view composer module initialization Soap exception connecting to Virtual Center, URL=https://:443/sdk


This  issue occurs when the RSA hash for SviKeyContainer referenced in the SVI_VC_CONFIG_ENTRY table does not match the SSL certificate currently installed for View Composer.


To resolve this issue, you must create a new SviKeyContainer and replace the old SviKeyContainer entry with the new one.
To create a new SviKeyContainer and to replace the old SviKeyContainer entry with the new one:
Note: This procedure creates a new View Composer database to populate the SVI_VC_CONFIG_ENTRY table with correct contents. Ensure to back up the existing View Composer database before proceeding.

  1. Back up the current View Composer database.
  2. Uninstall View Composer.
  3. Create a new View Composer database and a DSN that Composer can utilize.
  4. Install View Composer using the new DSN and database.
  5. Disable and enable View Composer in the View Admin portal.

    For View 5.1 and later:
    • Disable/Enable virtual machine provisioning in the vCenter Server instance that is associated with the View Composer service.
      1.  In View Administrator, click View Configuration > Servers.
      2. In the vCenter Server tab, select the vCenter Server instance.
      3. Click Disable provisioning to disable or click Enable Provisioning to enable.

    For View 5.0 and earlier:
    • Disable/Enable composer
      1. In View Administrator, click View Configuration > ServersvCenter Servers.
      2. Click Edit tab
      3. Deselect Enable View Composer to disable or select Enable View Composer to enable.
      4. Press OK.

  6. Copy the entire row in the SVI_VC_CONFIG_ENTRY table of the new View Composer database and import it to the SVI_VC_CONFIG_ENTRY table of the old View Composer database.
  7. In the old View Composer database, copy the GUID of the new entry in the SVI_VC_CONFIG_ENTRY table and use that value to overwrite the current value in the VC_CONFIG_ID column of the SVI_REPLICA and SVI_DEPLOYMENT_GROUP tables.
  8. Delete all old rows in the VC_CONFIG_ENTRY table.
  9. Disable View Composer in the View Admin portal. See step 5 of this article for steps.
  10. Uninstall and reinstall View Composer using the old DSN and old database.
  11. Enable View Composer in the View Admin portal.

Additional Information

For related information, see the VMware Communities thread Composer service cannot access Soap.



See Also

Update History

10/20/2011 - Added additional error to Symptoms and View Manager 5.0 to Products 10/09/2012 - Added View Manager 5.1.x to Product Versions 01/29/2013 - Clarified step 5 in resolution section for different versions of View

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 6 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 6 Ratings