This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 25%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKV%3C/text%3E%3C/svg%3E)
Hello,
We have been experiencing a new of issues recently in relation to printer re-direction with RDP, looking through the forums I can't see any recent threads so thought I would start a new one...
Has anybody else being experiencing the same issues? Looking at recent updates I cannot see anything glaringly obvious and nothing in event viewer? not sure if redirected print logs will be logged in there.
It seems hit and miss too, for some users it works - some users it doesn't.
Any ideas would be greatly appreciated.
Regards,
Karl
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 53%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBM%3C/text%3E%3C/svg%3E)
I had this issue and fixed it - turned out to be a fault with the Microsoft Easy Print driver. Event logs led me to it:
https://www.papercut.com/kb/Main/LogPrintJobsInEventViewer#the-print-service-operational-log
"The print spooler failed to load a plug-in module C:\WINDOWS\system32\spool\DRIVERS\x64\3\tsprint.dll, error code 0x7E. See the event user data for context information."
Solution was to uninstall and reinstall the Microsoft Easy Print driver using the Print Management console underneath Print Servers. It failed to remove the associated ini file in my case during uninstall, but ignoring that and installing it again made it work - obviously had to log out and back in again to pass through the connections.
https://www.top-password.com/blog/open-print-management-in-windows/
Hopefully this is the same fix for you :-)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 50%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJY%3C/text%3E%3C/svg%3E)
Hi,
I am checking to see how things are going there on this issue.
Please let me know if you would like further assistance.
Hope this helps and please help to accept as Answer if the response is useful.
Thanks,
Jenny
Hello, I thought I had replied?
We published wordpad and had the same issue, but has mentioned - we have noticed the issue happening with drive redirections also.
Since removing KB5003538 from one of the servers so far we haven't had any issues with that specific server so thinking this might be the issue?
Regards,
Karl
Hi Karl,
Thanks for the update. The previous follow up is to ensure that you have checked the registry key value and additonal information shared by other visitors.
Per internal seaching, i did not find any reference that confirmed the KB5003538 was related to any printer issues but will keep monitoring this.
If removeing the specific KB will help to elimiate your problem, you could keep monitoring and then deploy the workaround to other machines.
Best Regards,
Jenny
Hello,
The registry setting was not present on the servers, but I had added it in previously and the issue still happened on and off.
I have removed the update from our other two servers now also, so will monitor how that goes over the next couple of days and come back to you.
Regards,
Karl
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 26%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELB%3C/text%3E%3C/svg%3E)
i found this error on server eventviewe
iWin32 error code returned by the print processor: 122. The data area passed to a system call is too small
its only after disconnecting from terminal server and reconnect again
It seems that removing KB5003538 from our RDP servers has completely resolved our issue - not sure if this update is potentially causing an issue with the software we are running but this has fixed the problem.
We will continue to monitor but I would consider this issue resolved.
Regards,
Karl
Hi Karl,
Thanks for reaching our forum and could you please provide more details for us to better understand your problem?
1.What is the OS version for the target server and users with problem?
2.What is the exact behavior for the Printer Redirections related issue? Like if any error message or screenshot when users encountered the issue?
3.Were the users experienced the issue belong to the same user group in Active Directory?
4.For event logs, it locates: Event log -> Event Viewer\Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-Printers.
5.Kindly advise if any changes have been made before this issue occurred.
Hope this helps and please help to accept as Answer if the response is useful.
Thanks,
Jenny
Hi,
Just checking if any updare regarding the details to better understand your issue.
Looking forward to your reply.
Best Regards,
Jenny
My apologies!
The servers are windows server 2019 and the client machines are windows 10.
The printers are sometimes not showing up within the application we are publishing, there are no error messages.
Yes the users are part of the same group as that is what publishes the app to them
I will look in there for logs but couldn't see any previously.
No changes have been made, apart from a windows cumulative update a few days before we first started noticing the issue.
Regards,
Hi Karl,
Thanks for your update and appreciate your further check on below points.
1.Go and check if anything special has been recorded into the event logs when issue occurred.
2.Kindly check if any other application will experience the missing redirected printer when the specific application has the issue.
If so, then it should be the printer redirection problem.
If not, then probably it is a compatibility issue between the redirected printer and the specific application.
3.kindly advise the update you've patched and let me check internally if any known issue related.
If the Answer is helpful, please click Accept Answer and upvote it. Thanks.
Thanks,
Jenny
Hello,
Thanks,
Karl
I have been looking again today and have both accessed our app via rdwebapps and directly remoted onto the server then opened the app and both ways, the printers are not redirecting.
I cannot see anything recent in event viewer that might be causing it.
Hi Karl,
1.both accessed our app via rdwebapps
Which kind of remote app you've used to access the application? Did you check the device redirection settings in the app?
For the latter one, will you get a .rdp file when login the rdweb page to access the remote application?
If so, please open the .rdp file with notepad and confirm if the printer redirection settings are well configured.
2.In our case, it is worthy to test against the default remote app like WordPad which will also have features of printing. With this test we could narrow down if it is application related issue or RDP printer redirection.
If the Answer is helpful, please click Accept Answer and upvote it.
Thanks,
Jenny
Hello,
Also another thing I have noticed today, is during a session to the RDP servers, if the printers don't re-direct, neither do the local drives. So I think it points more to a session/client issue than specifically a printer issue.
i am assuming that may change things.
It looks like just before the issue started the following updates were installed; KB5003703, KB5003538, KB5003255, KB4601555, KB4577586. Out of those, only KB5003538 seems to be remaining on the servers, so assuming the others have been superseded.
Regards,
Karl