Attempted to be Unpaused

KB Home   |   Attempted to be Unpaused

Main.AttemptedToBeUnpaused History

Hide minor edits - Show changes to output

July 30, 2018, at 11:09 PM by Aaron Pouliot - Fixed with input from Alan
Changed line 15 from:
This may happen if you are printing to a Windows print queue using Legacy Windows LPD (which could be the case if you are printing from macOS workstations or an older system like [=AS400=]).  For customers with PaperCut version 15.1 and above, replace Windows LPD service with the [[https://www.papercut.com/kb/Main/PaperCutLPDService|PaperCut LPD Service]] which is fully supported. 
to:
This may happen if you are printing to a Windows print queue using the [[https://www.papercut.com/kb/Main/LPROnWindows|Windows LPD Service]] which is sometimes the case when printing from an older system like [=AS400=].  For customers with PaperCut version 15.1 and above, replace Windows LPD service with the [[https://www.papercut.com/kb/Main/PaperCutLPDService|PaperCut LPD Service]] which is fully supported. 
July 30, 2018, at 10:20 PM by alan morris - a couple of edits
Changed line 15 from:
This may happen if you are printing to a Windows print queue using using the Legacy Windows LPR (which could be the case if you are printing from macOS workstations or an older system like [=AS400=]).  For customers with PaperCut version 15.1 and above, replace Windows LPR with the [[https://www.papercut.com/kb/Main/PaperCutLPDService|PaperCut LPD Service]] which is fully supported. 
to:
This may happen if you are printing to a Windows print queue using Legacy Windows LPD (which could be the case if you are printing from macOS workstations or an older system like [=AS400=]).  For customers with PaperCut version 15.1 and above, replace Windows LPD service with the [[https://www.papercut.com/kb/Main/PaperCutLPDService|PaperCut LPD Service]] which is fully supported. 
July 30, 2018, at 08:53 PM by Aaron Pouliot - Edited article with input from Alan
Changed line 15 from:
This may happen if you are printing to a Windows print queue using using the Legacy Windows LPR (which could be the case if you are printing from macOS workstations or an older system like [=AS400=]).  For customers with PaperCut version 15.1 and above, replace Windows LPR with the [[https://www.papercut.com/kb/Main/PaperCutLPDService|PaperCut LPD]] Service which is fully supported. 
to:
This may happen if you are printing to a Windows print queue using using the Legacy Windows LPR (which could be the case if you are printing from macOS workstations or an older system like [=AS400=]).  For customers with PaperCut version 15.1 and above, replace Windows LPR with the [[https://www.papercut.com/kb/Main/PaperCutLPDService|PaperCut LPD Service]] which is fully supported. 
July 30, 2018, at 08:53 PM by Aaron Pouliot - Edited article with input from Alan
Changed line 15 from:
This may happen if you are printing to a Windows print queue using using the Legacy Windows LPR (which could be the case if you are printing from macOS workstations or an older system like AS400).  For customers with PaperCut version 15.1 and above, replace Windows LPR with the PaperCut LPD Service which is fully supported. 
to:
This may happen if you are printing to a Windows print queue using using the Legacy Windows LPR (which could be the case if you are printing from macOS workstations or an older system like [=AS400=]).  For customers with PaperCut version 15.1 and above, replace Windows LPR with the [[https://www.papercut.com/kb/Main/PaperCutLPDService|PaperCut LPD]] Service which is fully supported. 
July 30, 2018, at 08:52 PM by Aaron Pouliot - Updated article with input from Alan
Changed lines 3-13 from:
Q: In the logs I see an error message that says "A print job was attempted to be unpaused while being held and was deleted by the system".  What do I do?

A: This error occurs when
PaperCut detects that a print job was deleted from the Windows Print Spooler by an unknown process.  This can occur for a broad number of reasons which we have tried to document below.

A: If you suspect that end-users are cancelling or resuming held print jobs on their own,
then make sure that the  [[PrintQueueSetUpOnWindows | Windows Print Queue Permissions]] have been configured. 

A: If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may
occur because the [[LPROnWindows | Legacy Windows LPR]] service is in use.  For customers with PaperCut version 15.1 and above, replace Windows LPD with the [[PaperCutLPDService | PaperCut LPD Service ]].
 
A: Occasionally we see this occur when there a 3rd party software program with the ability to manage the Windows Print queue like Printer Logic or Print Audit 6. Please
make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.  It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application as a test to see if it resolves the issue.

A: Alternatively, if you have McAfee HDLP (Host Data Loss Protection) set up on your network, we have seen issues with it causing this error - symptoms include jobs being printed successfully but not being logged, and the account in question not being debited. To test to see if this is
the root cause, disable HDLP, and re-test.
to:
''"Help! In the logs I see an error message that says “A print job was attempted to be unpaused while being held and was deleted by the system”. What does this mean?"''

When a user prints a document
PaperCut will pause the print job temporarily for analysis, or may hold the print job for longer if Hold/Release is enabled.  This error message may be logged if  PaperCut detects that a print job was released outside of it's control by another process.  The PaperCut server may then attempt to delete the print job before it finishes processing, hence the enigmatic error message: “A print job was attempted to be unpaused while being held and was deleted by the system”.

This can
occur for a few different reasons which we have tried to document below.

!! Are end users manually trying to resume their job?
If you suspect that end users are cancelling or resuming held print jobs on their own, then try configuring security on the Windows Print Queue to remove “Manage Documents” rights from the Creator/Owner user.  Note that there’s no need to
make this change on a Find-Me print queue, as the job will be “printed” to the nul port anyway and will simply disappear.

Attach:Security_Tab.png

!! Is the printing happening through the Windows LPR/LPD service?
This may happen if you are printing
to a Windows print queue using using the Legacy Windows LPR (which could be the case if you are printing from macOS workstations or an older system like AS400).  For customers with PaperCut version 15.1 and above, replace Windows LPR with the PaperCut LPD Service which is fully supported. 

!! Is another print management app interfering?
Occasionally we see this occur when there a 3rd party software programs with the ability to manage
the Windows Print queue like Printer Logic or Print Audit 6. Please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours. It may also be the case that this application could conflict with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application as a test to see if it resolves the issue.

!! Is Data Loss Protection software canceling print jobs?
We have heard of other scenarios where customers had Host Data Loss Protection software like McAfee HDLP. In this case, the symptoms would include jobs being printed successfully but not being logged, and the account in question not being debited. To test to see if this is the root cause, disable HDLP, and re-test.

!! Still have questions?
Let us know! We love chatting about what’s going on under the hood. Feel free to leave a comment below or visit our [[https://support.papercut.com|Support Portal]] for further assistance
.
February 19, 2018, at 07:14 AM by jamesv - fixed a non-required link
Changed line 11 from:
A: Occasionally we see this occur when there a 3rd party software program with the ability to manage the Windows Print queue like PrinterLogic or Print Audit 6. Please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.  It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application as a test to see if it resolves the issue.
to:
A: Occasionally we see this occur when there a 3rd party software program with the ability to manage the Windows Print queue like Printer Logic or Print Audit 6. Please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.  It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application as a test to see if it resolves the issue.
November 22, 2017, at 07:37 PM by Aaron Pouliot -
Changed line 9 from:
A: If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may occur because the [[LPROnWindows | Legacy Windows LPR]] service is in use.  For customers with PaperCut version 15.1, replace Windows LPD with the [[PaperCutLPDService | PaperCut LPD Service ]].
to:
A: If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may occur because the [[LPROnWindows | Legacy Windows LPR]] service is in use.  For customers with PaperCut version 15.1 and above, replace Windows LPD with the [[PaperCutLPDService | PaperCut LPD Service ]].
November 22, 2017, at 07:36 PM by Aaron Pouliot - added hyperlinks and edited for clarity
Changed lines 3-11 from:
Q: I've got the message "A print job was attempted to be unpaused while being held and was deleted".  What do I do?

A: This error message essentially means that PaperCut detected that a print job was deleted from the Windows Print Spooler by an unknown process.

A: If you suspect that end-users are cancelling the jobs themselves, then make sure that the driver permission settings are configured as outlined here: https
://www.papercut.com/kb/Main/PrintQueueSetUpOnWindows

A:
If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may be related to this: https://www.papercut.com/kb/Main/LPROnWindows.  For customers with PaperCut version 15.1, replace the Windows LPD service with the PaperCut LPD Service.  https://www.papercut.com/kb/Main/PaperCutLPDService

A: Alternatively, if you have McAfee HDLP (Host Data Loss Protection) set up on your network, we have seen issues with it causing this error - symptoms include jobs being printed successfully but not being logged, and the account in question not being debited. To test to see if this is the root cause, disable HDLP, and re-test
.
to:
Q: In the logs I see an error message that says "A print job was attempted to be unpaused while being held and was deleted by the system".  What do I do?

A: This error occurs when PaperCut detects that a print job was deleted from the Windows Print Spooler by an unknown process.  This can occur for a broad number of reasons which we have tried to document below.

A
: If you suspect that end-users are cancelling or resuming held print jobs on their own, then make sure that the  [[PrintQueueSetUpOnWindows | Windows Print Queue Permissions]] have been configured.  

A: If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may occur because the [[LPROnWindows | Legacy Windows LPR]] service is in use.  For customers with PaperCut version 15.1, replace Windows LPD with the [[PaperCutLPDService | PaperCut LPD Service ]]
.
Changed lines 11-13 from:
A: Check to see if there is a 3rd party software program with the ability to manage the Windows Print queue like PrinterLogic or Print Audit 6. Then please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours. It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application to see if it resolves the issue.
to:
A: Occasionally we see this occur when there a 3rd party software program with the ability to manage the Windows Print queue like PrinterLogic or Print Audit 6. Please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.  It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application as a test to see if it resolves the issue.

A: Alternatively, if you have McAfee HDLP (Host Data Loss Protection) set up on your network, we have seen issues with it causing this error - symptoms include jobs being printed successfully but not being logged, and the account in question not being debited. To test to see if this is the root cause, disable HDLP, and re-test.
November 22, 2017, at 12:47 AM by Aaron Pouliot -
Changed lines 13-14 from:
A: If you are using another software program with the ability to manage the Windows Print queue like PrinterLogic
 or Print Audit 6. Please
make sure that you have not configured this program to purge active or held print jobs after a certain number of hours. It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application to see if it resolves the issue.
to:
A: Check to see if there is a 3rd party software program with the ability to manage the Windows Print queue like PrinterLogic or Print Audit 6. Then please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours. It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application to see if it resolves the issue.
November 22, 2017, at 12:46 AM by Aaron Pouliot -
Changed lines 13-14 from:
A: If you are using another software program with the ability to manage the Windows Print queue like PrinterLogic then please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.
to:
A: If you are using another software program with the ability to manage the Windows Print queue like PrinterLogic
 or Print Audit 6. Please make sure that you have not configured this program to purge active or held print jobs after a certain number of
hours. It may also be the case that this application could conflict  with PaperCut as both applications try to manage print jobs in the queue, so try disabling the application to see if it resolves the issue.
November 08, 2017, at 12:24 AM by Aaron Pouliot -
Changed line 13 from:
A: If you are using another software program with the ability to manage the Windows Print queue like PrinterLogic, please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.
to:
A: If you are using another software program with the ability to manage the Windows Print queue like PrinterLogic then please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.
November 08, 2017, at 12:24 AM by Aaron Pouliot - Added note about PrinterLogic
Changed lines 5-6 from:
A: Make sure that the driver permission settings are configured as outlined here: https://www.papercut.com/kb/Main/PrintQueueSetUpOnWindows
to:
A: This error message essentially means that PaperCut detected that a print job was deleted from the Windows Print Spooler by an unknown process.

A: If you suspect that end-users are cancelling the jobs themselves, then make
sure that the driver permission settings are configured as outlined here: https://www.papercut.com/kb/Main/PrintQueueSetUpOnWindows
Added line 13:
A: If you are using another software program with the ability to manage the Windows Print queue like PrinterLogic, please make sure that you have not configured this program to purge active or held print jobs after a certain number of hours.
June 11, 2015, at 09:05 PM by 71.236.214.84 -
Changed lines 7-8 from:
A: If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may be related to this: https://www.papercut.com/kb/Main/LPROnWindows
to:
A: If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may be related to this: https://www.papercut.com/kb/Main/LPROnWindows.  For customers with PaperCut version 15.1, replace the Windows LPD service with the PaperCut LPD Service.  https://www.papercut.com/kb/Main/PaperCutLPDService
Changed line 9 from:
A: Alternatively, if you have McAfee HDLP (Host Data Loss Protection) set up on your network, we have seen issues with it causing this error - symptoms include jobs being printed successfully but not being logged, and the account in question are not debited. To test to see if this is the root cause, disable HDLP, and re-test.
to:
A: Alternatively, if you have McAfee HDLP (Host Data Loss Protection) set up on your network, we have seen issues with it causing this error - symptoms include jobs being printed successfully but not being logged, and the account in question not being debited. To test to see if this is the root cause, disable HDLP, and re-test.
September 24, 2013, at 07:36 PM by timg - Added HDLP known issue
Added lines 9-11:
A: Alternatively, if you have McAfee HDLP (Host Data Loss Protection) set up on your network, we have seen issues with it causing this error - symptoms include jobs being printed successfully but not being logged, and the account in question are not debited. To test to see if this is the root cause, disable HDLP, and re-test.
 

Changed line 12 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: LPR, print queue, unpaused-]
Changed lines 1-2 from:
(:title TODO Page Title:)
to:
(:title Attempted to be Unpaused:)
Added lines 1-12:
(:title TODO Page Title:)

Q: I've got the message "A print job was attempted to be unpaused while being held and was deleted".  What do I do?

A: Make sure that the driver permission settings are configured as outlined here: https://www.papercut.com/kb/Main/PrintQueueSetUpOnWindows

A: If you are seeing these issues when printing from Mac workstations to a Windows print queue, it may be related to this: https://www.papercut.com/kb/Main/LPROnWindows

----
''Categories:'' [[Category.Troubleshooting|+]]
----
[-Keywords: TODO keywords here if needed-]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on July 30, 2018, at 11:09 PM
Printable View   |   Article History   |   Edit Article