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

Failed to verify Composer server certificate after upgrading to Horizon 7.x (2149331)

  • 1 Ratings

Symptoms

  • The View administrator System health dashboard displays the View Composer Server status in Red.
  • On verifying the Composer Server Certificate. It will display the message as:
     There was an error identifying the validity of the server
  • In the Horizon Connection server debug log, you see message similar to:
2017-02-21T15:31:30.358+08:00 DEBUG (01E8-15B4) <ajp-nio-8009-exec-2> [ViewFlexFactory] Error while attempting to connect to View Composer. 
    com.vmware.vdi.admin.ui.common.ViewFlexFactory$ViewProxy.invoke(SourceFile:125)
    com.vmware.vdi.admin.ui.common.FlexRemoteException: Error while attempting to connect to View Composer.

2017-02-13T16:17:06.983+08:00 DEBUG (13D0-0BCC) <ajp-nio-8009-exec-1590> [VCManager] SVI connection failed for SVI https://<FQDN_Composer>:18443
2017-02-13T16:17:06.984+08:00 DEBUG (13D0-0BCC) <ajp-nio-8009-exec-1590> [ViewFlexFactory] There was an error identifying the validity of the server. 
    com.vmware.vdi.admin.ui.common.ViewFlexFactory$ViewProxy.invoke(SourceFile:125)
    com.vmware.vdi.admin.ui.common.FlexRemoteException: There was an error identifying the validity of the server.

2017-02-08T09:01:28.218+08:00 ERROR (13D0-0A38) <Publish VC Cert Task-1486515658332> [PublishVcCertToSviFederatedTask] Unable to update VC certificate thumbprints on SVI server https://<FQDN_Composer>:18443 - (403)Forbidden

Caused by: (403)Forbidden
        at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:218)
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
        at org.apache.axis.client.Call.invoke(Call.java:2767)
        at org.apache.axis.client.Call.invoke(Call.java:2443)
        at org.apache.axis.client.Call.invoke(Call.java:2366)
        at org.apache.axis.client.Call.invoke(Call.java:1812)
        at com.vmware.SviService.Admin.v3_5.Binding.SslBasicAuthAdminEndpointStub.enumerateAdConfigEntries(SslBasicAuthAdminEndpointStub.java:1542)
        at com.vmware.vdi.admin.ui.bean.VCServerBean.a(SourceFile:1181)

Cause

This issue may occur due to configuration issue with UPN style and Domain level name format which affects how global catalogs searches the NT user account.

Resolution

To resolve this issue, Change composer username in the ADAM (pae-SVIUsername) from Domain level format (domain\user) to UPN format (user@domain.com).
  1. Connect to the ADAM database in Connection server. How to Connect to ADAM database, see Connecting to the view adam database (2012377)
  2.  Expand the OU=VirtualCenter,OU=Properties,DC=vdi,DC=vmware,DC=int
  3.  Right click the entry CN= and select Properties
  4.  In the Attribute Editor change the value of pae-SVIUserName from the Domain level format to UPN format.
  5.  Save and close. 
In the dashboard of View Administrator console, the Composer status will return to green.

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.

Feedback

  • 1 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.
  • 1 Ratings
Actions
KB: