Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,516 questions
Server 2022 RDP printing error
![](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(12.8, 80%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
doriansu
0
Reputation points
All of a sudden I'm seeing an occassional printing error on our server: user is connected via RDP and tries to print on their local printer. Nothing happens and user sees no error. Server event log says this:
The document Print Document, owned by user1, failed to print on printer HP3 (redirected 8). Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 406376. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \SERVER1. Win32 error code returned by the print processor: 122. The data area passed to a system call is too small.
Signing out of the RDP session and signing back in resolves the issue temporarily.
No printer drivers are installed on the server, we are using Easy Print and users print on redirected printers.
I know about TSPrint software but I don't want to use it until I see there is no other solution.
Has anyone experienced this issue and managed to solve it?
{count} votes
-
![](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(3.2, 28.999999999999996%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZ%3C/text%3E%3C/svg%3E)
Zamy 5 Reputation points2024-06-25T19:22:53.8366667+00:00 We have the same issue. Don´t know what I should to do.
-
Zamy 5 Reputation points
2024-07-01T11:31:03.23+00:00 Hi, I only want to inform about the issue.
I ran SFC and it found errors, but was unable to repair them. In the CBS.log there was a problem with LServer_PKConfig.xml (hash mismatch). So I ran DISM with Windows Server image and it finished successfully. Than I ran SFC again and it finished successfully.
Second thing I did I replaced "MXDWDRV.DLL" (in the C:\Windows\System32\spool\drivers\x64\3 location) with older version and restarted the machine. The current library was 0.3.17763.5830. The older one I used is 0.3.17763.4010. After replace I restarted the machine. I don´t know which step resolved the issue but we don´t have a problems for several days.
Sign in to comment
3 answers
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more