Answered by:
Win32 error code returned by the print processor: 122. The data area passed to a system call is too small.

Question
-
Anyone got any ideas when a user prints through windows 2012 R2 RDS server using printer redirection getting the following message
The document Print Document, owned by pete, failed to print on printer Michelle (redirected 2). Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 110709. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\SERVER. Win32 error code returned by the print processor: 122. The data area passed to a system call is too small.I've deleted the user profile on the RDS server, updated the print driver on the local machine to the latest driver, and installed the latest driver to the server and set that as their default printer and still getting the issue. Other users are working fine so a bit stumped on this one and would appreciate a fresh outlook on it.
Thanks
Thursday, August 25, 2016 7:41 AM
Answers
-
Are other users printing to the redirected printer Michelle?
Have you added a fake printer that uses the same driver as Michelle on another client included redirection and is printing successful?
Are all the clients the same OS and using the same RDP client version?
I associate error 122 with lower end device models. What print process is used by the device? This information is on the Advanced tab of printer properties.
Alan Morris formerly with Windows Printing Team
- Proposed as answer by Wendy Jiang Monday, August 29, 2016 7:11 AM
- Marked as answer by Wendy Jiang Friday, September 2, 2016 9:05 AM
Thursday, August 25, 2016 1:05 PMAnswerer -
Hi,
It seems that this error could be caused by variety of reasons.
According to my search on the internet, I quote some ways which help others to fix the similar error, you could have a try to see if they work:
1. Make sure that user account has the full access on Windows\System32\spool\PRINTERS folder.
2. Have a try to print a few pages see if it breaks.
3. The driver is updated into the newest one for the printer
4. The server and client are patched fully with the latest updates.
5. Install the same correct driver on the client and server.
The following thread has many discussion there about the similar error, you could refer to it for more reference:
Windows 2012 R2 - Intermittent RDP Printing
https://social.technet.microsoft.com/Forums/windows/en-US/df6ab00d-e463-4ad1-b3fc-06e7e13ec21c/windows-2012-r2-intermittent-rdp-printing?forum=winserverTS
Best regards,
WendyPlease remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
- Proposed as answer by Wendy Jiang Monday, August 29, 2016 7:11 AM
- Marked as answer by Wendy Jiang Friday, September 2, 2016 9:05 AM
Friday, August 26, 2016 8:45 AM
All replies
-
Are other users printing to the redirected printer Michelle?
Have you added a fake printer that uses the same driver as Michelle on another client included redirection and is printing successful?
Are all the clients the same OS and using the same RDP client version?
I associate error 122 with lower end device models. What print process is used by the device? This information is on the Advanced tab of printer properties.
Alan Morris formerly with Windows Printing Team
- Proposed as answer by Wendy Jiang Monday, August 29, 2016 7:11 AM
- Marked as answer by Wendy Jiang Friday, September 2, 2016 9:05 AM
Thursday, August 25, 2016 1:05 PMAnswerer -
Have the same issue with 2 different customers. I have installed the printer on the RDS server as well as on the client.
Print processor is winprint Raw and all clients are running windows 7 pro. Printer is a ricoh MP C3003
Thursday, August 25, 2016 1:48 PM -
Hi,
It seems that this error could be caused by variety of reasons.
According to my search on the internet, I quote some ways which help others to fix the similar error, you could have a try to see if they work:
1. Make sure that user account has the full access on Windows\System32\spool\PRINTERS folder.
2. Have a try to print a few pages see if it breaks.
3. The driver is updated into the newest one for the printer
4. The server and client are patched fully with the latest updates.
5. Install the same correct driver on the client and server.
The following thread has many discussion there about the similar error, you could refer to it for more reference:
Windows 2012 R2 - Intermittent RDP Printing
https://social.technet.microsoft.com/Forums/windows/en-US/df6ab00d-e463-4ad1-b3fc-06e7e13ec21c/windows-2012-r2-intermittent-rdp-printing?forum=winserverTS
Best regards,
WendyPlease remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
- Proposed as answer by Wendy Jiang Monday, August 29, 2016 7:11 AM
- Marked as answer by Wendy Jiang Friday, September 2, 2016 9:05 AM
Friday, August 26, 2016 8:45 AM -
Hi,
I am checking how the issue going, if you still have any questions, please feel free to contact us.
Appreciate for your feedback.
Best regards,
Wendy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Monday, August 29, 2016 7:11 AM -
Updated all microsoft patches on the server have 4 users using redirected printing and 2 who can only use the printer installed on the server so all now working, so not going to try and change the 2 back to redirected printing :)
- Proposed as answer by Wendy Jiang Monday, September 5, 2016 1:23 AM
Friday, September 2, 2016 10:06 AM -
Hi,
I am glad that all is working, and appreciate for your update and share, it will be greatly helpful to others who have the same problem.
Thank you for your time again.
Best Regards,
WendyPlease remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Monday, September 5, 2016 1:23 AM -
I ended up running Windows setup to upgrade the build and it's fixed the issue for meThursday, November 1, 2018 7:38 AM