Director does not display session info

[KraBecs]

After updating from 1912 LTSR CU1 VDA to CU2 (or even 3 or 4), the Director no longer displays session information.

Neither in the WebVersion nor directly on the server. All other components are already on CU4.
The programs can be started quite normally with test users.
However, the sessions cannot be logged out, so it is not possible to work with the vDisk.

[Pavan nannapaneni1709152483]

Try  Test-MonitorDBConnection also check Citrix monitor service is started as this service is responsible for providing Director information.

[KraBecs]

What is the best way to do this?
Do you have any instructions?

[Pavan nannapaneni1709152483]

on controllers, open powershell and try Test-Monitor DBConnection. Open Services and check monitor service is up and running, if it is restart and try again.

[KraBecs]

the monitor service has started
From users working on a CU1 version, I also see the session info without selection of the server (see next photo)

 

Not from users in a new environment (test) (CU3).

[KraBecs]

the monitor service has started
From users working on a CU1 version, I also see the session info without selection of the server.

 

Not from users in a new environment (test) (CU2).

Just tested with CU5 -  same result

[KraBecs]

I have tested again and now installed the CU5 Provisioning Target Device & CU 5 Virtual Apps and Desktops.

 

I still have the problem that the sessions are not displayed/connected correctly.
This is the session:

when I click on my name, I get the following image:

“User is actually not connected”
Which service is responsible for transferring the info from the server to the director?!

Somewhere here must be the error.

in the director it looks like this

Looks like a Ghost Session.
From all other Users, which works on the “normal” & old CU 1 Version I can get infos, in the same director.

[Valerie Agneessens]

Hello,
I have the same problem after updating from 7 1912 LTSR CU7 VDA to 7 2203 LTSR CU4.
On VDAs in production, it works very well.
Did a VDA cleanup then reinstalled, the problem is still there.
Did anyone have a solution?

Thanks.

Valérie