We are experiencing the odd intermittent issue with users being unable to connect to their existing disconnected sessions in Horizon.
Rather than connecting to their existing session, a new session gets launched (Instant clones). As we are using FSLogix profiles, this means that they get a temporary profile as their VHDX is still mounted to the old disconnected session.
The only thing I've found in the Windows Logs that could be related is:
AGENT PENDING EXPIRED
The pending session on machine <HOSTNAME> for user <DOMAIN\username> has expired
In the VDM logs I can see:
BLAST: Failed to prepare session for sessionID=1;
Failed to obtain connection object for BLAST
Released session lock sesssionId=1
REquested protocol for session is not available, user <DOMIAIN\username>
session::pendingSessionDuplicateCount(): final duplicate count = 0
SessionCounts: total=3, pen=0, con=1, dis=1, por=1, lgf=0
Publish SESSION PENDING_EXPIRED
No need to stop protocol, already cleared
DesktopManager got a SendEvent message
Message is PENDING_EXPIRED
Any ideas would be welcome.
Environment: Horizon 2212 (currently still running 7.13 Agent version on the gold image)
Did you ever figure this out?
We are having almost exact same issue, with temp profiles getting created, or user just able to log back in until someone sign outs the disconnected session. We are using Horizon 8, with server 2022 used as the Host servers.
Similar issue discussed on a Microsoft Hub session. It's an Azure environment, but apparently the FXLogix is a common thread - until an update (no details on that). Thread is a little dated, but might point you in a good direction.