Usblist2.exe Printer Not Ready
Posted on
In our organization we have 4 different HP printermodels: Laserjet 3055 Laserjet M525 MFP Color Laserjet M575 MFP Color Laserjet M775 MFP Last friday i added the latest HP Universal Printer Driver (upd-pcl6-x64-5.6.0.14430) to our printserver, for the HP laserjet 3055. From that moment on, users went complaining that they can't print anymore. The symptoms are as following: When the user wants to print, they get the message 'printer not ready'. This occurs random. The user can't print from any application, to any printer, at that moment.
Only a particular user has the problem, no complete department for example. Restarting the print spooler alone doesn't fix the issue/ I have a temporary fix for this: Remove the printers from the users account Empty the folder c: windows system32 spool printers Emty the folder c: windows system32 spool drivers x64. After a reboot the printers are readded by the loginscript, and the user can print again.
This is a temporary fix, but after a while the problem comes back to the same user(s). I deleted the UPD package from the print server already, but the problem continues.
So far, only users printing to a HP M525 MFP reported the problem. Users printing to the other devices are not affected. Facts: Clients: Windows 7 SP1 Enterprise x64 Printserver: Windows Server 2008 x64 Drivers: each model uses it's own propriatery driver, latest version downloaded on HP Support. For the Laserjet 3055, only the UPD driver is available for download.
Usblist2.exe Printer Not Ready Outlook 2016
I have also problems with the UPD driver for this model, but that's another story. Anyone have suggestions how to complete fix this issue?
Thanks in advance. We are removing all model specific HP drivers and just going with the HPUD (5.6 right now). We have found that as we move forward HP is not making model specific drivers and forcing the use of HPUD. Might try removing each queue one at a time and rebuilding them from scratch using the HPUD. After you have done that to all the queues remove the model specific drivers from the server.
(May want to reboot afterwards but it can wait until a 'slow' or maintenance window time.) Instead of using a logon script to depoy the printers we would suggest using GPOs since you have Win 7. This option may give you more flexibility later one with troubleshooting and migration(s). As for the 'printer not ready', try going to properties, ports tab, remove check in Enable bidirectional support.
Wait a little bit to see if it goes to ready. Sometimes this works, other times it does not. Send a test page to print from the server and then from a workstation. Next attempt to print from an application. We are removing all model specific HP drivers and just going with the HPUD (5.6 right now). We have found that as we move forward HP is not making model specific drivers and forcing the use of HPUD. Might try removing each queue one at a time and rebuilding them from scratch using the HPUD.
After you have done that to all the queues remove the model specific drivers from the server. (May want to reboot afterwards but it can wait until a 'slow' or maintenance window time.) Instead of using a logon script to depoy the printers we would suggest using GPOs since you have Win 7. This option may give you more flexibility later one with troubleshooting and migration(s). As for the 'printer not ready', try going to properties, ports tab, remove check in Enable bidirectional support. Wait a little bit to see if it goes to ready.
Sometimes this works, other times it does not. Send a test page to print from the server and then from a workstation. Next attempt to print from an application. Only thing I would add is did you installed it with the setup? I suggest to do so if not. And most of all, select 'tradional's mode', the dynamic's mode is a nightmare on print server.
(If already in dynamic, remove the UPD, and re-install with the setup again). Installing via the.inf work, but seem to leave bad artifact (I never achieved good result that way) MCP MCTS 70-236: Exchange Server 2007, Configuring Twitter - @yagmoth555 Blog:.