Printing queue management

I'm not sure this is really a "LabVIEW" problem, but I was looking for someway to solve it from within my program.
In my application, I am automatically printing out a 2 page test report approximately every 15 minutes. (I do this by calling a VI, and printing it out using the 'Print this VI when completed' option.) The problem is that after some time, the print queue eventually builds to a large amount of printouts and begins to bog down system performance. I am assuming that this is because the printer is running out of paper or has jammed; but I can't be sure since I am not local to the site where the software is running.
Is there some way from within LabVIEW for me to determine if there has been a problem printing out my reports, or if the printer status is OK? I am printing to a HP Laserjet 1022n that is just plugged into the LAN. There doesn't seem to be an API in any of the manuals I've looked at for me to send a message to the printer via the network to get the size of the print queue or anything like that. The PC is running Windows XP.
Has anyone dealt with similiar problems, or have any ideas? The best that I've been able to come up with is just to task schedule in windows a reset of the print spooler at a regular interval to stop this from happening. (Which is not really a good solution to the real problem.)

A simple solution might be to open a command prompt using the SYSTEM EXEC.VI (essentially a container for a CIN {Code Interface Note}) and issue the NET PRINT command which will return a list of jobs in the printer queues.
You could then work out if jobs were being printed or not and subsequently decide if to warn the user or selectively delete print queue items.
You will get a list of all print queus so you may need to have the user indicate a specific print queue or server.
The other option is to start accessing the Windows API to obtain printer que information, the former is likely to be the fastest to implement, if tedious.
Below is a sample output for a computer without print queue
"NET PRINT
\\computername\sharename
          [\\computername] job# [/HOLD | /RELEASE | /DELETE]
NET PRINT displays print jobs and shared queues.
For each queue, the display lists jobs, showing the size and status of each job, and the status of the queue.
\\computername        Is the name of the computer sharing the printer queue(s).
sharename                Is the name of the shared printer queue.
job#                          Is the identification number assigned to a print job. A computer with one or more printer queues assigns each print job a unique number.
/HOLD                       Prevents a job in a queue from printing.The job stays in the printer queue, and other jobs bypass it until it is released.
/RELEASE                Reactivates a job that is held.
/DELETE                  Removes a job from a queue.

Similar Messages

  • Java Print Queue Manager

    I am new to Java. I recently ran into a need to have a Java print queue manager to handle network printers. Is something like this already available or are there companies who can provide this?
    Please email me with any comments ([email protected]).
    Thank you in advance for any help.
    Regards,
    JS

    Have a look at javax.print API. I'll warn you, it's limited, but it can dynamically discover networked printers.

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

  • [Solved] Lightweight print queue manager recommendations?

    My wife uses fluxbox and is very happy with it, but she is not really a command line user. However, once in a while she needs to look at her print queue and sometimes delete a print job. lpq and lprm are out of the question, although I suppose I could write a bash script for her to do that easily. Also, I don't want to confuse her with the cups interface as this requires root login to delete print jobs.
    Anyone know of a small print queue GUI manager that is lightweight and does not require a load of KDE or Gnome libraries? I don't see one in the AUR that is not KDE based.
    Last edited by lagagnon (2012-03-10 00:04:52)

    lagagnon wrote:That requires root login and root password to delete stuff on the queue.
    Are you sure? Looks like /etc/cups/cupsd.conf can be tweaked, e.g.:
    <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
    Require user @OWNER @SYSTEM susan
    Order deny,allow
    </Limit>
    <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
    AuthType Default
    Require user @SYSTEM susan
    Order deny,allow
    </Limit>
    Where the user you want to allow is named, of course, susan.
    This is in cups 1.4.8, anyway.

  • 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

  • Rights needed to manage and create print queues

    On a Netware 5.1 install with eDir 8733, what rights would I need to give a
    user so that this person would be able to create new print queues, print
    servers, and print objects? This person is not an admin and I prefer not
    making him an admin equivalent if at all possible.
    Also, on a side note, how do I create a new print queue/server/printer
    without using HP Jet Admin for an HP printer? Has anyone done this with out
    Jet Admin?
    Thank you

    Oh, but how do I link them to the MAC of the printers NIC?
    Isn't that what HP JetAdmin did for me?
    Thanks
    "Peter Kuo" <[email protected]> wrote in message
    news:[email protected]..
    | Will wrote:
    |
    | > Also, on a side note, how do I create a new print queue/server/printer
    |
    | Just use NWAdmin ...
    |
    |
    | --
    |
    |
    | Peter
    | eDirectory Rules!

  • Printing w/Leopard & AD-based Windows Print Queues:

    For those interested, I have written an overview of printing in Leopard 10.5.0 to Windows print servers (published queues Active Directory). Your mileage may vary. This document contains the good the bad and the ugly.
    Objective:
    Get Leopard based Macs to print to AD published SMB print queues hosted on Windows 2003 print servers. Sounds easy, huh?
    Overview:
    Print Servers:
    Windows 2003 print servers.
    Printers:
    All the printers in my test were all new HP network b/w printers or network MFP b/w printers. All of them were less than 2 years old. None of them were consumer-grade home USB printers.
    Mac Clients:
    My test clients were Intel MacBook Pros and Intel iMacs running 10.5.0 Leopard. All of them had user AD accounts and all Macs were bound to AD using Directory Utility (or dsconfigad)
    The AD clients have a unique naming convention at my company. In my environment we use the initials of the person for their login name (SAM). Example:
    Real “human” Name: “Stephen Paul Jobs”
    Long Active Directory Name: “Steve Jobs”
    Short Active Directory Name: “spj”
    “Legacy” NT Names: “domain\spj”
    Full domain name (used for email etc): “[email protected]
    (you get the idea...)
    Note: My Mac clients are not in an Open Directory domain. No “Magic Triangle” in this environment. Pure AD for the sake of this example. I am not managing the Mac clients via MCX in this scenario.
    Print Protocols:
    All the print queues hosted on the print servers were standard SMB/CIFS print queues. The syntax (UNC) looks like this:
    smb://print_server.domain/queue
    (This syntax is invisible to most users printing to AD-published printers (or any network based printer really) . Most users will have no idea what protocols are being used.)
    Procedures:
    Part 1: Set up a new printer from an existing AD-published print queue:
    From the Apple menu select “System Preferences...” (or launch it from /Applications). The Printer Setup Utility app no longer exists. Apple has discontinued it fro various reasons.
    Click on the Printer & Fax pane.
    Click the “+” button on the left. This will launch the Apple Printer Browser (called “AddPrinter”, and lives in /System/Library/CoreServices), which looks similar to the previous browser in Tiger. The Printer Browser by default will usually show network printers vai Directory Services (AD/OD etc) as well as Bonjour printers and Mac OS X based shared printers – if they are shared via IPP and LPR under certain circumstances).
    Select the desired AD-published print queue you want to print to by highlighting it in the browser list and clicking the “Add” button. (Note: Print queues published via Active Directory will show up as “Open Directory” printers, even though this is not 100% technically correct.)
    Before the queue will be added, you will be prompted to authenticate as a local administrator. If you are not an admin you are screwed. Enter your name and password.
    Once the print queue is added, it will show up on your Mac in several ways (barring any bugs – see below). Here are the ways to tell if you have added the print queue successfully:
    A The new print queue will now be displayed in the Print & Fax system pref pane (but not always – see below).
    B You will see a printer proxy application in ~/Library/Printers/ which corresponds to your new print queue. This is the print monitor app that will show up in your Dock when you print to the queue.
    C You can see the new print queue via the CUPS admin page at http://localhost:631/printers.
    D You can see your new print queue from the Terminal by typing this command: “lpstat –v” (type “man lpstat” for more info on the lpstat and related commands)
    E You can also see your printers by launching an print-enabled application such as TextEdit or Safari and printing a page. You will be presented with Leopard’s new print dialog box (which now includes a print preview pane). From the “Printer” drop-down menu you can see all of your printers. You can add a printer from here too (which takes you to the steps listed above)
    (of course, most end users will only use option A listed above. The other options are more abstract and complicated)
    Now that the AD print queue has been setup on your Mac, you can print to it (maybe).
    Part 2: Printing to an AD-published print queue:
    Open a document you want to print.
    Choose “Page Setup...” from the File menu if you need to configure the job. (Optional)
    Choose “Print” from the File menu.
    From the Print dialog box, choose the desired print queue from the Printer menu
    Click the Print button.
    You will need to authenticate with a valid Active Directory username and password. You don’t have to have administrator credentials, but you have to verify that you are a domain member. In my environment, my Windows print server doesn't require authentication, but for some reason Leopard or CUPS makes you authenticate. (See below). Not only is this a major PIA, but the authentication dialog box itself is formatted to include the wrong credentials format for authentication in the first place.
    Volia! Done. Easy huh? Not really. Read on for the ugly stuff.
    My Complaints and Caveats:
    OK, so here’s where I vent, complain and scratch my head. Join in on the fun.
    Sometimes shared print queues don’t show up in the Print & Fax system preference pane after they have been added. I have no idea why. The local CUPS admin page (http://localhost:631) on my Mac test clients can see the connected queues, and the queues show up in ~/Library/Printers. The “lpstat –v” command shows the connect queues too. But for some reason, sometimes network print queues that I have previously setup (and use regularly) don’t show up in the Leopard Print & Fax preference pane. Local USB printers always show up fine for me.
    2. When challenged to authenticate a print job to a Windows print server (AD), the Mac’s authentication dialog box pre-populates the AD user’s name in the “Name” field incorrectly. Example:
    A user named “Joe Is Cool” (short name “JIC”) prints a job to the print server. The print auth dialog box challenges him for a name and password. It is pre-populated already with the name of “Cool, Joe”. When a valid AD password is entered, the job is rejected (it fails authentication and gets put on hold – which is hard to see this unless you explicitly look at the Printer.app proxy tool in the Dock). However, if the user replaces “Cool, Joe” with his official AD short name of “JIC” and then enters his AD password, the print job is accepted and printed. I wish Apple didn’t try and pre-populate the dialog box! Can this be avoided or prevented?
    In my environment, my Windows print server doesn't even require authentication, but for some reason Leopard or CUPS makes you authenticate. I’m working with my Windows administrators to figure this out. It will only accept user names with the short name format. It will not accept long (full) names or NT legacy names.
    3) The Printer Setup Utility app, which used to live in /Applications/Utilities, no longer exists. Apple has discontinued it for various reasons. Mainly security and simplicity. I wish it was still available, but the system pref pane works fine (well, usually)
    4) Active Directory-based print queues will show up in the OS X Printer Browser as “Open Directory” printers, even though this is not 100% technically correct. Why can’t OS X tell the difference between OD queues and AD queues and label them as such?
    5) Leopard has locked down the ability to add network printers. You now must be a local administrator in 10.5 or later. I understand the importance of this security measure in certain environments, but why can’t there be an option in the Security preference pane to “Allow non-admins to add printers”? This would make me very happy.
    6) Setting the default printer and resetting the CUPS system now require you to right-click in the left side of the Print & Fax pane. There no longer is a button or menu option to do this.
    7) Sometimes after a job has printed the printer proxy app (from ~/Library/Printers) stays in the Dock and won’t go away.
    Conclusion
    Please chime in on your experiences, bugs, opinions and comments.
    Message was edited by: Daniel Stranathan

    I have noticed several of the changes in our system when printing to an AD printer from a Leopard client. I have one issue that is pretty odd and I'm not sure what is going on. When printing an Excel worksheet, I get prompted for AD credentials. After submitting the job, the print queue says "Waiting for Authentication", I have to press the Resume button and then the authentication dialog pops up. I successfully authenticate (My auth dialog is populated correctly and the remember to keychain option is selected) and the job prints fine. If I print the same document again (without closing the worksheet or Excel), or any other worksheet, I still have to reauth. I can print just fine to the same printer from Textwriter and I do not need to authenticate. Weird...

  • Moving print queues

    We are preparing to move from queue based printing to iPrint and are
    experiencing the following problem with Windows XP locked-down workstations.
    We created the queue directory on the iprint server, gave the ou rights to
    the queues directory, changed the appropriate attributes to point the queue
    to the new server and volume, and under qms management, had the iprint
    printer service the queue. If you add the printer (queue based), it works
    fine. If you log into the workstation as admin, it works fine. If you log
    in as the "normal locked-down user" it doesn't. What we did find is that
    there are two keys in
    HKEY_Local_Machine\SOFTWARE\Novell\Print\NDSConnec tions, under the tree and
    queue. The first queue key is the short name and has the correct settings.
    The second key is fully qualified and is retaining the old setting
    (server/volume). If we manually change the key and reboot it works.
    How do we change the second key without having to manually change it?
    Don't say ZENworks as the queues will be different for every user.
    Thanks,
    Mark

    Hi Mark,
    What iprint client version ?
    Try the latest version 4.12
    http://support.novell.com/cgi-bin/se...i?10099419.htm
    If this doesn't help, repost your question in the iprint forum. Some iprint
    developers hang out there, that provide good support.
    Peter vd Woude
    Novell Support Forums SysOp
    > We are preparing to move from queue based printing to iPrint and are
    > experiencing the following problem with Windows XP locked-down
    > workstations.
    >
    > We created the queue directory on the iprint server, gave the ou rights to
    > the queues directory, changed the appropriate attributes to point the
    > queue
    > to the new server and volume, and under qms management, had the iprint
    > printer service the queue. If you add the printer (queue based), it works
    > fine. If you log into the workstation as admin, it works fine. If you
    > log
    > in as the "normal locked-down user" it doesn't. What we did find is that
    > there are two keys in
    > HKEY_Local_Machine\SOFTWARE\Novell\Print\NDSConnec tions, under the tree
    > and
    > queue. The first queue key is the short name and has the correct
    > settings.
    > The second key is fully qualified and is retaining the old setting
    > (server/volume). If we manually change the key and reboot it works.
    >
    > How do we change the second key without having to manually change it?
    > Don't say ZENworks as the queues will be different for every user.
    >
    > Thanks,
    > Mark

  • 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.
    ¯\_(ツ)_/¯

  • Print Queue Status Monitor with Email

    I have a brand new Windows Server 2012 R2 Datacenter virtual server that is setup as a print server.  I saw the custom filters in the Print Management console but found out that notifications only work with that console open.  Since I'm not logged
    into that machine all the time, I need a powershell script that can do what the custom filters do in the Print Management console.  Here's what I'm looking for:
    1. When the print server starts the script starts.  This script should always stay active.
    2. The script polls the print queues for a change in status to anything other than Ready every 5 minutes or so.
    3. If the printer name contains "CC2", then email certain people the status of that particular printer.  Only email them once so as to not spam them with constant emails (maybe 1 email per day per status change).
    So basically I'm looking to email my customer service department if one of their printers goes to a status of anything other than Ready.  Is something like this possible with Powershell?

    My scripts compares the customer service printers (printer names starting with CC2) status every 5 minutes.  If the status has changed and there are Offline printers then customer service gets an email.  I'm using Task Scheduler to start the script
    at 6:00am every day and the script will quit around 11:00pm.  It's not very elegant but it will get the job done.  Thanks for all your help!
    # Time limit when the script expires
    $Limit = (Get-Date).AddDays(1)
    $SleepSeconds = 300
    $PreviousStatus = @()
    while ((Get-Date) -lt $Limit)
    $CurrentStatus = Get-Printer -computername SERVER | Where {($_.PrinterStatus -ne "Normal") -and ($_.Name -Match "CC2")} | Select Name,PrinterStatus
    if ($CurrentStatus)
    if (Compare-Object $CurrentStatus $PreviousStatus -property Name,PrinterStatus)
    # Establish Connection to SMTP server
    $a = "<style>"
    $a = $a + "TABLE{border-width: 1px;border-style: solid;border-color: black;border-collapse: collapse;}"
    $a = $a + "TH{border-width: 1px;padding: 0px;border-style: solid;border-color: black;}"
    $a = $a + "TD{border-width: 1px;padding: 0px;border-style: solid;border-color: black;}"
    $a = $a + "</style>"
    $filedate = get-date
    $smtpserver = “smtp.gmail.com”
    $msg = new-object Net.Mail.MailMessage
    $smtp = new-object Net.Mail.SmtpClient($smtpServer )
    $smtp.EnableSsl = $True
    $smtp.Credentials = New-Object System.Net.NetworkCredential(“[email protected]”, “password”); # Put username without the @GMAIL.com or – @gmail.com
    $msg.IsBodyHtml = $True
    $msg.From = “[email protected]
    $msg.To.Add(”[email protected]”)
    $msg.To.Add(”[email protected]”)
    $msg.To.Add(”[email protected]”)
    $msg.To.Add(”[email protected]”)
    $msg.To.Add("[email protected]")
    $msg.Subject = "Printer Status Errors $($filedate)"
    $msg.Body = Write-Output -InputObject (Get-Printer -computername SERVER | Where {($_.PrinterStatus -ne "Normal") -and ($_.Name -Match "CC2")} | Select Name,PrinterStatus,Comment,Location,Portname) | ConvertTo-Html -Head $a
    $smtp.Send($msg)
    $PreviousStatus = $CurrentStatus
    Start-Sleep -Seconds $SleepSeconds
    if ((get-date).Hour -eq 23) {Exit}

  • Printer proxy problem? 300 jobs in my print queue.

    I left my MacBook Pro on overnight. When I 'woke it up' about 24 hours later, I found that I had 303 documents in my print queue for my HP LaserJet 1320. Printer proxy has quit upon awakening in several instances before. This is the first time the queue has 'completed' printing of documents. Some of the documents were sensitive. Do you think my security/ID has been compromised?

    “Windows Server Print Services 2012 Printer Queue” target is a part of  Windows Server Print management
    pack which is useful for collecting the print queue information.
    The Base windows MP wont be able to do this.

  • Print Queue suddenly stopped: OS X 10.4.10 and Bonjour via AirPort

    I've been using an Intel iMac with no problems for many months: 2 printers attached: 1 inkjet via USB, and 1 HPLJ1200 via Bonjour through Airport/USB.
    System Version: Mac OS X 10.4.10 (8R2218),
    Kernel Version: Darwin 8.10.1
    Suddenly, the Bonjour one has stopped. One minute it's printing, next minute, all jobs go into a queue but never emerge. The printer queue shows in the dock with a red "!" with all jobs in that queue stopped. If I restart the queue, it just tries to restart (green) then reverts to red "!" again. The direct USB printer continues to work fine. Problem is confined to the Bonjour printer.
    I've tried:
    1. Checking all the cables etc. Turning everything off, then one by one on. Restarting iMac, etc.
    And then (after a few experiences of others on the Forums):
    2. Verifying and fixing permissions via Disk Utility (there were no problems to fix)
    3. Uninstalling the HPLJ, and then reinstalling.
    4. Installing a 2nd instance of the HPLJ to bypass the first instance (which has a little grey "!" next to it in the Print dialogue box)
    All to no avail.
    I've then tried:
    5. OnyX, running maintenance scripts, cleaning caches.
    Still no good.
    6. Finally, I've looked into the CUPS Error Log via OnyX, and I can see a number of Errors (see transcript at end of this email). I have removed the HPLJ from the printer setup, then reinstalled it. The CUPS Error Log for this is shown below, from removal, to reinstallation.
    Is there a Unix or OSX expert in the forum who can help please?
    Many thanks
    LeslieB
    =================
    (extract of newest lines of CUPS Error Log, from OnyX:
    Covers process of deleting, then readding HPLJ1200, to the USB port on Apple Airport. Printer was recognised as Bonjour and installed. Sharing was enabled. Then test page was printed ->failed to print and queue showed red "!")
    E [14/Aug/2007:21:52:15 +1000] getprinterattrs: resource name '/printers/®¯6' no good!
    E [14/Aug/2007:21:52:15 +1000] getprinterattrs: resource name '/printers/Pâ¨ê' no good!
    I [14/Aug/2007:21:52:28 +1000] Printer 'HPLaserJet1200' deleted by ''.
    I [14/Aug/2007:21:52:28 +1000] Saving printers.conf...
    E [14/Aug/2007:21:52:28 +1000] getprinterattrs: resource name '/printers/HPLaserJet1200' no good!
    I [14/Aug/2007:21:55:53 +1000] Setting HPLaserJet1200 device-uri to "mdns://HP%20LaserJet%201200.pdl-datastream.tcp.local./?bidi" (was "file:/dev/null".)
    I [14/Aug/2007:21:55:53 +1000] Setting HPLaserJet1200 printer-is-accepting-jobs to 1 (was 0.)
    I [14/Aug/2007:21:55:53 +1000] Setting HPLaserJet1200 printer-state to 3 (was 5.)
    I [14/Aug/2007:21:55:53 +1000] Saving printers.conf...
    I [14/Aug/2007:21:55:53 +1000] New printer 'HPLaserJet1200' added by ''.
    I [14/Aug/2007:21:56:02 +1000] Installing config file "/private/etc/cups/cupsd.conf"...
    I [14/Aug/2007:21:56:02 +1000] Listening to 0:631
    I [14/Aug/2007:21:56:02 +1000] Listening to c0173200:0
    I [14/Aug/2007:21:56:02 +1000] Loaded configuration file "/private/etc/cups/cupsd.conf"
    I [14/Aug/2007:21:56:02 +1000] Configured for up to 100 clients.
    I [14/Aug/2007:21:56:02 +1000] Allowing up to 100 client connections per host.
    I [14/Aug/2007:21:56:02 +1000] Partial reload complete.
    I [14/Aug/2007:21:58:30 +1000] Adding start banner page "none" to job 5.
    I [14/Aug/2007:21:58:30 +1000] Adding end banner page "none" to job 5.
    I [14/Aug/2007:21:58:30 +1000] Job 5 queued on 'HPLaserJet1200' by 'leslie'.
    I [14/Aug/2007:21:58:30 +1000] Started filter /usr/libexec/cups/filter/cgpdftops (PID 1474) for job 5.
    I [14/Aug/2007:21:58:30 +1000] Started filter /usr/libexec/cups/filter/pstops (PID 1475) for job 5.
    I [14/Aug/2007:21:58:30 +1000] Started filter /Library/Printers/hp/filter/hppostprocessing (PID 1476) for job 5.
    I [14/Aug/2007:21:58:30 +1000] Started backend /usr/libexec/cups/backend/mdns (PID 1477) for job 5.
    E [14/Aug/2007:21:58:32 +1000] [Job 5] Unable to locate printer 'Leslie-Office.local.' - Unknown host
    E [14/Aug/2007:21:58:32 +1000] PID 1477 stopped with status 1!
    I [14/Aug/2007:21:58:32 +1000] Hint: Try setting the LogLevel to "debug" to find out more.
    I [14/Aug/2007:21:58:32 +1000] Saving printers.conf...
    I [14/Aug/2007:21:58:41 +1000] Saving printers.conf...
    I [14/Aug/2007:21:58:41 +1000] Printer 'HPLaserJet1200' started by ''.
    I [14/Aug/2007:21:58:41 +1000] Started filter /usr/libexec/cups/filter/cgpdftops (PID 1490) for job 5.
    I [14/Aug/2007:21:58:41 +1000] Started filter /usr/libexec/cups/filter/pstops (PID 1491) for job 5.
    I [14/Aug/2007:21:58:41 +1000] Started filter /Library/Printers/hp/filter/hppostprocessing (PID 1492) for job 5.
    I [14/Aug/2007:21:58:41 +1000] Started backend /usr/libexec/cups/backend/mdns (PID 1493) for job 5.
    E [14/Aug/2007:21:58:43 +1000] [Job 5] Unable to locate printer 'Leslie-Office.local.' - Unknown host
    E [14/Aug/2007:21:58:43 +1000] PID 1493 stopped with status 1!
    I [14/Aug/2007:21:58:43 +1000] Hint: Try setting the LogLevel to "debug" to find out more.
    I [14/Aug/2007:21:58:44 +1000] Saving printers.conf...
    And while I was typing this forum posting, and doing a further test print, then cancelling it when I could not start the queue, the following error log was appended:
    I [14/Aug/2007:22:06:07 +1000] Started filter /usr/libexec/cups/filter/pstops (PID 1650) for job 5.
    I [14/Aug/2007:22:06:07 +1000] Started filter /Library/Printers/hp/filter/hppostprocessing (PID 1651) for job 5.
    I [14/Aug/2007:22:06:07 +1000] Started backend /usr/libexec/cups/backend/mdns (PID 1652) for job 5.
    E [14/Aug/2007:22:06:09 +1000] [Job 5] Unable to locate printer 'Leslie-Office.local.' - Unknown host
    E [14/Aug/2007:22:06:09 +1000] PID 1652 stopped with status 1!
    I [14/Aug/2007:22:06:09 +1000] Hint: Try setting the LogLevel to "debug" to find out more.
    I [14/Aug/2007:22:06:09 +1000] Saving printers.conf...
    I [14/Aug/2007:22:15:32 +1000] Job 5 was cancelled by 'leslie'.
    I [14/Aug/2007:22:15:40 +1000] Saving printers.conf...
    I [14/Aug/2007:22:15:40 +1000] Printer 'HPLaserJet1200' started by ''.

    Dear All
    I have been able to partially solve this problem myself.
    I've managed to track the problem down to the Apple Airport Express (which is hosting the USB printer via Bonjour). The problem seems to be that the iMac can't see the printer, even thought it's connected.
    It turns out that the problem started at the time of an internet outage, and the iMac can't seem to find the printer since that time (even though Bonjour is working fine).
    I've tried resetting the Airport Express, and even upgrading the firmware, but no luck so far.
    I'll close this posting, and put a new one in the Airport Express Forum.
    many thanks to those who viewed this in the interim.
    LeslieB

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

  • 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

  • I have a iMac and i just updated the computer to Yosemite.  I have Photoshop CS5 and when I try to print under print size --- manage custom size , photoshop unexpectedly quits every time.  I updated the printer drivers (epson 9880)  uninstalled and instal

    I have a iMac and i just updated the computer to Yosemite.  I have Photoshop CS5 and when I try to print under print size --- manage custom size , photoshop unexpectedly quits every time.  I updated the printer drivers (epson 9880)  uninstalled and installed all the drivers. restarted computer and it is still doing the same thing.  Cant find any costumer service here either except forums.

    I have exactly the same problem - Whenever I go to Print, the print widow appears, it thinks about it for a bit (rotating symbol) and then quits.
    This is the beginning of the problem details, cut and paste. It goes on much longer than this:
    Process:               Adobe Photoshop CS5 [786]
    Path:                  /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/MacOS/Adobe Photoshop CS5
    Identifier:            com.adobe.Photoshop
    Version:               12.0 (12.0x20100407.r.1103] [12.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Photoshop CS5 [786]
    User ID:               502
    Date/Time:             2015-02-01 10:56:19.422 +0000
    OS Version:            Mac OS X 10.10.2 (14C109)
    Report Version:        11
    Anonymous UUID:        C0191A3D-714A-8117-8061-9291955759D1
    Sleep/Wake UUID:       B201F1B6-486D-4D70-B99A-E4F89B024BBF
    Time Awake Since Boot: 5600 seconds
    Time Since Wake:       240 seconds
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_ACCESS (SIGBUS)
    Exception Codes:       KERN_PROTECTION_FAILURE at 0x00007fff789d1e70
    VM Regions Near 0x7fff789d1e70:
        __DATA                 00007fff78986000-00007fff7898b000 [   20K] rw-/rwx SM=COW  /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Ve rsions/A/libLAPACK.dylib
    --> __DATA                 00007fff7898b000-00007fff789e1000 [  344K] rw-/rwx SM=COW  /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        __DATA                 00007fff789e1000-00007fff789e6000 [   20K] rw-/rwx SM=COW  /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   ???                           0x00007fff789d1e70 OBJC_CLASS_$_NSMutableArray + 0
    1   com.apple.print.framework.PrintCore 0x00007fff95693021 PMRelease + 43
    2   com.adobe.Photoshop           0x0000000100c237cf AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 9727123
    3   com.adobe.Photoshop           0x0000000100c23e7d AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 9728833
    4   com.adobe.Photoshop           0x0000000100c23eb7 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 9728891
    5   com.adobe.Photoshop           0x0000000100c23da5 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 9728617
    6   com.adobe.Photoshop           0x0000000100aee053 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 8459543
    7   com.adobe.Photoshop           0x0000000100768c64 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4768040
    8   com.adobe.Photoshop           0x0000000100af067e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 8469314
    9   com.adobe.Photoshop           0x0000000100af0be9 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 8470701
    10  com.adobe.Photoshop           0x0000000100af1295 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 8472409
    11  com.adobe.Photoshop           0x000000010007bbdc 0x100000000 + 506844
    12  com.adobe.Photoshop           0x00000001000d6a7e 0x100000000 + 879230
    13  com.adobe.Photoshop           0x00000001000d6a9e 0x100000000 + 879262
    14  com.adobe.Photoshop           0x0000000100066eb1 0x100000000 + 421553
    15  com.adobe.Photoshop           0x0000000100071d74 0x100000000 + 466292
    16  com.adobe.Photoshop           0x000000010006716f 0x100000000 + 422255
    17  com.adobe.Photoshop           0x0000000100067232 0x100000000 + 422450
    18  com.adobe.Photoshop           0x00000001012f0007 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16856267
    19  com.apple.AppKit               0x00007fff8d77c608 -[NSApplication run] + 711
    20  com.adobe.Photoshop           0x00000001012ee19c AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16848480
    21  com.adobe.Photoshop           0x00000001012ef3c7 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16853131
    22  com.adobe.Photoshop           0x0000000100068e82 0x100000000 + 429698
    23  com.adobe.Photoshop           0x0000000100238308 0x100000000 + 2327304
    24  com.adobe.Photoshop           0x00000001002383a7 0x100000000 + 2327463

Maybe you are looking for