Symptoms
An error on the Horizon Admin console stating "An internal error eccurred" when clicking on Machines tab.After collecting HAR files you see the following errors:
How to collect a HAR Log file (67589)https://kb.vmware.com/s/article/67589
"text": "{\"message\":\"Failed to find entity\",\"name\":\"com.vmware.vdi.vlsi.binding.vdi.fault.EntityNotFound\"
Purpose
This article discusses the "An internal error occurred" banner message that appears when clicking Horizon Connection Server Admin tabs.
Cause
Machines STUCK in deleting state, while the desktop pool entry under OU=Applications went missing or deleted. This brought an deadlock state, that machines never get deleted from database. Replication failures between Connection Server may cause stale entries when deleting Machines/Desktop pools.
Impact / Risks
The Horizon Admin console will be unable to populate the Machines in Inventory - Machines tab
Resolution
Find Stale desktop pool entry from Browser developer tools. Decode the desktop pool name from it using the response of MachineDetailsView create query sent from browser.
Ex: "text": "{\"message\":\"Failed to find entity:(...) :\"Desktop/xxx/poolname\"}" You can use any tool to decode from Base64 format.
Verify that desktop pool cn with same name does not exist in OU=ApplicationsThen find the machines of stale desktop pool in OU=Servers. Ex: pae-MemberDNOf: CN=DESKTOP-POOL,OU=Server Groups,DC=vdi,DC=vmware,DC=intDelete all the machines belonging to this desktop pool
Issue will get resolved if that was the only one desktop pool remained in stale state
