Win32 Error Code Returned By The Print Processor 122

[Courtland Boland]

Ihave a few printers set up on a print server. When some of my users try to print, the first print job seems to go through fine. After that, trying to send another print job to a printer completely locks up the application they are printing from, and the print job is never completed.

I've tried restarting the print spooler, cleaning out the spool files under system32\spool\printers, removing and adding the printer again, nothing seems to allow the user to print, until they do a hard reboot. Then we repeat the process again, first print works, nothing after that.

The print job 22 was sent through the print processor hpcpp140 on printer Office Printer, driver HP LaserJet Pro MFP M521 PCL 6, in the isolation mode 1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x103.

The print job 21 was sent through the print processor hpcpp140 on printer Office Printer, driver HP LaserJet Pro MFP M521 PCL 6, in the isolation mode 1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x0.

I believe the issue was I didn't remove the printer and the drivers from the clients before removing the device off the server. I removed the deployed printer from the GPO through Print Management, completely removed the device from the server, cleaned the drivers, then set the printer back up from scratch using the HP Universal PCL 6 driver. Re-deployed the printer through GPO, everything seems to be working now.

Restarted the printer and the job pushes thru. After a couple of minutes, another print job gets stuck in the queue for the same machine. Same status, same situation. Restarted the machine again and it prints. Odd thing, the server is able to see the printer as ping requests are received and replied to.

I think you need to check the drivers of the clients that have the printer installed. Check if they have SNMP enabled. If yes i would guess that, that is your problem. If not maybe you need to reconsider about the drivers that you have installed.

SNMP was the first thing I checked when it went offline. Went and disabled it from the server side printer properties. Then I reconnected my laptop to that printer share and tried printing. Job just got stuck in the queue and not pushed to the printer.

I was able to print after a complete printer restart, printer reinstall and server restart. After that, in a couple of minutes after the successful prints, succeeding jobs just gets stuck in the queue again.

Data type: NT EMF 1.008. Size of the spool file in bytes: 158216. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \PRINT_SERVER. Win32 error code returned by the print processor: 2250. This network connection does not exist.

I don't know what to suggest next, other than to try (if you haven't already) installing one of the other available printer drivers - I'm assuming (but don't know for sure) that you're probably using the v4 driver version.

- The print spooler failed to regenerate the printer driver information for driver Microsoft XPS Document Writer for environment Windows x64. Win32 system error code 1797 (0x705). This can occur after an operating system upgrade or because of data loss on the hard drive.

In my attempt to install one of the other printer drivers, the existing HP software was removed and for some reason, a new full installation fails every time now. I don't get any error messages during the new installation, but afterwards I find that there isn't any HP-program (like HP Scan etc.) installed. The printer is displayed among the devices though and the driver seems installed as well. And printing still does'nt work, of course.

I must say I start considering to reinstall Windows after all. But first I will try to use someone else's laptop and see what happens then when installing or communicating with our printer. I'll keep you informed, and thanks a lot for all your efforts and thinking so far, it's very much appreciated!

When looking for possible solutions for the installation problems I had faced after removing the HP software, I found the following advice on -Software-and-Drivers/M477-software-installation-fails-at-99/td...:

I selected the driver (the one with the dash, not the who was in use and without the dash) manually in the printer properties, and that did the job! The printer works properly once again and all the HP programs are completely installed now.

It all seems to have been a driver issue and it's quite disappointing that the HP technician wasn't able to help me out of this and left me to my own devices saying it was a network or system problem. I didn't change anything in the printer settings in the first place so I shoudn't have been bothering with this issue for weeks. Thank God there is Google and this HP forum with volunteers like you gladly helping people out. So thanks again for all your help and advice!

Does it queue up the print job on the printer you sent it to? Is the print spooler running on the print server(it must be if you can add printers)? Is there anything in the spools folder on the server. C:\Windows\System32\spool\PRINTERS if there is stop the print spooler delete the contents and restart the spooler.

I just ran into something similar to this when I was updating SNMP on my devices and Spiceworks. I changed the SNMP names from the default of public to something else. On my printer tcp/ip ports SNMP was enabled but the community name did not match. Thus from the client it all looked fine, but it never actually made it to the server from what I could see. Once I updated the community name on the port settings everything started to print fine. Any chance something similar is going on?

The document Print Document, owned by ismails, failed to print on printer HP LaserJet Pro CM1415 MFP PCL6 Class Driver. Try to print the document again, or restart the print spooler.

Data type: RAW. Size of the spool file in bytes: 925. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: ISMAIL-PC. Win32 error code returned by the print processor: 5. Access is denied.

The document Print Document, owned by Administrator, failed to print on printer HP LaserJet Pro CM1415. Try to print the document again, or restart the print spooler.

Data type: RAW. Size of the spool file in bytes: 193954. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \AFSOLSRV. Win32 error code returned by the print processor: 5. Access is denied.

The document Test Page, owned by USERNAME, failed to print on printer PRINTER. Try to print the document again, or restart the print spooler.

Data type: RAW. Size of the spool file in bytes: 145189. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\SERVERNAME. Win32 error code returned by the print processor: 5. Access is denied.

I am looking for assistance with the following problem when trying to print to a client redirected printer (on another subnet), when connected to RDS (Windows Server 2012 R2).

We have found that the first time you print to a redirected printer on the RDS box, it will print correctly at the client printer, however after you log off, that's it, you're unable to print to this printer again from within an RDS session on the RDS box, and it logs the following event in the Print and Document Services each time you try.

The document Print Document, owned by , failed to print on printer (redirected 2). Try to print the document again, or restart the print spooler.

Data type: RAW. Size of the spool file in bytes: 42449. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\-RDS. Win32 error code returned by the print processor: 122. The data area passed to a system call is too small.

Dedicated print server with 15 TCPIP printers installed. Each different HP has the correct Class driver installed. Each HP prints from this server no problem. Three of the Ricoh printers use the RICOH Class driver without issue. One model Ricoh I had to download the MP 161 type 3 driver from the web, works flawlessly on the Print server.

Went to the RDS 2012R2 server and in devices and printers i manually added each of the Class drivers for the printers, the list of v4 drivers matched the print server exactly. Then i added the one Ricoh v.3 driver.

On the print server in Print Management each printer was right clicked>Deploy with Group Policy... selected a predefined GPO, set it to Per Machine, that GPO is applied to the OU that the RDS server is in, and loopback replace is enabled.

GPUpdate and rebooted the RDS server, logged into the console and all of the printers were there as expected. The drivers however were a different story. The Ricoh's the use the Class driver, no problem. The Ricohs that needed the v.3 driver were instead using the HP Laserjet A4, a random other HP used that driver as well, and a couple were using the Laserjet ZJS driver. Then after another reboot a couple of the Ricoh's started using the v3 driver, but in Devices and Printers the model is simply "Network Printer Connection"

***the behavior seems to be consistent, for instance I have 3 printers on the server using the HP Laserjet P205X series PCL6 Class Driver, and on the RDS server I manually installed that driver, but all 3 printers are instead using the HP Laserjet A4/Letter PCL 6 Class Driver.

Hey there.. weird one here.. I am testing RemoteApps with Server 2012. All is fine except for when I try and grant access to user in another forest where we have a two-way\forest transitive trust. The error is below.. What is interesting is the trust works fine otherwise. For example, if I try and add a user to the local admin group on the server it works great.. I can even authenticate via RDweb portal from a user in the trusted domain.. any ideas?

3a8082e126