Papercut client unreliable

[bondbill2k2]

We've been having on and off issues now for a good couple of months regarding Papercut. Users who get charged directly to a single department are fine but those required to select which department for the job on the Papercut popup have been struggling.

 

The papercut client is ran from the print server at login, we even have a delayed login script checking if its running then launching it again if required. Some users will print fine then half an hour later be unable to, papercut will stop popping up for the department selection but still show as running in the task bar. Some times the pcclient.exe will of stopped running other times its still running but needs to be killed and relaunched in order to resume regular printing. Event logs show no clues and running papercut in debug mode doesn't help as the logs just stop with no unusual activity or errors.

 

We are running Version: 17.4.4 (Build 42562) with the zero-install method. We have some users which kept having the issue running the client locally installed, these still get the same issue.

[fiza]

Has it only become an issue since you upgraded? We are on Papercut MF 17.2.3 and run it exactly the same way with no issues.

Worth upgrading to version 18?

[mthomas08]

We are on 17.2.2 and no issues. Our plan is to upgrade during next half term.

[FN-GM]

In the server share where pcclient.exe lives, there is a version named something like pcclient_local_cache.exe this works much better. For us it solved the problem you describe.

 

It also makes the Windows 10 notifications work properly.

Edited March 7, 2018 by FN-GM

[MatthewL]

FYI PaperCut MF 18.0.4 is now available. I would always recommend running the client locally rather than from a share.

[mullet_man]

FYI PaperCut MF 18.0.4 is now available. I would always recommend running the client locally rather than from a share.

 

We run it locally - deployed with SCCM and have no issues, had the odd teacher laptop not running the client when trying to print but that’s very rare.

[newpersn]

In the server share where pcclient.exe lives, there is a version named something like pcclient_local_cache.exe this works much better. For us it solved the problem you describe.

 

It also makes the Windows 10 notifications work properly.

 

+1

 

Swapped to this when i rewrote our group policy. Not had a problem since.

[PotNoodleTech]

When run directly from the server the client won't tolerate disconnection and will not recover if it becomes disconnected. I've only noticed this very occasionally if there has been a power cut in a room or building for example, users need to log off and back on to reconnect the client. in daily use on hundreds of PCs I don't have an issue with the client.

 

It could actually be letting you know you have some site wide network issue of some sort which is disconnecting the client, or it could be a server issue if the server is becoming disconnected from the network temporarily. If your network is reliable and your server is reliable, the client is reliable.

[tech-man]

We deploy it to computers via the MSI, never had an issue.

[Big_Ted]

enable debug in the client as per:

https://www.papercut.com/kb/Main/HowToEnableDebugInTheUserClient/

 

wait for it to happen

collect logs

record time/date it happened (and what happened)

send logs to support

[ricki]

I had a similar problem a long while ago and had to use the latest paper cut client and that fixed it Richard

[chrisakak9]

I know this is an old thread but if you are having this issue i have created a script that will check for the papercut client running and restart it if not.

 

Read my post herehttp://www.edugeek.net/forums/educational-software/210259-papercut-client-randomy-closing-heres-fix-you.html#post1796158