Skip to main content

Horizon Agent 7.6 installation fails with "Error 1920. Service VMware Blast (VMBlast) failed to start."

  Symptoms

When installing(fresh or upgrade installation) Horizon Agent 7.6, the installation may fail and show the following error dialog. 
"Error 1920. Service VMware Blast (VMBlast) failed to start."

The installation then rolls back.
Cause
The log4cxx.dll bundled in Horizon Agent 7.6 does not have Product Version information. The log4cxx.dll bundled with older versions of Horizon Agent contains version information.  This issue will happen when the Horizon Agent 7.6 is unable to delete the log4cxx.dll belonging to earlier versions.
As a result, the Blast Service (which depends on log4cxx.dll) will fail to start and the Horizon Agent 7.6 installation will not succeed.
Resolution
This issue has been resolved in Horizon Agent 7.7.
Workaround
If you need to install Horizon Agent 7.6 instead of using a later Horizon version, then delete the C:\Program Files\VMware\VMware Blast\log4cxx.dll (or the entire VMware Blast directory) manually before installing Horizon Agent 7.6.

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...
Post a Comment
Read more

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms While accessing the performance tab and navigating to Overview, you see: No data available   The data for Real time, but fails to retrieve it for past 1 day, week, month or year.  While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see  "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter...
Post a Comment
Read more