Home > View Connection > View Connection Server Communication Error 5.1

View Connection Server Communication Error 5.1

Desktop tries to open, but immediately disconnects This section provides troubleshooting tips for the VMware View connector. 18.5.1. Error Messages18.5.1.1. But the Windows logs are your best hope for determining why Windows went unresponsive, for instance. Error connecting to VMware View Manager: http://ip_address//broker/xml: 404: Not Found In the event the software does not work as expected, look at the log messages located in the Sun Ray Our Software Unidesk and...

Failure Point #1: Network Connectivity between Client and Connection or Security Server Network connectivity is probably the most common issue you’ll run into. Failure Point #5: VM stuck in Customizing state On the other hand, if you find a VM stuck in the Customizing state, it is most likely because there just isn’t enough Post navigation « Previous Post Next Post » One Response to View 6.2.1. Upgrades failed and un-installing the current version did not succeed.

Or, more specifically, you can make sure that you can properly connect from the View Client machine to the Connection Server or Security Server. All View knows is that it cannot communicate. Detailed troubleshooting If the certificate verification fails, review the zero client logs and search for MGMT_VDMCSI and see why the zero client does not trust the VCS. All rights reserved.

By default, if you don’t specify a datastore to store the replica machines on, one replica will be created for each datastore that that pool is defined to use. Also check that there is enough free space on the datastore that you configured for the pool. If you are using VMware View 5.0 or earlier and you want to use HTTP, you must configure non-SSL connections as described in Section 18.3.2, “How to Enable Non-SSL Connections to the The VMware view Agent version should not be higher than the View Connection Broker version.

Check the Performance tab in vSphere to see if the CPU is pegged at 100%, for instance. Figure 2 The resolution for this error needs some explanation: From the VMware Horizon 6 Readme document: Items to watch out for when you install or upgrade to Horizon 6 version So the question becomes, why is the user's desktop not available? So while upgrading from View 6.0.1, the pre-existing message security mode should be retained!

The VCS trusted SSL root certificate must be uploaded to the zero client. Possible reasons the VCS is not trusted: 05/29/2012, 14:41:37> LVL:2 RC: 0 MGMT_VDMCSI :Trusted result: FAILED Self-signed certificate: the zero client trust store does not contain a copy of the server's Prev Up Next18.4. Configuring the VMware View Connector Kiosk Session Type Home Chapter 19. Alternate Network Configurations Copyright © 2013, Oracle and/or its affiliates. At this point, it was decided to check the View related firewall rules.

Active Directory and/or DNS is not set up properly on the desktop. While the PCoIP communications over UDP port 4172 goes on, PCoIP also opens up a heartbeat connection between the Client and the Agent using TCP port 4172. Again, this occurs over TCP port 443. Firmware 4.0.1 and newer will only check for a Server Authentication if the Extended Key Usage is defined.

For example, you’ll often get involved in activities like checking proxy and firewall settings as well as verifying whether DNS resolution works. Check This Out This could be in instances wherein DNS resolution may not be available. Citrix XenDesktop Citrix XenApp Microsoft VDI Microsoft Azure VMware Horizon Resources Webinars Ebooks Tools Training Customers Concierge Solutions For Healthcare For K-12 Education For Higher Education For Commercial For Legal For Check the certificate chain presented by the VCS to identify the root.

We changed it to issue SHA RSA instead. Failure Point #2: Network connectivity between Desktops and Connection Server When you run into network connectivity between a Desktop and the Connection Server, you’ll usually see issues within View Administrator where It certainly doesn't hurt to do this even if it doesn't help. Source Anyway, the first thing you should do is go to your VMware View Administrator web page and verify the state of the desktop in the pool.

This happens over several back and forth communications on TCP port 4172. Re: PCoIP client throws "View Connection Server communication error" bickyz Oct 14, 2014 12:39 PM (in response to Linjo) no I havent disabled/changed ciphers/encryption settingsLog says:2014-10-13T13:51:38Z> LVL:2 RC: 0 MGMT_VDM :INIT.INIT: And also on the Zero Clients make sure "Warn before connecting to untrusted servers" has been selected.

If you have a certificate that expires after the year 2099 then use firmware 4.0.2 or newer.

With the number of Desktops that View can spin up and down in a short period of time, it’s not unusual for a DHCP Scope to be used up fairly quickly. There are VMware KB’s like this one and numerous blog post on this subject, what worked for me was; Boot the parent VM in safe mode. This occurs over TCP port 4172. Occasionally, replicas can be orphaned and will need to be manually deleted from vCenter.

Reset to factory defaults on the client to clear the cached time. 05/29/2012, 14:41:37> LVL:2 RC: 0 MGMT_VDMCSI :Hostname result: FAILED The certificate's subject or Subject Alternative Name fields do not Convert to PEM if necessary Is the certificate less than 6 KB? This is the primary method of manipulating the pools and the Desktops within it. Next, verify that the policies within VMware View for the Global, Pool, and Individual user levels, all have USB Redirection enabled.

Go to View Configuration -> Global Settings and verify the setting. If you run into a resource constraint on your vCenter server, you may need to reduce the maximum number of concurrent provisioning and power operations within the View Administrator console.