You Want to Prevent Large Print Jobs From Displaying the Print Jobs on Nonart

"Help! Print jobs from our workstations don't actually print. What should we check?"

This is a bit of a mammoth article, but hopefully it gets you immediate help in figuring out 'where have my print jobs gone?'

This will take you through in-depth troubleshooting for scenarios where you or your users are pressing impress, but nil is coming out of the printer, and in that location are no jobs showing up for release when you log into the printer or release station.

Where does the job go missing?

The commencement step is to narrow down where in the press process the jobs are 'disappearing'. To do this, try pausing the impress queue on the server and endeavor to recreate the issue:

Pausing the print queue to diagnose issues with missing jobs

Log into the Windows print server.
Open up Print Management by pressing Windows key + R , then type printmanagement.msc and hitting the enter key.
Right-click on the printer and click 'Open Printer Queue'.
Click on 'Printer' in the menu bar and check 'Suspension Printing'.
Submit a print job that demonstrates the problem and enquire these questions.

          - Does the job at to the lowest degree prove upward?          - Does the Owner match the name of the          PaperCut          user?          - Is the status paused?

Then resume the job by unchecking 'Intermission Printing'.

          - Does the job disappear immediately, does information technology stay held in the queue, or was it never there in the starting time place?

Which behavior describes your issue the best?

If the job never reaches the print server or printer…
If the chore reaches the print server but then disappears from the queue…
If the task reaches the print server and is held in the queue, but the user sees nothing to release…
If the job reaches the impress server, the user tin can release the job, but nothing prints out…
If this just happens with Mobility Impress print jobs

The chore never reaches the print server or printer…

Is the impress job somehow bypassing PaperCut?

If the print chore isn't reaching the server at all, then check to come across how the printer connexion is set upwards.

It could be the case that the workstation is printing directly to a Bonjour-enabled printer, or direct to the IP accost of the printer. If this is the case, consider deleting this print queue and connecting to the print server instead. You can ensure this past having the user connect to a shared print queue on the impress server or by setting upwards PaperCut Mobility Print to share printers. If printing through the server is non desired, and then one selection is to install the PaperCut Direct Impress Monitor on the user's workstation so that these jobs can be tracked.

At a minimum nosotros need to make certain that the user is press to a queue that is monitored by PaperCut, and that print jobs prove upward in the PaperCut Job Log, otherwise at that place is not much for PaperCut to track.

Is this a Mac client and are they seeing the notorious 'hold for hallmark' fault?

Hold for authentication error shown in the printer queue

If you're seeing a 'hold for authentication' error in the print queue on the local macOS client, then accept a look through the Troubleshooting 'Concur for Hallmark' errors commodity.

Is the impress job coming from a Windows workstation that's not joined to the domain?

Nosotros've seen cases where the print queue was added on a Windows WORKGROUP computer, and so later the user'due south password expired or the account was disabled. When this happens, the print chore will never evidence upwardly in the Windows impress queue and will go cancelled without alarm. This situation would happen with or without PaperCut. Try deleting and re-add the printer with up-to-engagement credentials to see if that works.

Better yet, employ Mobility Print to share impress queues with WORKGROUP computers.

The job reaches the print server but and then disappears from the queue…

If the job shows up in the print queue on the server, only doesn't keep onto the printer or disappears earlier the user has the opportunity to release the job, so these are the things nosotros check for…

Is the Print Provider service running?

Commonly if this service is stopped, so impress jobs will be allowed to pass through your impress system (successfully printing) but non be tracked by PaperCut.

However, when Discover-Me Printing has been set up (usually with a nul port) and the Print Provider is not running, then the job 'prints' straight to the nul port, and finer disappears! This might happen if someone has stopped and started the Print Spooler, but has then forgotten to restart the Impress Provider service.

Double bank check this by heading into the Services console in Windows, and ensure the PaperCut Print Provider Service is started.

Is PaperCut configured in a mode that would cancel the jobs?

It's totally possible that PaperCut could exist configured (or misconfigured) in such a mode that print jobs are getting canceled. If this is the case, you tin can also see evidence of this in the Admin interface, under Logs → Awarding Log, where a message will land that the job was canceled due to policy.

Is the user business relationship Restricted and too out of rest?

A user with no credit

If the user account has a crimson 10 next to their name, then information technology means they are not allowed to print because they are out of credit. To set this, set the user business relationship to "unrestricted" or make sure the user has balance (at least enough for the cost of the test job).

Changing the user balance or restriction status

If this is the case, you tin also see evidence of this in the Application Log, under Logs → Awarding Log, in the Admin interface.

Is the printer in PaperCut configured to deny whatsoever jobs based on Filters & Restrictions?

Check the Filters & Restrictions tab, under Printers → [select a printer] → Filters and restrictions. Worth keeping an centre out, since these atmospheric condition nonetheless apply when troubleshooting BYOD solutions (Mobility Print, Google Deject Impress, Spider web Print, and Electronic mail to Print) but because these users might not be running the client, they won't see any pop up telling them why their job was canceled.

You lot should besides be able to meet evidence of this in the job log, under Logs → Job Log.

Is in that location a impress script enabled for this printer in PaperCut?

Check to see if in that location is a print script enabled on the print queue in question. Endeavour temporarily disabling the script to meet if this is causing the result. In the PaperCut admin interface, head over to Printers → [select printer] → Scripting, and so uncheck the Enable Impress Script checkbox. Relieve the settings, and try again.

Is On-Demand User Creation set up to 'Deny Usage'?

In a default PaperCut installation On-demand user creation is enabled so that print jobs from unknown users will be tracked. Even so, if this setting was inverse to "do not create the user and deny usage" then impress jobs from unknown users will exist deleted by PaperCut.

On-demand user settings set to not create users

Confirm how this setting is configured by logging into the Admin interface and navigate to Options → User/Group Sync → On Demand User Creation. Depending on your organization's needs, you may demand to reevaluate this setting or make sure the user business relationship gets imported or created in PaperCut.

Yous can besides see evidence of this in the Awarding Log, under Logs → Application Log, in the Admin interface.

Do you lot encounter an error message in the Application log with "A impress job was attempted to be unpaused while existence held and was deleted by the organisation"?

This means the chore has been 'resumed' outside of PaperCut's command. This is non a mutual issue, only if you come up beyond this message then accept a expect at this commodity on the 'attempted to exist unpaused' error.

The job reaches the print server and is held in the queue, but the user sees nothing to release…

Is the PaperCut Application Server waiting for the user to answer to a client Popup?

Certain PaperCut features like Account Option and Unauthenticated Printing require users to run the PaperCut Customer on their workstations to respond to pop-upward messages. This may exist to select an account to bill to or enter their credentials when prompted. A handy way to see if this is the issue is to wait x minutes subsequently printing the test task (I kid you non), and and then head into the PaperCut admin interface, and look at Logs → Application Log. Y'all'll see a warning something along the lines of "Canceling print chore ten printed by user because they did not answer to the customer popup within 10 minutes":

Application log showing a job that hasn't had a response from the user

If you lot see this error, and so try these steps:

Is the Account Selection popup enabled for the user, but they haven't seen the pop-up yet? To test, attempt changing the user settings to "automatically charge to personal account" (under Users → [select user] → Account Selection, in the PaperCut admin interface).
Is the user or printer configured for Unauthenticated Printing? If and so, then the workstation must be running the PaperCut client, and they must sign in when prompted. To confirm if that's the case, you'll need to cheque both the printer (Printers → [select printer] → Summary → Avant-garde Configuration → Unauthenticated printer (enable popup authentication)), and the user (Users → [select user] → Details → Advanced Options → Unauthenticated user (enable popup authentication)). Temporarily uncheck those options, salvage the setting, and re-examination if you're unsure.
Is Impress Scripting enabled on this printer, and is PaperCut waiting for the user to respond to a pop-upwardly? To test, try disabling the Impress Script (nether Printers → [select printer] → Scripting → uncheck Enable Print Script).

If the job then works when you modify / disable these settings, and so that's cracking!! Adjacent step is to brand sure the PaperCut Customer is installed and working. To test, ship a customer notification popup and make sure this is seen by the user. Hop over to the Client popup and Notification Problems Troubleshooting page if you're after assist with that.

Does the PaperCut username lucifer the user that submitted the job?

If the print task arrived at the print server, but doesn't appear when the user signs into the Release Station or MFD then there could be a couple things going wrong. Nosotros run across this happen occasionally when the owner of the impress task doesn't friction match the user doing the releasing.

Wait for the held impress job in the PaperCut Admin interface under Printers → Jobs Awaiting Release.

Does the username match what you would wait? If "Tim" printed the document, but PaperCut thinks the job was printed by "SYSTEM" then see our Troubleshooting jobs attributed to the wrong user or wrong owner name commodity. We run into this happen occasionally when users print through a 3rd party service like Google Cloud Impress, Presto, or some server. We also encounter this happen if the users are badging in with the wrong card, or the carte is incorrectly associated with the wrong user. Rule out this scenario by having users log in with username/password instead of ID badge.

The print task has been temporarily hidden from the Print Release screen

This occurs when a user attempts to release their impress task, but the Print Provider which is tracking the chore is no longer able to contact the app server. This beliefs was introduced as a security enhancement to prevent a scenario when print jobs are inadvertently released later on the user walks away from an MFP when the Print Provider and the PaperCut server are not able to communicate.

To ostend if this is what is happening in your surroundings, take a look at the Application Log, under Logs → Application Log.

If you lot've found this issue happening in your environment, in that location's some in-depth information about this over on the Print Job Temporarily Hidden commodity.

Is this user configured as a release managing director, only the user that submitted the chore has business relationship choice enabled?

PaperCut might withhold a print chore from the Release screen because a user has account selection enabled, is waiting for an business relationship selection pop-upwards, or other reasons discussed above in this article. If you lot are troubleshooting a problem with "delegated impress release" or "Agree/Release queue manager" in PaperCut, endeavor turning this setting off and ensure that the task tin first be seen at the release station interface (or the Mobile Release page http://your-server-proper name:9191/mobile/release) before adding this actress layer of complexity.

Is this user configured as a release manager, merely is trying to release their own job?

Currently if a user who is configured as a Release Managing director logs in to release a job through the release station or release manager interface (at http://yourserver:9191/release), they'll only see the jobs that they have permission to release with their release-director hat on. Have the impress release director open the browser and sign into the user spider web interface (at http://yourserver:9191/user) to see and release their own print jobs.

For case in the case below, Alice is a release managing director, and has printed a job. Tim has also printed a chore. Alice only has permissions to release jobs grouping people in the 'students' group, and 'Tim' is a member of the students group. Alice is a member of the staff group. With the states so far?

This is what an admin sees when logging into the Admin interface, and checking nether the Printers → Jobs Awaiting Release tab:

Admin view of jobs pending release

Since Alice has been configured every bit a release manager, when she logs into the /release interface, information technology will just show jobs from users in the 'students' group - in this example, Tim - so she isn't able to see her own job:

Release manager view of jobs pending release

To release her own job, she should log into the /user URL as her, to be able to release her own job.

The task reaches the print server, the user can release the job, just nothing prints out…

Does this merely happen when printing to a Find-Me queue?

Sometimes the problem is just with Notice-Me Printing specifically, but impress jobs sent to other queues piece of work just fine? To confirm, effort press straight to a "target" print queue on the same print server instead of the "Find-Me" print queue.

Does the chore go straight through? If so this might be an issue with the way that Find-Me Printing is configured. Have a look at our commodity on Troubleshooting Find Me Printing for the adjacent steps.

Is the print driver configured to require a PIN or other Authentication?

Some manufacturer's impress drivers can exist configured to bear witness an authentication prompt for a user or department Pivot. Xerox Pull/Print is one example, only Konica Minolta, Toshiba, Precipitous and others may as well have this feature. Ostend whether this is the case past printing a exam page from the Windows print server. Is there an authentication prompt from the driver? If and then, disable this setting (normally found in the Device Settings tab in Printer Properties on the Windows print queue).

For instance, Konica Minolta drivers can too behave by not request for authentication and the job volition just exist canceled. You lot can see the auth settings hither in the print driver defaults:

KM Driver setting for authentication within the driver - switch this off!

In another example, for Sharp devices, make sure User Hallmark is not enabled in Printing Defaults. When this is incorrectly enabled, customers may study a 042F Mistake in the log on the Sharp copier. There'due south more than information in the Known Issue for 042F errors article, along with a screenshot of the setting in the Printing Defaults.

Does this simply happen when printing from Windows 10 apps like Edge, and are you using driver authentication?

When this happens nosotros hear about print jobs getting stuck. We describe this scenario and the workaround in our article Jobs stuck with the status of 'Printing'.

Is the print queue set to utilize the PaperCut TCP/IP port instead of a Standard TCP/IP port?

If the printer is in an fault state, and so this may forbid the side by side job from being sent to a impress queue. If y'all're not explicitly wanting to utilise hardware validation/checking, then use a Standard TCP/IP Port and don't apply the PaperCut TCP/IP port, unless it is absolutely necessary. This will slow down printing past design equally PaperCut will wait until the printer reports that the terminal job was printed earlier sending the side by side one. In that location's more information about the affect of Hardware Checking on printing speed.

Does the trouble but happen when printing from macOS to a Windows Print Server?

If you're printing from macOS to a Windows server, with Blazon-4 or XPS-enabled drivers, then the job will non become through - this is really the case fifty-fifty without PaperCut running. For more of the gory details behind this, bank check out Windows and Type four Drivers.

Still have questions?

Let usa know! We dear chatting about what'southward going on under the hood. Experience free to leave a comment below or visit our Support Portal for further aid.

Categories: Troubleshooting Articles, Print Jobs, Impress Queues

Keywords: missing, disappearing, impress jobs gone, no print task, no impress out

storyandence.blogspot.com

Source: https://www.papercut.com/kb/Main/MissingOrDisappearingPrintJobs