We recently updated to Horizon 8. Since then, we are seeing multiple console errors...
Connection server console message shows "DETECTED UNRECOGNIZED REQUESTS"
UAG shows "BROKER DETECTED UNRECOGNIZED SESSIONS"
Has anyone seen these and or come up with a resolution? I cannot find any mention on the net or in kbs.
Edit 07-10-23 We are using F5 load balancer.
Worth noting we just upgraded to 2306 and experience the same issues. We have load balancers in front of our external UAG's but not the internal ones and I see the errors on both sides.
Just thought I'd chime in as another 2306 user since https://kb.vmware.com/s/article/90398 says It was fixed still in 2303 up which clearly isn't the case.
Adding my 2 cents as well. We recently upgraded to 2306 and seeing the error as well, but only concerning internal Connection Servers, my UAG's are showing all green.
I sent my "LB Guy" the relevant VMware KB's, but he can't find anything wrong.
Looking at the debug logs, we see the following lines, but searches haven't turned up anything of value (except this thread).
Nothing immediately immediately before or following this entry provides any relevant information either.
<MessageFrameWorkDispatch> [MessageFrameWork] KeyVaultWorker::MessageHandler(): KeyVault service got operation=decipherWithDerivedKey, ok=1, msecs=16
<ajp-nio-127.0.0.1-8009-exec-1> [ConnectionServerHandler] Incrementing the warning count : Reason : unrecognized request detected
We upgraded our Horizon to last ESB version 2212.1 and got same alerts. We use Citrix ADC for UAGs and CS. LB have correct settings which we compared with VMware recomendation. Would to disable this messages on Horizon's Dashboard.
I've been working an SR with VMWare on this issue and their response/solutions is:
Upgrade to version 8.10(2306)
Apply a Hot Patch they made available to me via FTP download: VMware-Horizon-Connection-Server-x86_64-8.10.0-22364614.exe
I have not upgraded and tested yet, but will update this post once I confirm this works or not.
Yes very interested in how that goes. They had offered a hot patch but we decided to forgo messing with our production system right now since this is more cosmetic than anything.
I'd be curious with 2306.1 out now if that addresses it or if we'll need yet another patch. (2306.2?? 😀 )
Incidentally, we've removed our load balancers and are just using an HA UAG config and the problem persists so it isn't load balancers causing our problem.
We have exact same issues. we just upgraded to 2306 and experience the same issues. We have load balancers in front of our external UAG's to 2 connection server and also 2 connection server internal side with load balancers.
we see the errors on external sides both UAG's and Connection Servers
We applied the hot patch that was provided to us and added a new entry in the ADAM database to disable the alerts.
This has resolved the issue with the "Unrecognized Requests" warnings for our CS but unfortunately, we are awaiting a resolution for the UAG alerts.
Personally I stick to the plan of ignoring it. The environment works, therefore i feel like there's nothing to be done on my end.
For the record:
I have set up the environment (2 UAG, 2 CS) in 2306 in the first place, so nothing that is 'fixed' by updating to that version. And since those message appear and disappear all by themselves ... ¯\_(ツ)_/¯
Just upgraded from 7.13 to 2212.1 and seeing the same message.
F5 in front of connection servers.
Environment seems to be working fine.
We have 3 pods. First Pod is for testing and digital signage and I don't have those messages. Second Pod is for production use and is seeing the messages. I have not updated the third Pod yet as it is the other production pod.
I adjusted the setting under Servers > Global Settings > General Settings > Discard SSO Credentials, and set it to "After" "1 minute".
So far I have not encountered this alert anymore.
I have tried disconnecting and reconnecting as quickly as possible.
I have tried logging off an Instant Clone, and relaunching to get a new session.
I am on Horizon 2212.1 (8.8.1 build - 22192183) and UAG 184.108.40.206-21063638
Fingers crossed this will stop these useless events.