Papercut - redirect large jobs

[ass17]

Hi all,

 

I have a papercut script that redirects large print jobs to another printer. It works to a printer ok but we what to redirect it to the virtual followme printer where it will hold the job for release. Problem is that when the print job is redirected to the FollowMe it doesn’t hold and sends it out to a random MFP that are selected as release stations for the FollowMe.

 

Is there a way to keep it head on redirection?

 

Thanks

[GaryPad]

Sounds like your redirect action isn't set to hold. You probably want it to hold and reprice too - something like this:

 

actions.job.redirect("Follow Me", {allowHoldAtTarget: true,recalculateCost: true});

[ass17]

Sounds like your redirect action isn't set to hold. You probably want it to hold and reprice too - something like this:

 

actions.job.redirect("Follow Me", {allowHoldAtTarget: true,recalculateCost: true});

 

Thanks, This is default in the script. Only a few minutes ago I had an email from Papercut support to say that it is an issue they are now investigating and a fix will come in time...

[GaryPad]

As a workaround until they do resolve it what you could try is add the LPD feature to the server (if it isn't already), create a new queue on that server (don't share it) using the same driver as your Follow Me queue, configured for Standard TCP/IP but use the server's own IP address, then (I'm assuming Windows here!), go into the Properties and switch the port protocol from RAW to LPR, set the queue name to be your "Follow Me" queue, tick the box to enable "LPR byte count", then change your redirect script to go to this new queue instead.

What should happen is the redirect script bounces jobs to the new queue which LPRs it over to the Follow Me and hopefully PaperCut will see this as a new job in the system and will hold it as normal.

 

Depending on the volume of jobs going this way, you might have to create a new DWORD registry key called:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\LPDSVC\lpr\UseNonRFCSourcePorts

And set this to 1 (there's more detail on why here).

[ass17]

As a workaround until they do resolve it what you could try is add the LPD feature to the server (if it isn't already), create a new queue on that server (don't share it) using the same driver as your Follow Me queue, configured for Standard TCP/IP but use the server's own IP address, then (I'm assuming Windows here!), go into the Properties and switch the port protocol from RAW to LPR, set the queue name to be your "Follow Me" queue, tick the box to enable "LPR byte count", then change your redirect script to go to this new queue instead.

What should happen is the redirect script bounces jobs to the new queue which LPRs it over to the Follow Me and hopefully PaperCut will see this as a new job in the system and will hold it as normal.

 

Depending on the volume of jobs going this way, you might have to create a new DWORD registry key called:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\LPDSVC\lpr\UseNonRFCSourcePorts

And set this to 1 (there's more detail on why here).

 

Great thanks!! [emoji1303]