vCenter 5.1 Single Sign On error during installation

Today vSphere 5.1 is released. I did an upgrade of my existing vSphere 5 vCenter server. During the installation of the vCenter Single Sign On (SSO) software the following warning occurred:

Error 29115: Cannot authenticate to DB.


After this error the installation stops and the rollback begins. To solve this make sure the server authentication checkbox is set to SQL Server and Windows Authentication mode on the SQL server.


Thanks to Gabrie van Zanten and Maish Saidel-Keesing for helping me out!

After upgrading to vCenter Server 5, “com.vmware.converter” alert

After upgrading to vCenter 5, the vCenter Service Status page displays the following error:


com.vmware.converter alert unable to retrieve health data from https:///converter/health.xml

This error occurs because the integrated vCenter Converter plug-in is no longer available in vSphere 5!  To solve this error  following the VMware KB article listed below:

Error after upgrading to vCenter Server 5.0: com.vmware.converter alert unable to retrieve health data – KB: 2006132

After following the KB article, the  converter plug-in is removed from the vCenter Service Status page.


Unable to join domain when deploy a template using guest customization specification

At a customer I was unable to join a domain when deploying a template from vCenter using a guest customization specification. This only happened with Windows 2008 R2 and Windows 7 templates.

To solve this problem, you need the do the following in the guest customization specification:

– Enter the FQDN name in Windows Server Domain field (1)

– Enter the user@domain_FQDN in the username field (2)


I used the NetBIOS domain name in the “Windows Server Domain” field and “domain\username” in the username field what doesn’t work with Windows 2008 R2 and Windows 7 anymore.

More information can be found here state that you need to fill in: