… so I opened the file in Notepad and began reviewing the entries until I found the following: T15:44:23.232-03:00 INFO (0724-0F38) wsnm_jms died, restarting in a minuteĪfter reviewing the agent logs of the virtual desktop, I proceeded to log onto the VMware View Horizon Connection Server to review the server logs located in the folder:
#VMWARE HORIZON CLIENT TIMEOUT ERROR UPDATE#
T15:42:16.553-03:00 WARN (0724-079C) Update rejected, attempt to reconfigure as paired with missing key information Parsing through the logs allowed me to identify the following 3 suspicious entries: … so I opened the file in Notepad and began reviewing the entries: For this example, the latest debug log that had been modified was: What I typically do when in the log folder is to sort the files by Date modified so the most recently modified files are displayed on top. … the first step for troubleshooting issues that have limited information provided in the error details is to review the Horizon View Agent logs on the problematic virtual desktop via the following folder: Desktop’s domain secure connection is not broken.All Horizon View Agent services have been started.
There is connectivity between the View Connection server and VDI.You’ve noticed that desktops in a Desktop pool has the Status reported as being Agent unreachable:Ĭlicking on the ellipsis displays the following details:Īssuming the following obvious items have already been verified: desktop being powered on, an IP address was obtained, etc) so I thought I’d take the opportunity to write this blog post using a recent issue I encountered at one of the environments I work with. I’ve had several colleagues reach out to me in the past to ask about how I normally troubleshoot an Agent unreachable issue when all of the usual checks were verified (e.g.
0 kommentar(er)
