Problem
You have a VMware Horizon View Connection Server 7.5.0 that was recently upgraded from 7.4.0 and you noticed that the VMware Horizon View Connection Server service does not start. Attempting to start the service shows that it starts but then stops a few seconds later:
Navigating to the VMware Horizon View Connection server logs directory at:
C:ProgramDataVMwareVDMlogs
… and reviewing the wsnm_starts.txt file:
… show that the service starts and stops:
Reviewing the most recent log file log-2018-06-25.txt:
… shows a series of errors:
Navigating to the bottom of the log file reveals the following errors as the service stops:
2018-06-25T10:42:47.052-03:00 INFO (0714-1280) <logloaded> [MessageFrameWork] Plugin ‘ws_winauth – VMware Horizon View Framework Windows Authentication Support’ loaded, version=7.5.0 build-8583568, buildtype=release
2018-06-25T10:42:47.052-03:00 INFO (0714-0E90) <Service Main Thread> [wsnm] The VMware View System Service is starting
2018-06-25T10:42:47.068-03:00 INFO (0A94-12E8) <logloaded> [MessageFrameWork] Plugin ‘ws_java_bridgeDLL – VMware Horizon View Framework Java Bridge’ loaded, version=7.5.0 build-8583568, buildtype=release
2018-06-25T10:42:47.068-03:00 INFO (0A94-123C) <Main Thread> [MessageFrameWork] Program ‘ws_MessageBusService – VMware Horizon View Java Component Service’ started, version=7.5.0 build-8583568, pid=0xA94, buildtype=release, usethread=1, closeafterwrite=0, sessionId=0
2018-06-25T10:42:47.068-03:00 INFO (0A94-12D4) <Service Main Thread> [ws_MessageBusService] The service ‘MessageBusService’ is started
2018-06-25T10:42:47.068-03:00 INFO (0A94-13E4) <logloaded> [MessageFrameWork] Plugin ‘ws_javaview – VMware Horizon View Framework Java Diagnostics’ loaded, version=7.5.0 build-8583568, buildtype=release
2018-06-25T10:42:47.070-03:00 INFO (0A94-0CE4) <logloaded> [MessageFrameWork] Plugin ‘mfw_java – VMware Horizon View Framework Java Native Support (64-bit)’ loaded, version=15.0.0 build-8440871, buildtype=release
2018-06-25T10:42:47.211-03:00 ERROR (0A94-112C) <javabridge> [mfw_java] Java Bridge Managed failed on tmp =jniEnv->FindClass(“com/vmware/vdi/mfwj/binaryResp”)
2018-06-25T10:42:47.211-03:00 ERROR (0A94-112C) <javabridge> [mfw_java] Exception in BagConv::Init
2018-06-25T10:42:47.211-03:00 WARN (0A94-112C) <javabridge> [ws_java_bridgeDLL] Exception
2018-06-25T10:42:47.211-03:00 WARN (0A94-112C) <javabridge> [ws_java_bridgeDLL] in thread “main”
2018-06-25T10:42:47.211-03:00 ERROR (0A64-09F4) <Service Main Thread> [ws_ConnectionServer] Wait for READY state FAILED for dependent ‘wsmsgbus’, error: The specified service is stopping
2018-06-25T10:42:47.243-03:00 INFO (0A94-123C) <Main Thread> [ws_MessageBusService] The service ‘MessageBusService’ is stopped
2018-06-25T10:42:47.726-03:00 ERROR (0A64-09F4) <Service Main Thread> [ws_ConnectionServer] wsnm OpenProcess FAILED, error: 87 (The parameter is incorrect.)
2018-06-25T10:42:47.726-03:00 ERROR (0A64-09F4) <Service Main Thread> [ws_ConnectionServer] wsnm OpenProcess FAILED, error: 87 (The parameter is incorrect.)
2018-06-25T10:42:47.726-03:00 INFO (0714-0E90) <Service Main Thread> [wsnm] The VMware View System Service is shutting down
2018-06-25T10:42:47.726-03:00 WARN (0A64-0D40) <NodeManagerWatcher> [MessageFrameWork] Connection to Node Manager lost
2018-06-25T10:42:47.898-03:00 INFO (0714-04B4) <Main Thread> [wsnm] The VMware View System Service has stopped
2018-06-25T10:42:47.960-03:00 INFO (0A64-0440) <Main Thread> [ws_ConnectionServer] The service ‘Broker’ is stopped
2018-06-25T10:43:21.813-03:00 WARN (07D4-0C84) <3204> [v4v_broker_agent_svc] SocketChannel: Unable to connect to contoVV02:32111
Solution
There wasn’t much information available only aside from this old KB listed for version 6.2.x and older:
View Administrator portal fails to launch after upgrading from VMware Horizon View 5.2 to 5.3 (2075114)
https://kb.vmware.com/s/article/2075114
The environment for this example did not have vRealize Operations Manager but I went ahead and uninstalled the VMware Horizon 7 Connection Server component:
Ensured that I left the AD LDS Instance VMwareVDMDS intact:
Then reinstalled VMware Horizon 7 as a replica server using the same AD LDS instance, which corrected the problem.
