"Protocol Failure" in Horizon View Administrator

[BriansVblog]

Lately I've had random VMs showing their View Agent status being "Protocol Failure."  The View Agent logs show the following:

06/02/2014, 13:54:05.773> LVL:2 RC: 0           VGMAC :Agent selected interface address: 169.254.123.87

06/02/2014, 13:54:05.773> LVL:2 RC: 0        MGMT_ENV :Setting ENV variable[  4]: pcoip.ip_address = 169.254.123.87

06/02/2014, 13:54:05.773> LVL:2 RC: 0        MGMT_ENV :Setting ENV variable[  5]: pcoip.address_given = 1

06/02/2014, 13:54:05.773> LVL:1 RC:-500           VGMAC :tera_sock_bind() failed for 169.254.123.87 - Can't assign requested address!

06/02/2014, 13:54:05.773> LVL:2 RC: 0          COMMON :tera_sock_socket_close() failed - Socket operation on non-socket (code 10038); treating socket as closed.

06/02/2014, 13:54:05.773> LVL:1 RC:-500 MGMT_PCOIP_DATA :ERROR: Failed to open UDP socket

06/02/2014, 13:54:05.773> LVL:1 RC:-500 MGMT_PCOIP_DATA :Failed to prepare for connections

06/02/2014, 13:54:05.773> LVL:0 RC:-500          ASSERT :Assert at function init_managers at line number 237.

06/02/2014, 13:54:08.815> LVL:0 RC:-500          COMMON :Critical Exception/Reset Detected!! Saving a minidump file...

06/02/2014, 13:54:11.139> LVL:0 RC:-500          COMMON :Minidump File saved as C:\ProgramData\VMware\VDM\logs\pcoip_server_2014_06_02_0000054c.txtpcoip_server_2014_06_02_0000054c.dmp

Is the error because of the 169.254.123.87 APIPA?  Usually a restart of the VM resolves the issue, however I'm trying to get to the bottom of it.  This is a Horizon View 5.3 environment.  Thanks in advance for any help.

[Linjo]

It does look like its because of the APIPA adress, do you have more then 1 vNic on the desktop or any other reason why the APIPA-adress would come up?

// Linjo

[TTT10]

Hello,

I've got the same error but without an APIPA... do you have a solution for your connection error?

[Linjo]

What version of view are you running?

[TTT10]

Well, we are running View in 5.3. Now I've seen, that we sometimes also get an APIPA in the log errors.

We have *only* one network adapter in the VM - but this one is called "Network Connection 2" in Windows 7. (this network adapter has the correct IP settings) ... but the numbering is a little bit strange to me. What do you think?

Will the View Agent sometimes grab the IP from "Network Connection 1" which is NOT visible in the GUI?

[Linjo]

Could it be related to this MS KB? Ghost NIC seen on Windows 7/Windows 2008 R2 machines built from VMWare Templates when the Template ...

[TTT10]

Thanks for your idea. Well, maybe it is or maybe not. But personally I think - regardless why this is number #2 - the PCoIP agent should take the correct IP address and not an APIPA after I have tied the PCoIP agent to the correct subnet (key: HKLM\Software\VMware, Inc.\VMware VDM\Node Manager\subnet) but without success...