none
HP Universal Printer Driver conflicts with other HP drivers? - Printer not ready

    Question

  • 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. 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.


    • Edited by Roel_85 Wednesday, January 23, 2013 2:28 PM
    Wednesday, January 23, 2013 2:28 PM

Answers

  • Hi Roel,

    removing driver package will not fix the problem since driver files are already copied to  c:\windows\system32\spool\drivers\x64.

    some dll's at  c:\windows\system32\spool\drivers\x64 can be used by different drivers simultaneously.

    I suspect that during UDP 5.6 installation some dll was replaced by the newer versions and this is why older driver fails.

    Check Event Viewer's 'PrintService' logs, it may point you to the conflicting files.


    Friday, January 25, 2013 5:44 AM

All replies

  • 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.

    Wednesday, January 23, 2013 5:28 PM
  • 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: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

    Thursday, January 24, 2013 3:18 AM
  • We did install it as "traditional mode".  We normally did it when we added the first printer and pointed to the driver instead of using the exe that came with the driver.  However, either way works in setting it to traditional mode.  After the printer is installed, we go to the Device Settings Tab and run the "Automatic Configuration" which asks the printer what features it has and sets them.
    Thursday, January 24, 2013 5:08 PM
  • You maybe yes, I quoted you because I just wanted to add that to your tip for Roel_85 :)

    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

    Friday, January 25, 2013 2:36 AM
  • Hi Roel,

    removing driver package will not fix the problem since driver files are already copied to  c:\windows\system32\spool\drivers\x64.

    some dll's at  c:\windows\system32\spool\drivers\x64 can be used by different drivers simultaneously.

    I suspect that during UDP 5.6 installation some dll was replaced by the newer versions and this is why older driver fails.

    Check Event Viewer's 'PrintService' logs, it may point you to the conflicting files.


    Friday, January 25, 2013 5:44 AM
  • Okay, but will removing that referenced file affect an older driver (PCL 6 v5.3 and v5.4)?  Should I just upgrade all queues with UPD PCL 6 versions to the latest v.5.6.0?  As it stands I may not have a choice, but want to be sure that upgrading to v5.6 will resolve the crisis.  Comments welcomed.
    Friday, February 15, 2013 2:42 AM
  • yes, I guess that update of the older versions to 5.6 will help.
    Friday, February 15, 2013 5:18 AM