Horizon View 5.2 new install, protocol failure on desktops

[VirtualSven]

On a new Horizon View 5.2 deployment, I'm experiencing a "Protocol failure" status on all provisioned desktops. I have not enabled or installed HTML5 access, but in the debug log file of the virtual desktops, the following error is logged:

Failed to initialize BLAST server interface, protocol will not be available.

Which is expected behaviour, because I did not install the HTML5 feature pack. Can I disable Blast in the virtual desktops completely, so I will not have "Protocol failure" status on all my desktops?

I only want PCoIP enabled.

regards,

Sven

[mpryor]

Is it definitely the BLAST protocol that's the issue and not RDP or PCoIP? If that's the case you'd see something like this in the agent logs:

2013-06-26T14:19:19.795+01:00 DEBUG (06A0-06F8) <Thread-39> [ComponentResponse] Message is <?xml version="1.0"?><TERMINALRESPONSE>...<PROTOCOL><NAME>RDP</NAME><PORT>3389</PORT><STATUS>ready</STATUS></PROTOCOL><PROTOCOL><NAME>PCOIP</NAME><PORT>0</PORT><STATUS>negotiate</STATUS></PROTOCOL><PROTOCOL><NAME>BLAST</NAME><PORT>0</PORT><STATUS>error</STATUS></PROTOCOL> ...

If it is, how did you install the agent? There's a known issue in the 5.2.0 agent, where if you specify an explicit list of components on the command line such as ADDLOCAL=Core,PCoIP,USB,VPA,VmwVaudio,VmVideo,VMCI then you don't get the HTML access interface dll (needed for talking to the feature pack component), causing the protocol to be reported as in an error state even if the feature pack is not installed. You can include the Appblast component in the list to work around this.

[VirtualSven]

Yes, that is exactly how the View Agent is installed, with the ADDLOCAL=Core,PCoIP,USB,VPA,VmwVaudio,VmVideo properties. How can I add the appblast component to the list?

[mpryor · Accepted solution]

Try just adding it to the list in line when installing:

ADDLOCAL=Core,PCoIP,USB,VPA,VmwVaudio,VmVideo,Appblast

[VirtualSven]

Thanks, that was the solution!

[ChrisBCarlson]

did i miss something? i was having the same issue!! and i was up till 2 in the morning doing this haha (my agents would be stuck in the startup mode and then eventualy going to the protocol failure when upgraded to view agent 5.2.0. I do not see anywhere in the 5.2 documentation saying that this appblast feature needs to be installed when customizing the install. The only thing that needs to be there according to the documentation is the the "core". i added appblast to my configuration and now all of them come up as available. Also i do not see an updated list in the 5.2 documentation describing all of the features that you can use when using the ADDLOCAL command line switch. I can only find them in the view 5.0 administration guide and appblast is not even mentioned anywhere that i could see.

[mpryor]

You didn't miss something, the Appblast component isn't a fully fledged component in the agent installer and shouldn't be split out - it's a bug that we intend to fix in a future release. The real functionality that this links to is part of the feature pack installer, labeled as HTML Access Agent.

[ChrisBCarlson]

Cool, well maybe someone can get around to updating the documentation ?

Thanks

[mpryor]

It's unlikely the documentation will be updated, it's not generally changed for update releases - instead the installer will be fixed to not require the component and the original problem will/may be release noted.

[iamxCPx]

Nevermind.

I think my firewall was disabled because of the Persona Management script.

VMware needs to update that script if Blast is involved.

Thanks to:

Core four: VMware View fails with Protocol Failure after running optimization script

Message was edited by: CP Nevermind. I think my firewall was disabled because of the Persona Management script. VMware needs to update that script if Blast is involved. Thanks to: Core four: VMware View fails with Protocol Failure after running optimization script

[mpryor]

You simply add Appblast to the end of your existing ADDLOCAL parameter for the silent install. If you're not using ADDLOCAL then you're not experiencing the same issue.