Symptoms
Desktop is unable to be connected with Blast protocol after the Blast Secure Gateway is enabled on a Connection server.
Unable to connect to desktop: There is no available gateway for the display protocol. Try Again, or contact your administrator if this problem persists.
The VMware Horizon View Blast Secure Gateway service is in Paused status.The VMware Horizon View Blast Secure Gateway service fails to manually start with the error message:
Windows could not start the VMware Horizon View Blast Secure Gateway service on Local Computer.
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem persists, contact your system administrator.
Cause
The VMware Horizon View Blast Secure Gateway service can fail to start for several reasons for instance if it cannot read the certificate's private key or has issues reading the path.For more details on the private key, please see Blast gateway not running when a Certificate generated from IIS is used (89820)
Resolution
Increasing Logging for the Blast Secure Gateway Service:
Login to the Connection server where you are encountering issues with the blast service. Make sure the folder "Blast Secure Gateway" exists under C:\ProgramData\VMware\VDM\logs. In a Windows command-prompt window with admin privileges, run these commands:
cd "C:\Program Files\VMware\VMware View\Server\appblastgateway"
nssm set VMBlastSG AppStderr "C:\ProgramData\VMware\VDM\logs\Blast Secure Gateway\absg-stderr.log"
Restart the Blast Secure Gateway Service.Check the absg-stderr.log:
if it contains the below error messages, manually add the C:\Windows\System32 to the PATH environment variable in the Connection server system, then restart the VMware Horizon View Blast Secure Gateway service.
'reg' is not recognized as an internal or external command,
operable program or batch file.
( was unexpected at this time.
Note: to add the directory to the PATH environment variable, please read the How to Add to Windows PATH Environment Variable
if the file shows a different error message, please contact VMware Technical Support for additional support.
Please reset log levels Afterwards.
nssm reset VMBlastSG AppStderr
Restart the Blast Gateway Service for the log level reset to apply immediately.