Jan-Peer Gebauer
-
Posts
3 -
Joined
-
Last visited
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Jan-Peer Gebauer
-
-
4 hours ago, lterpst151 said:
Do you have a case ID or the link to the file? We would love to try this also.
Currently you can get the file only from the Trend Micro support. There is no download on official Trend Micro web pages.
TM Case: 05300965 -
Hi.
We are running VDA 2109 on Server 2019 with TM ApexOne 14.0.9645 and got the same login problems with gray screens when starting a published desktop.
We contacted the Trend Micro support. They send us a new version of the file "tmlocfg.ptn".
On a VDA (or VDA master image) I had to stop ApexOne, replace tmlocfg.ptn in the locations:
C:\Program Files (x86)\Trend Micro\Security Agent
C:\Program Files (x86)\Trend Micro\BM\Patterns
C:\Program Files (x86)\Trend Micro\BM\updateRestart the VDA.
After these steps it seems to be solved. No more gray screens in the last 2 days.
What is your experience with the ApexOne patch? Did you get the same solution?
JP
Windows 8.1: HDX Engine crashes trying to call GetDpiForWindow function
in Receiver for Windows 4.x
Posted
Hi.
We have the same problem with Windows 8.1.
Teams HDX optimization shows "Citrix HDX not connected"
Uninstalling Workspace App 2204 and installing 2109.1 fixed the problem on Windows 8.1.
It seems that WSA 2202 is also affected on Win8.1
Client event log error:
Name der fehlerhaften Anwendung: HdxRtcEngine.exe, Version: 15.33.0.10, Zeitstempel: 0x62166d7c
Name des fehlerhaften Moduls: 6)\Citrix\ICA Client\webrpc.dll!GetDpiForWindow, Version: 6.3.9600.20302, Zeitstempel: 0x62165b52
Ausnahmecode: 0xc0000139
Fehleroffset: 0x0009d322
ID des fehlerhaften Prozesses: 0x2b24
Startzeit der fehlerhaften Anwendung: 0x01d84ff0c1bf0d48
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Citrix\ICA Client\HdxRtcEngine.exe
Pfad des fehlerhaften Moduls: 6)\Citrix\ICA Client\webrpc.dll
Berichtskennung: 28fcab28-bbe4-11ec-8353-600292314952
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: