every day user's complaining about they are unable to launch published applications from start menu suddenly. They always have an open session, which is disconnected suddenly. Reconnect is not working after it. Workspace app launches for a short time and disappears. No errors or warnings in event logs on Storefront, ddcs and vdas. But one on the client:
Workspace App: 2107
Error Event:
1002
Application hang
the program wfica32.exe stopped interacting with windows and was closed
It affects multiple users, which are working in different domains on different Citrix sites.
No webcams or anything else connected by usb to de client device.
We use Virtual apps 2203 now. The issue existed with 2103 before. Update to workspace 2203.1 is not an option because of a bug in it. 2203.2 is not released.
User is not able to reconnect from another computer to his session. In Studio the new connection with the new clientname is displayed.
Computer restart is not helpful.
The only workaround to get the users working again is to log off their session from studio / director.
Question
Björn Schläfli
every day user's complaining about they are unable to launch published applications from start menu suddenly. They always have an open session, which is disconnected suddenly. Reconnect is not working after it. Workspace app launches for a short time and disappears. No errors or warnings in event logs on Storefront, ddcs and vdas. But one on the client:
Workspace App: 2107
Error Event:
1002
Application hang
the program wfica32.exe stopped interacting with windows and was closed
It affects multiple users, which are working in different domains on different Citrix sites.
No webcams or anything else connected by usb to de client device.
We use Virtual apps 2203 now. The issue existed with 2103 before. Update to workspace 2203.1 is not an option because of a bug in it. 2203.2 is not released.
User is not able to reconnect from another computer to his session. In Studio the new connection with the new clientname is displayed.
Computer restart is not helpful.
The only workaround to get the users working again is to log off their session from studio / director.
Anybody have an idea?
Link to comment
3 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now