If we download the driver, it may be different from the one you are using and as a result, we might not be able to get the same results. Link to download the driver: As drivers are often regional, we ask for the download link.We’ll need to know, if not already known: On top of that, if we can get the following bits together, we can likely provide a result promptly as opposed to having to go back-and-forth. Get them switched on and wait for the problem to manifest itself again. How to enable debug in the print providerĮnable those options and send some print jobs that will have the issue.īoth sets of logs will provide useful information for us to troubleshoot any odd or intermittent issues. The two places to enable debug are the PaperCut Application Server and PaperCut Print Provider. We need you to enable debugging in two places and perform some testing that highlights the issue. Man, you are in for a treat! We need some logs and some data (or just data – depends on how you say it!). No luck or not wanting to try a different driver? In all honesty, if you can recreate the issue on your setup using the latest code, then send us the driver download link, and we will do the rest. Using a driver like the PaperCut PS driver, is also another good idea, does that work? If so, you know it should work (if it works on one driver, why not your one?). ![]() In fact, try a completely different driver – you don’t need to waste paper, get it held by PaperCut using a Nul port and see if PaperCut detects everything correctly once printed to the Nul port. This way, you can see if one of the new options prints as expected and PaperCut detects everything correctly. However, if the existing driver has specific functionality that the other drives are missing (we know you like your finishing options), then consider installing 2-3 test queues with different drivers. Life is short, maybe an older/newer/universal driver will work, and we can all move on. Click Modify on the Papercut Mobility DNS TCP Virtual Service. Click View/Modify Services in the left-hand navigation. Is the driver causing your PaperCut Print Analysis issue? Select the Papercut Mobility DNS template in the Use Template drop-down list. We mention this because a B&W document detected as being in colour comes up a lot, and it’s because the image contains some form of colour and is not actually greyscale. Now, you could “re-colour” your proper image in Word and set it to grayscale – that may help. If you check the properties, you will see the low bit depth. …add that to a new Word document and print it, we bet that it’s detected as greyscale. You can go further to test this by grabbing a sample greyscale Tiff file from here. Did PaperCut detect the job correctly? If it did, that means the image you were using is causing the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |