Find Me Printing "Error 32"

KB Home   |   Find Me Printing "Error 32"

Main.FindMePrintError32 History

Hide minor edits - Show changes to output

July 05, 2018, at 06:36 PM by Aaron Pouliot - Added category FindMePrinting
Added line 13:
Changed line 15 from:
''Categories:'' [[Category.Error | +]]
to:
''Categories:'' [[Category.FindMePrinting|+]], [[Category.Error |+]]
Changed lines 7-13 from:
This is usually an indication that a process other than [=PaperCut=] has an exclusive file lock on the print spool files. This can be caused by Anti-virus, backup or more even more customer-unique software.

To better determine where the issue lies some of our customers have reported success by using [=SysInternals=] (http://technet.microsoft.com/en-us/sysinternals/default.aspx) “Process Monitor”. This application is able to monitor a Windows Server and see what processes are accessing what resources. Once known steps can be taken to resolve this issue.

When monitoring file access it is best to filter the events to only include the Print Spooler directory, traditionally C:\Windows\System32\Spool\. Please also note that this kind of monitoring may have a impact on system performance.

[-keywords: find me, error 32, redirect -]
to:
This is usually an indication that a process other than PaperCut has an exclusive file lock on the print spool files. This can be caused by Anti-virus, backup or more even more customer-unique software.

To better determine where the issue lies some of our customers have reported success by using `SysInternals (http://technet.microsoft.com/en-us/sysinternals/default.aspx) “Process Monitor”. This application is able to monitor a Windows Server and see what processes are accessing what resources. Once known steps can be taken to resolve this issue.

When monitoring file access it is best to filter the events to only include the Print Spooler directory, by default C:\Windows\System32\Spool\. Please also note that this kind of monitoring may have a impact on system performance.
Changed lines 14-16 from:
''Categories:'' [[Category.Error | +]]
to:
''Categories:'' [[Category.Error | +]]
----
[-Keywords: find me, error 32, redirect-
]
Added lines 12-15:

[-keywords: find me, error 32, redirect -]
----
''Categories:'' [[Category.Error | +]]
Changed lines 7-10 from:
This is usually an indication that a process other than !PaperCut has an exclusive file lock on the print spool files. This can be caused by Anti-virus, backup or more even more customer-unique software.

To better determine where the issue lies some of our customers have reported success by using !SysInternals (http://technet.microsoft.com/en-us/sysinternals/default.aspx) “Process Monitor”. This application is able to monitor a Windows Server and see what processes are accessing what resources. Once known steps can be taken to resolve this issue.
to:
This is usually an indication that a process other than [=PaperCut=] has an exclusive file lock on the print spool files. This can be caused by Anti-virus, backup or more even more customer-unique software.

To better determine where the issue lies some of our customers have reported success by using [=SysInternals=] (http://technet.microsoft.com/en-us/sysinternals/default.aspx) “Process Monitor”. This application is able to monitor a Windows Server and see what processes are accessing what resources. Once known steps can be taken to resolve this issue.
Added lines 1-11:
(:title Find Me Printing "Error 32" :)

Occasionally customers report that Find Me Print jobs are failing with the below error message.

@@Mar 23 11:43:29 ERROR: Unable to open spool file for redirect. - The process cannot access the file because it is being used by another process. (Error: 32)@@

This is usually an indication that a process other than !PaperCut has an exclusive file lock on the print spool files. This can be caused by Anti-virus, backup or more even more customer-unique software.

To better determine where the issue lies some of our customers have reported success by using !SysInternals (http://technet.microsoft.com/en-us/sysinternals/default.aspx) “Process Monitor”. This application is able to monitor a Windows Server and see what processes are accessing what resources. Once known steps can be taken to resolve this issue.

When monitoring file access it is best to filter the events to only include the Print Spooler directory, traditionally C:\Windows\System32\Spool\. Please also note that this kind of monitoring may have a impact on system performance.

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 05, 2018, at 06:36 PM
Printable View   |   Article History   |   Edit Article