Tim_at_PaperCut

Hi mikkydoos! I wish I had a definite answer for this one, but as you mentioned, it seems like it might be related to the driver in use. I did dig through our ticket history but I don't see any symptoms like this for the Sharp devices - or any devices for that matter : ) What I'd suggest may be something that you've already tried - definitely worth setting up a brand new queue on your print server, and apply the Sharp generic driver, then check to see if that works or not. We've sometimes seen issues where drivers get updated on the current queue, and old settings stay in the registry, ultimately corrupting the driver. So creating a brand new queue will rule that issue out. Next up I would try using either an older (or newer if it exists) version of the Sharp generic driver, to see if that makes a difference. If they supply different 'flavours' of the driver that would be worth a try too - for example try using a Postscript driver instead. Finally it might be worth seeing if there is an 'Advanced Printing Options' checkbox in the driver properties (on the advanced tab normally) and unchecking that, then testing to see if that makes any difference too. Sorry that I don't have more concrete answers for that one!

Hi Amila, That's perfect - thank you for that! The ticket was escalated through to one of our top spool-file-analyzing developers yesterday, so hopefully we'll have some news on that issue shortly!

Hi Grumon, It sounds like the driver in that case isn't producing a spool file that we're able to read for some reason. Sometimes that's a fault with the driver, and sometimes that's a fault with us! Either way, we should be able to find a way around it. I dug through the ticket system and I found a very similar issue which is currently being looked at by the dev team, but there's not a way of confirming if that's you or not : ) Would you either be able to let us know the user name that you sent the ticket in as, or give us the ticket number, or if you'd prefer not to post publicly, can you send another support ticket in to our email address, and let us have the ticket number that you're following up on? We'd love to get to the root cause of the issue so that we can see if we can fix the issue that you're seeing! Thanks!

Just to echo what's been said above - looks like everyone has covered the main points - we have customers who use both methods (3rd party tool to broadcast the Windows print queues, or instead use a Mac secondary server). Some go the mac-mini route since they have a spare Mac lying around, so they can just re-use it for a secondary server (nice situation to be in!) and others are Windows-only environments, so they prefer the simplicity of Presto. I haven't heard of the issue with Presto needing to be restarted, but if you are using the free trial and you come across that, I'd definitely bring that up with the Presto support team, it's not something I've heard of from other customers - but I imagine they'd want to hear about it! It should also be possible to get the find-me/follow-me queues working with the Mac secondary - there's a few more details about it here: PaperCut KB | Setup Find-Me Printing on Multiple Operating Systems - but in short, since you can't re-direct jobs cross-platform, you'd have to set up the find-me Mac queue, and create the target queues on the Mac too, so that the jobs can go Workstation/iPad -> Mac find me queue -> Mac target queue. With that setup, you can keep all your find-me functionality of your current queues. If you're seeing issues with that setup though, definitely worth sending in an email to PaperCut, and we'll help out with your specific scenario if you prefer!

Hi Craig, Hm. Good question... the issue is that the installer from the older versions of PaperCut on Mac OS 10.10 doesn't quite do what it's supposed to do, so there's a bunch of files missing and some that don't pick up permissions correctly. Ideally, the preferred method is to convince your copier provider to help you upgrade to 14.3 - that will sort all the issues out, and you'll be guaranteed a working environment : ) If you're having issues with that route though, please feel free to email the sales team here: Contact Us - PaperCut if you're getting the run-around on the licensing side of things - our sales team will see if they can help smooth things along. Otherwise, the other way around this is to fix things manually, which is a little murky, but should work: 1. You'll need to install 13.5 onto a spare Mac which is Mac OS 10.9, so that it installs fully - you'll then use that as your file source. Or alternatively it should be possible to install e.g. the trial version of NG 14.3 onto a test Mac, since the files that we'll be copying shouldn't be different between the versions. You basically want to get a test machine on Mac with PaperCut installed successfully, so that you can copy the working files over to your current server. 2. In Terminal navigate to: [install directory]/providers/iosprint/mac/pc-iosprint on your current server e.g: cd /Applications/PaperCut\ MF/providers/iosprint/mac/ 3. Type: sudo chmod oug+x * To add 'execute' permissions to the files in that folder (currently the execute permissions will be missing, which means that iosprint won't be able to launch) 4. Copy /Library/LaunchDaemons/papercut-iosprint.plist from your test machine installation, over to the same location on your current server. 5. Make sure that it's owned by root - so change directory to that directory: cd /Library/LaunchDaemons/ Then change the ownership: sudo chown root papercut-iosprint.plist 6. Then you should be able to start the iosprint advertiser - run the following .command file: [install directory]/providers/iosprint/mac/start-iosprint.command You should then see a terminal window popup, and it'll try to start the iosprint advertiser, after asking for your password. You should then see a message saying: iOS printing started If that all makes sense, then you can give that a go - otherwise the preferred option is to be hassle-free and upgrade to 14.3 If you run into issues with the above, then please feel free to reach out to us by email via Contact Us - PaperCut - that will then generate a ticket, and we can dig into the nitty gritty! Thanks, and hope it goes well! Tim

@pete, thanks! Yep, will get this added. We basically need a 'handler' which uses the API for Office (in the case of Office docs) to do the equivalent of opening up the document and pressing print, but it actually does it at an API level - so it's not identical to how a user would print the document. This also has other implications - for example if you install e.g. Word Viewer on the web print sandbox, the handler won't work because it needs the Office APIs only available with the full Word/Office install. Hopefully we can build out additional handlers for other file-types, and I'll add your notes above too, to see if there's a way that we can auto-handle new filetypes if there's an app on the machine that can handle that particular filetype. No harm in asking : )

Hi Pete, You're absolutely correct unfortunately - in terms of formats supported in Web Print, the full list is shown here: Web Print (Driver-less printing via a web browser) but at the moment LibreOffice formats aren't supported. Things are always work-in-progress however, so I've added a 'vote' to our internal ticket for looking into the possibility of supporting those formats (as well as e.g. .png / .gif / .jpg etc) in a future version of PaperCut. Sorry that there's not a more immediate workaround for that!

Hi Adam, I'm new to Edugeek, and feeling green with this first post Anyway, if you're using the built-in hold/release functionality of PaperCut, then as Roberto mentioned, you can definitely apply conversions or scripts to change the job to grayscale/duplex. There isn't a way to convert jobs to simplex, but hopefully if the users sent the job as duplex in the first place, that means they're doing the right thing! In terms of releasing the job once it's been held in a hold/release queue, you can either use the Release Station software on an old PC, exactly as you mentioned, or you can also let the users release jobs through the other methods available (mentioned here: Hold/Release Usage Scenarios ) - for example the user web release page, or even the mobile release page (users can walk up to the device and release the job from their phone). Otherwise if you're using an MFP which is able to be embedded with PaperCut running on the device, then you can always use the device-based release through the embedded PaperCut app. Hope that helps - otherwise, feel free to reach out to us directly if you'd prefer - Contact Us - PaperCut - we'll help however we can!