Server Print Queue Clogging

Hi, I am running Leopard Server in a small office with mixed Windows XP, Vista and Mac 10.6 clients. I am not an IT administrator, but I own the company and have been teaching myself on a DIY basis. These forums are a very helpful source of information for me.
We have a DELL MFP 1600n printer connected to the server via USB. Users can print to the printer. However, very frequently, the print queue will get clogged or jammed and the network printer will go into a paused state. It usually happens when a user tries to print a PDF or .jpg file. I resolve the problem by going manually into the print queue through System Preferences on the server and deleting the PDF or jpg, clicking resume, and then the remaining docs in the queue usually print as normal.
I don't see why I am getting so many frequent clogs/jams in the first place -- the Dell specs show it has 32MB of RAM so shouldn't it be able to handle a moderately large PDF?
Is there a special method for configuring printer services on Leopard Server that will help resolve this problem? Do I need a different printer?
Also, can I assign a user limited privileges that would enable him/her to go in and clear the jammed print queue without giving full access to everything else on the server? Currently, only I can do it and it is a hassle because it needs to be done at least once per day.

Magnify your issue by 145 and that is what I've been dealing with. I'm running a print server with 145 printers and 1800 users, and until recently, I've had to periodically clear the queues and un-pause the printers. Huge PITA.
I still don't know what is causing certain jobs to pause the printers, but here's how I am managing the symptoms to this problem.
Create a launchdaemon to run periodically (mine runs every 120 seconds)
Have it run a script with the following two lines:
cancel -a `lpstat -t | grep disabled | awk '{print $2}'`
cupsenable `lpstat -t | grep disabled | awk '{print $2}'`
The first line cancels all jobs in paused printers.
The second line re-enables any paused printers.
It won't stop certain jobs from hanging the printer, but it will "un-stick" them and eliminate the huge backlog of jobs that pile up as a result of it being paused all day.
FYI...we are running mostly Xerox Phaser 8550 and 8560 printers.
Hope this helps.

Similar Messages

  • How to share 10.6 OSX Server print queue with Windows 7 successfully?

    I used Bonjour Print Services for a Windows 7 machine (http://support.apple.com/kb/dl999) to successfully connect to a Mac OX Server 10.6 print queue, and the following message is generated in the print log and CUPS log,
    "POST/printers/stormoncecar/ HTTP/ 1.1" 200 2205 Print-Job Successful-OK
    There are no errors, however, nothing comes out of the printer.  It works for all the Mac OS Client machines, but not for any of the Windows 7 machines.
    How to share print queue with Windows 7 successfully?

    I'm back on this problem.  I thought I would give more details as I still can't print. 
    Operating System: 10.6.8
    Driver for Canon LBP6750 UFRII prints from Mac and prints from Windows 7.  However, printing from Windows 7 as you share the printer from your Mac does not print out anything and has no errors.
    JOB INFO
    Completed smbprn.00000004 Microsoft Word - Document 1 3:43PM Today 3:43PM Name
    CUPS > access_log
    localhost - - [01/Feb/2012:15:43:33 +0900] "POST /printers/FLOOD_6750_UFR HTTP/1.1" 401 2003 Print-Job successful-ok
    localhost - lino [01/Feb/2012:15:43:33 +0900] "POST /printers/FLOOD_6750_UFR HTTP/1.1" 200 2003 Print-Job successful-ok
    CONSOLE MESSAGES
    2/1/12 3:47:45 PM    com.apple.launchd.peruser.501[
    200]    (jp.co.canon.UFR2.BackGrounder[664]) posix_spawn("/Library/Printers/Canon/UFR2/Utilities/UFR II BackGrounder.app/Contents/MacOS/UFR II BackGrounder", ...): No such file or directory

  • In Tiger server print queues stopped

    we are having the problem when we updated the server to Tiger that the print queues do not hold the jobs now and can't figure out why is this. Any leads?
    TIA

    Hi Zavion,
    à
    I am just curious why I see different behavior between the servers even tho they are the exact same image and the print queue setup is the same as well.
    Would you please let me confirm whether use the same account to do those operations when see that different behavior?
    Meanwhile, please temporarily
    disable firewall and antivirus program and then check if you still see the two different result.
    If any update, please feel free to let me know.
    Best regards,
    Justin Gu

  • Printer Queue Clogged

    I am printing to an HP LaserJet 1022. I've been running this printer for about a year with no problems at all. For some reason now when I print, it will stay in the queue until I go in and delete the last job that printed. Once it's printed the file, it doesn't move it out of the queue. I've deleted the printer and reinstalled it several times, unplugged it, turned it off, restarted, etc. I've gone into ~/Lbrary/Printers and deleted the queue there and that doesn't work either. Is there some other file that I need to delete to start from zero?

    First thing when printer issues arise - Check to see if there is a driver update available. The OS has undergone a number of changes in the last year, perhaps the driver has, too ... and don't forget to Repair Disk Permissions after.
    If that isn't the issue, see if there is a preferences file or folder for the printer in your User|Library|Preferences folder. That's most likely the cause of the queue problem and when you deleted the queue it just got recreated by the driver using the corrupt prefs, perhaps.
    HTH |:>)
    Bob J.

  • Kerberised printing to AD print queues from OD Clients

    Hello,
    I am trying to print to AD print queues from OS X 10.5.4 and my users keep getting requests for authentication. I heard that the printing to AD print queues was now kerberised and working in OS X leopard. The users are from the AD and log in fine with managed preferences from the Open Directory.
    What do i need to do to get this working properly?
    It is the only thing that is stopping me integrating OS X into my Active Directory.

    Thanks for letting me know.
    I did find the mentioned link. I also found a link on the apple-scripts forum as well which utilizes the same implementation but in a package form for a more user-friendly deployment.
    It can be found here if you are interested:
    [http://www.apple-scripts.com/forum/viewtopic.php?f=2&t=125&p=470#p470]
    Again this does not work in leopard.
    To get around this in the end i decided to use Papercut NG as all i needed to do was manage the print queues via quotas. This does the job nicely as it is cross-platform and keeps the quota system in one place. Great as i can now print to the os x server print queue from os x and print to the AD queues from Windows all with their own authentication systems.
    Message was edited by: Newbie-2-macs

  • Snow leopard server printing

    I've got a Mac mini running Snow Leopard Server (10.6.8) and the printer sharing has never worked. I have a Canon i860 printer hooked up to the Mac mini via USB. I have created an LPR print queue for that printer in the Server Admin app and everything seems fine -- it says that the printer service is running, it has a name, and it is showing up in the list of Bonjour printers from the other machines on the network.
    However, after adding this printer, no machines will print to that print queue over the network. The Mac mini will print to that printer over the direct USB connection, but other computers will not. Thus far:
    - the print queue shows up in the Bonjour list
    - you can add that printer to any computer on the network
    - you can (attempt) to print to it
    - but then all you get is an error message: "Network host 'Beefeater.local.' is busy; will retry in 30 seconds..."
    It is as though the print jobs are not sent because no jobs show up in the queue in the Server Admin app on the server.
    Any ideas?

    Found this thread: https://discussions.apple.com/message/13132912#13132912
    ...and renamed my print queue from "i860 on Beefeater" to "i860_beefeater"
    Now instead of getting the "will retry" message cited above, the problem is that it displays a message that says "Copying print data..." and then shows a message that says "Printer paused." Clicking "Resume" in the toolbar does nothing; no jobs show in the Snow Leopard Server print queue; and there is no indication that the printer itself is having any trouble.
    Ideas?

  • Publish client print queues as managed preferences?

    Hello,
    I followed the documentation from Papercut NG on Mac printing, section Publishing the printer via Workgroup Manager to get the defined print queues for my client machines published as managed preferences.
    I set up the print queues on the server. On the client, I configured the server print queues using the local Administrator account and printed successfully a few test pages. I then logged in with an Open Directory account with admin privileges. I then open Workgroup Manager, select a Computer Group, click Preferences, select Printing. I enable Manage Always, but the list of Available Printers remains empty, contrary to what the screenshot tells me from the referred article.
    Environment:
    + Snow Leopard Server 10.6.1 on a MacMini.
    + Snow Leopard 10.6.1 on a MacPro.
    Am I missing something?
    Ringo

    Hello,
    I followed the documentation from Papercut NG on Mac printing, section Publishing the printer via Workgroup Manager to get the defined print queues for my client machines published as managed preferences.
    I set up the print queues on the server. On the client, I configured the server print queues using the local Administrator account and printed successfully a few test pages. I then logged in with an Open Directory account with admin privileges. I then open Workgroup Manager, select a Computer Group, click Preferences, select Printing. I enable Manage Always, but the list of Available Printers remains empty, contrary to what the screenshot tells me from the referred article.
    Environment:
    + Snow Leopard Server 10.6.1 on a MacMini.
    + Snow Leopard 10.6.1 on a MacPro.
    Am I missing something?
    Ringo

  • Print Queue Management via Server Admin not working

    We have Xserves (10.5.8) running the Print Service for queue management to our printers. Clients print through the server just fine.
    When the printer jams or is otherwise paused, print jobs pile up in the queue as expected. The queue can be seen and managed by logging into the server, going to Server Preferences/Print & Fax and selecting the print queue.
    However, when the queue for the paused printer is viewed within Server Admin/Print, the queue shows as empty and therefore can't be managed. We want to use Server Admin for this function because:
    1) Server Admin can be run remotely on a workstation, so no login to the server required.
    2) We can assign Print Service management rights to select non-admins so they can manage the queues.
    Any ideas on why Server Admin fails to show spooled jobs? Is it working for anyone else?
    I am using Server Admin version 10.5.3 which are the latest available that comes with Server Admin Tools 10.5.7. We had been running 10.5.7 on the Xserve and it didn't work then either.

    Here's a bit more information about our setup and our experiences with Apple's CUPS implementation:
    On the server, all printer queues are set up with only lpr and ipp sharing enabled with the PPD setting for each printer set to Generic Postscript. We found that setting the PPD to the printer specific one on the server caused problems when clients tried to use printer specific options, like paper tray selection, etc.. The selection would be undone, apparently because the driver on the server would override the previous settings. Using Generic Postscript allows the client PPD settings to go through unmodified. Our printers are general a mix of HP LaserJets and some Sharp Copiers.
    All clients use lpd to the server queues with the printers' actual PPDs configured. Using ipp is superior in that printer feedback (jams, out of toner, etc) makes it back to the clients, but ipp only works when the client, the server, and the printer are on the same network. If the ipp client is not on the same network, the client spooler immediately goes into a paused state and the print job is stuck on the client.
    Using lpd to the server queues works reliably, but there is no feedback to the client. Jobs disappear from the client queue and go to the server, appearing to the user as a successful print. If the printer is down, there's nothing they can see or do about it.

  • Server Admin not showing jobs in print queue

    Hi All,
    I'm not sure if others are having this problem or if it's just me.  I am running Mac Server OS X 10.6.7  When I go to Server Admin and select "Print" and then "Job Status", I get a list of all the server's print queues.  In the pane below the list of queues, there is a section that says "Jobs on Queue:" which then allows me to select any specific print queue.  The problem is, no matter what queue I select, I am never able to see any of the print jobs going through the queue.  I have sent multiple jobs to different printers on the server, all while watching the "Jobs on Queue" window for the appropriate printer.  In every test, I have never seen ANY print job show up in that window, even though all the print jobs print out fine.  I have even tried pausing a printer to let jobs queue up, and still nothing shows up in that window.
    I have also tried the same tests while viewing the prints queues from the "Print & Fax" System Preferences pannel directly on the server.  Still no luck.  Everything prints out fine, but I am unable to ever see any print job hitting the queue.
    The reason I even noticed this problem is because a user accidentally printed a 500 page document by mistake.  The user called me to stop the job, but I was unable to see anything in the queue to kill.  I tried deleting the job directly from the printer, but this just caused the printer to lock up.  I would try powering off the printer and restarting it, but as soon as it powered back on, the print job would restart.  I even tried restarting the server, but as soon as the server came back online, the print job started again.  Finally, after hunting on the web, I tried logging into CUPS via http://localhost:631 and was able to see the print job listed there and finally delete it.
    Is there any way to monitor print jobs on the server in real time?  I found this previous archived thread describing what appears to the same problems using Mac Server OS X10.5.8, but there was never any solution listed before the thread was archived.
    https://discussions.apple.com/thread/2152737

    Is there anyone using printing services on a Mac server at all that could comment on whether or not you see the print jobs listed in the queue when printing?

  • Windows 2008 R2 Terminal Server clients lose remote printer queues after logoff

    There are similar issues to this already on the forums but not precisely like this as far as I can tell, and I have tried all the fixes mentioned in those other threads.
    Windows 2008R2 terminal server connecting to a 2008R2 print server. A script maps a connection to the print server on login. Users can browse the print server, connect to print queues to add them, and the queues work OK at first. As soon as they logoff/login
    again, the queues still appear in their list of printers but cannot be selected for printing ('Print' button is greyed out).
    Domain administrator users can print OK always; this is only affecting regular-user accounts, so it is probably a security/permissions issue. Print queues configured on the terminal server itself are OK, this only affects the queues on the
    print server.
    No errors are generated in the Event Logs. No failures seen for the print spooler or anything else.
    I have added Everyone with Full Control to C:\windows\system32\spool on the terminal server. Tried giving full permissions to all in the printer properties. Cleaned out all registry keys in Client Side Rendering Print Provider as mentioned in some other
    threads. In group policy, client printer redirection and LPT port redirection is allowed, use Easy Print driver first, and the print server is in the Intranet zone for low security. The issue happens for all print queues on the print server with a variety
    of drivers so I don't think it is driver-related.

    A bad GPO being applied ??
    If you isolate a user, remove all GPO (even loopback's one), connect manually to a printqueue to make him install's one. Logoff and reconnect and check again if the printqueue work good. The only right that could block you is the driver's installation, but
    I really sure that you don't have that issue (as it would be logged anyway)
    The admin. account often have less GPO that apply to him.
    MCP | MCTS 70-236: Exchange Server 2007, Configuring
    Want to follow me ?  |  Blog:
    http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

  • Server Admin doesn't show Print Queue status

    When I look at my print queues (all 17) under Server Admin, it shows queue name, # of jobs, shared via (IPP & SMB), and printer kind (HP LJ 1022n and HP LJ P2015). It has a column for status, but this is always 100% empty/blank. Also, if I go to the Jobs tab, then I can pick "Jobs on Queue" for all the queues, but the line below for "Queue Status" is again always blank.
    Is there something I can do to get this info to show up in Server Admin? I know that CUPS knows the printer status, as I can go to localhost:631 and see the status in the Printers list and the Jobs list.
    It isn't life threatening. It is just annoying to have to go to the web page when Server Admin -almost- gets me everything I need to diagnose a teacher's printing problem remotely.

    Hi Keith
    You could always consult the Print Service logs. If you set the logging levels to Debug or Debug2 you should get everything. You have to be a bit careful with this as the log can get quite large. Other than that I don’t know of anything that is available out of the box.
    There may be others that can suggest a 3rd party solution that gives you the appropriate feedback you are looking for. Opening port 631 should not be that much of risk I would have thought?
    Tony

  • How can I list print queues per server via power shell script

    Hello,
    we are managing many print servers on our domain environment,  now for auditing purpose I need to report print queues per server,  and it seems bit difficult task doing it via GUI in print management view, could someone help me with script which
    gets me the no. of print queues on each print server.
    Also I need to list all the print drivers installed on each print servers. 
    I tried to list the drivers " Get-WmiObject win32_printerDriver -filter " but this will get me complete information about the driver, I need to list only the driver name (-filter) either _RELPATH or _PATH
    dibu

    You can also use WMI like this:
    (get-WmiObject win32_printer -computer ws702).count
    I don't understand what you mean by list only.  Just select what you need.
    See: http://technet.microsoft.com/en-us/scriptcenter/dd742419
    That will give you some basic background on how to use PowerShell to get the properties of objects.
    ¯\_(ツ)_/¯

  • Cannot migrate users print queues to new print server

    I am needing to move the print queues on users computers to a new print server that I have set up by I am not able to do so. I have over 200 users at the office. I am thinking it is a problem getting to run it on the clients, but not sure where it is failing...
    To start... I have moved the print queues from Server 2003 to Server 2008 R2. The machines are both 64 bit. I was able to export the drivers and the print queues to the new server using the print migrate tool. The names of the printers are the same on both...
    The names of the print servers are different. I added a print queue to a test client and was able to print to it without a problem mapped to the new server, so that's not the problem.
    What I can't do is use the script (see below) to remap the clients to the new server. I have tried and configured the script as a user log on script, configured a group policy and placed my test user in the OU. Rebooted the machine, logged
    on with the test account but the print queues stay the same. I have even tried to run the script locally but still no joy... it runs but the queues stay the same. I used RSOP and see that the script is being applied... I am running Windows 7 Professional.
    I really need to get this resolved as the server is being decommissioned within the month.
    Option Explicit
    Dim from_sv, to_sv, PrinterPath, PrinterName, DefaultPrinterName, DefaultPrinter
    Dim DefaultPrinterServer, SetDefault, key
    Dim spoint, Loop_Counter, scomma
    Dim WshNet, WshShell
    Dim WS_Printers
    DefaultPrinterName = ""
    spoint = 0
    scomma = 0
    SetDefault = 0
    set WshShell = CreateObject("WScript.shell")
    from_sv = "\\srvprint_1" 'This should be the name of the old server.
    to_sv = "\\srvprint_2" 'This should be the name of your new server.
    'Just incase their are no printers and therefor no defauld printer set
    ' this will prevent the script form erroring out.
    On Error Resume Next
    key = "HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\Device"
    DefaultPrinter = LCase(WshShell.RegRead (key))
    If Err.Number <> 0 Then
        DefaultPrinterName = ""
    else
    'If the registry read was successful then parse out the printer name so we can 
    ' compare it with each printer later and reset the correct default printer
    ' if one of them matches this one read from the registry.
    spoint = instr(3,DefaultPrinter,"\")+1 
    DefaultPrinterServer = left(DefaultPrinter,spoint-2)
        if lcase(DefaultPrinterServer) = from_sv then
            DefaultPrinterName = mid(DefaultPrinter,spoint,len(DefaultPrinter)-spoint+1)
            scomma = instr(DefaultPrinterName,",")
            DefaultPrinterName = left(DefaultPrinterName,scomma -1)
        end if
    end if
    Set WshNet = CreateObject("WScript.Network")
    Set WS_Printers = WshNet.EnumPrinterConnections
    'You have to step by 2 because only the even numbers will be the print queue's
    ' server and share name. The odd numbers are the printer names.
    For Loop_Counter = 0 To WS_Printers.Count - 1 Step 2
        'Remember the + 1 is to get the full path ie..
    \\your_server\your_printer.
        PrinterPath = lcase(WS_Printers(Loop_Counter + 1))
        'We only want to work with the network printers that are mapped to the original
        ' server, so we check for "\\Your_server".
        if lcase(LEFT(PrinterPath,len(from_sv))) = from_sv then
            'Now we need to parse the PrinterPath to get rhe Printer Name.
            spoint = instr(3,PrinterPath,"\")+1
            PrinterName = mid(PrinterPath,spoint,len(PrinterPath)-spoint+1)
            'Now remove the old printer connection.
            WshNet.RemovePrinterConnection from_sv+"\"+PrinterName
            'and then create the new connection.
            'Do not create c6100
            if lcase(PrinterName) <> "c6100" then
                WshNet.AddWindowsPrinterConnection to_sv+"\"+PrinterName
                'If this printer matches the default printer that we got from the registry then
                ' set it to be the default printer.
                if DefaultPrinterName = PrinterName then
                    WshNet.SetDefaultPrinter to_sv+"\"+PrinterName
                end if
            end if
        end if
    Next
    Set WS_Printers = Nothing
    Set WshNet = Nothing
    Set WshShell = Nothing

    Hi,
    àI added a print
    queue to a test client and was able to print to it without a problem mapped to the new server, so that's not the problem.
    àWhat I can't
    do is use the script (see below) to remap the clients to the new server.
    Based on your description, I understand that you have moved print queues to new print server via print migrate
    tool successfully. However, when use this script (Remap Printer Connections) to re-map Printer Connections, the script seems to not be ran as expected. Meanwhile,
    I noticed that you had ran the script locally. Did you find any error when ran this script?
    On current situation, this issue seems to be more related to this Remap Printer Connections script. I suggest
    that you would post it in
    Official Scripting Guys Forum. I believe we will get a better assistance there.
    If anything I misunderstand or any update, please don’t hesitate to let me know.
    Best regards,
    Justin Gu

  • Restarting a paused local print queue remotly

    Is it possible to restart a paused print queue remotely? 10.5 does not seem to have the standard "resume" command available.
    I've been having issues where labs will clog a printer with jobs. the default action is for the OS to pause the print queue in question. I can clean out the queues with the "cancel -a -" command fine but I am stuck with random systems in a given lab with paused queues. There are no local admins to un-pause the systems, and disabling authentication to modify the printer (or its queue) is not really an option.
    thanks.

    I've had problems with the print queues in 10.4.x not taking print jobs after the server is restarted. Do a port scan on the server to see if port 515 is open. If it isn't then try restarting the print service on the server. Port scan the server again and see if port 515 is open. If it is open now try printing. I also had problems with ipp printing so have reverted all my clients to LPR. Some client machines I have switched to direct ip printing to the printer. The print queues in 10.4.x haven't been very reliable. I hope this helps.

  • How to create HP LaserJet 2420 printer queue on Solaris 10

    Hi Solaris Gurus,
    I am having difficulty creating a printer queue for HP LaserJet 2420 on Solaris 10 (11/9) Sparc (Sun Fire T5220) server. A popular method used is with hppi (HP Jet Direct) tool but it does not have the exact printer driver and alternative printer drivers (e.g. HP LaserJet 4 / 4M, HP LaserJet 2000 series) resulted in only part of the text occupying the wrong side of an A5 page.
    An alternative approach that has worked in the past for simple default paper tray 2 (single paper tray), with tray 1 reserved for manual feed. This method involves creating a working printer queue on a Windows workstation (XP) / server (2000) with the correct driver and having configured to support Unix printing to receive LPR request from Unix systems in general. A remote printer queue would then be defined on Solaris 10 system which points to the Windows system. However, the printing jobs kept going to tray 1 (top manual feed) even though the Windows printer queue was configured to go to tray 3 (bottom tray).
    The earlier method would be simplest but needs the right driver (PDD) but I don’t know where to find it. The latter approach is also not working despite having got the right driver on Windows. A test page on the target Windows printer queue would print to tray 3 (bottom tray) of the printer correctly.
    Printmgr does not work well with HP printers from experience. It is good for serial and local printers.
    Your advice would be much appreciated.
    Thanks,
    Crystal

    Hi Giogio, and welcome to the HP Forums.
    I am sorry to be the bearer of this news, but do the age of the printer, it is not supported by Mac OS X 10.9. I am including a list below of the supported printers from Apple:
    OS X: Printer and scanner software available for download.
    For more information, I would recommend contacting the Apple Support Communities.
    Thank you for posting on the HP Forums.
    Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
    Jamieson
    I work on behalf of HP
    "Remember, I'm pulling for you, we're all in this together!" - Red Green.

Maybe you are looking for