Hello,
We have Windows 8.1/Windows 10 users who give print jobs via print queue. From few days, users are reporting that they were unable to give print jobs/test pages from all the print queue's that were sitting on one print server. Restarting the print spooler fixed the issue but the issue came back after few days. I'm trying to find the root cause and permanent fix for this issue as restarting the print spooler service is a temporary work around for this.
Below are my findings:
- Print spooler service has no dependencies.
- From the event logs i see Event ID 372 with the below description: The document Microsoft Outlook - Daily Style, owned by XXXXX, failed to print on printer XXXXX. Try to print the document again, or restart the print spooler. Data type: NT EMF 1.008. Size of the spool file in bytes: 813732. Number of bytes printed: 512624. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: XXXX. Win32 error code returned by the print processor: 122. The data area passed to a system call is too small.
- I was'nt able to replicate the issue from my end as the users were able to print after the spooler service restart.
- i tried to print few pages to see if it breaks.(As suggested https://social.technet.microsoft.com/Forums/ie/en-US/13c5aa49-5fe9-4b5f-95b9-672b22e9d6b9/win32-error-code-returned-by-the-print-processor-122-the-data-area-passed-to-a-system-call-is-too?forum=winserverprint)
- The print server(WS2008 R2) and Client's machines are patched with latest updates.
- We have same set of drivers on other print servers and we haven't came across this kind of issue on them.
- I noticed that print jobs are failing initially on few Print queue's and after some time the failure is on all the print queue's that are sitting on the print server .
Any suggestions would be highly appreciated.
Thanks in advance!!