RDS connection crashes when printing with EasyPrint on Server 2019

Question

Hi everyone,

on our server 2019 we use RDS remote apps with printer redirection and EasyPrint. In a certain application there are certain program modules that cause the RDP connection to crash when printing. All other applications work fine. I've tried various solutions, but haven't been able to solve the problem.

• all updates installed
• Reinstalled EasyPrint

Yes, I also contacted the software manufacturer. They think it's a Microsoft problem.

The only working solution seems to be to forgo EasyPrint. But I wouldn't like to do that, especially since we also have other problems with our printer manufacturer's driver that EasyPrint circumvents. Unfortunately, in the spooler log I only see that the print job was successfully processed and sent to the client. After that the connection is dropped while the session is still active on the server. I'm even able to reconnect. Interestingly the redirected printers are not available anymore in said application after reconnecting but in Windows they are there. The behavior is the same with Win10 and Win11 clients. Maybe someone has an idea?
Thanks.

Answer 1

Hello AMKIT,

Are there any patterns or differences in the size of print jobs generated by the problematic modules in the third-party software compared to other applications that are working fine? Large or complex print jobs can sometimes lead to printing issues in remote desktop environments.

Regards,

Karlie

Answer 2

Hello Karlie,

thanks for your reply. From what I can tell, it's a pretty average print job. It even happens with an empty page. I printed the same page as XPS locally on the server which was only 104kB.

On the client i can see this error:

Name der fehlerhaften Anwendung: mstsc.exe, Version: 10.0.19041.3636, Zeitstempel: 0xf90305bf

Name des fehlerhaften Moduls: KMUU84H5.DLL, Version: 8.4.17.5, Zeitstempel: 0x645478b6

Ausnahmecode: 0xc0000005

Fehleroffset: 0x000000000012e1f3

ID des fehlerhaften Prozesses: 0x5e0

Startzeit der fehlerhaften Anwendung: 0x01da21cbdb716e60

Pfad der fehlerhaften Anwendung: C:\Windows\system32\mstsc.exe

Pfad des fehlerhaften Moduls: C:\Windows\system32\spool\DRIVERS\x64\3\KMUU84H5.DLL

Berichtskennung: f71313d1-acc3-4aae-ae6e-c70ff67361f1

Vollständiger Name des fehlerhaften Pakets: 

Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

This looks like the local printer driver has a problem with this specific EasyPrint print job.

Unfortunately there is nothing else in the client logs.

Edit: The only information i could squeeze out of our software provider was that this part of the software was programmed using a VSC++ framework. Other applications and modules are using integrated web browsers or CrystalReports etc..

Kind Regards

Johannes

Answer 3

Hello Johannes,

Based on the error message, when you reinstalled EasyPrint, did you ensure that you used the latest version compatible with Server 2019?

And have you tested printing from the same application modules locally on the Server 2019 (not through RDP) to see if the issue persists or if it's specific to the RDP sessions?

Kind Regards

Karlie

Answer 4

Hello Karlie,
I used the EasyPrint driver included in Server 2019. Driver version is 10.0.17763.973. If you have a download link for a newer version, I'd love to try it.

Printing locally works fine (without EasyPrint) on the server from the same application modules.

After some more testing I found that changing the local driver on the client (to an actually incompatible one) also changes the behavior. The RDP-connection does not crash anymore. But I'm only able to print once. After that in the application all redirected printers are gone. Only the local printers of the server are still available (PDF- & XPS-printers). Even though the redirected printers still appear in the system. In this case there is no error logged on the client or server.

I also tested with Server 2022. It's the same problem there with EasyPrint Version 10.0.20348.1.

Kind Regards
Johannes

Answer 5

Hello Johannes,

Thank you for the extra details. I've exhausted my current ideas and am unsure of any other possibilities. I find the complexity of the issue involving third-party software. To delve deeper into the problem, I suggest using Process Monitor (ProcMon). It can capture real-time system activity and may offer more insights into the RDS connection crash during printing.

Kind regards,

Karlie