Papercut 19.0

[siuko]

I had that issue when setting up the local cache version on PaperCut MF 18.3.2

 

I don't know if it was due to us preventing access on C drive

 

The fix was as follows

 

Machine based startup script that creates a cache folder on c drive and gives it permissions

 

if exist "C:\PapercutCacheDirectory" goto SetPermissions
md "C:\PapercutCacheDirectory"
goto SetPermissions

:SetPermissions
icacls "C:\PapercutCacheDirectory" /inheritance:r /grant:r "Domain Admins":(OI)(CI)(F)
icacls "C:\PapercutCacheDirectory" /grant "LB ITadmins":(OI)(CI)(F)
icacls "C:\PapercutCacheDirectory" /grant "*S-1-5-18":(OI)(CI)(F)
icacls "C:\PapercutCacheDirectory" /grant "*S-1-1-0":(OI)(CI)(F)

:end

 

You probably don't need all the groups to be fair - LB ITadmins is our local admin group (we are part of a mat), *S-1-5-18 is System and *S-1-1-0 is everyone (Everyone full control probably covers it but it works as it is) - PS make sure NOT to have the trailing \ after the folder name

 

Then run the papercut client using a machine policy with user loopback processing and add the following in - User Configuration > Admin Templates > System > Logon > Run these programs at user logon > Enable

 

\\LB-Print\PCClient\win\pc-client-local-cache.exe --silent --noquit --debug --cache c:\PapercutCacheDirectory

 

You probably don't need the --debug but it was handy to check what was happening

 

When it is working correctly you should see the files stored in your PCClient\win folder being copied to the c:\PapercutCacheDirectory folder - ours creates a folder called pc-client.exe-18.3.2.47391

Edited April 26, 2019 by siuko

[DrCheese]

Is anyone else getting this error about Cache?

 

Yes, got that on a few machines when we was on Version 19 (I rolled my VM snapshot back to 18.3 when the CPU error occurred) that I didn't get on 18.3 or below

[ITGURU]

We've had issues since upgrading to 19.0.2 - we use the cache client which runs at startup but all users are getting the error below:

 

I was told it was a known issue, and needed to change permissions on the C: drive but all other releases have been fine after updating the server. support eventually acknowledged other customers have the issue so is a bug is 19.0.2. Waiting for an update on a fix or re-release.

[ITGURU]

Just checked the server post 19.0.2 update - Papercut serer on windows server 2012 and PC-APP is running at 90% CPU ! Doh - will be reporting that one too!

[ITGURU]

Is anyone else getting this error about Cache?

 

Just seen this but replied on separate message. We're getting the same error but is NOT related to permissions and they've not been changed and every other version has been fine up til now!

[rogerdnixon]

We have the same error message - but only if a second user logs into the PC. First users is always fine. Rather than just running the cached client it appears to try to recreate the entire folder, but cannot as it open by the other user thats logged in. I'm just using the previous version of the client which appears to work fine. Papercut reproduced the issue after I reported it a couple of weeks ago and are working on a fix.

[Big_Ted]

new release:

https://www.papercut.com/products/mf/release-history/

[MartinT]

19.0.3 applied successfully, all seems to be working ok.

 

Hoping I don't have to go around doing all the copier clients again after 19.0.2.

[Big_Ted]

19.0.3 applied successfully, all seems to be working ok.

 

Hoping I don't have to go around doing all the copier clients again after 19.0.2.

 

what devices do you have?

[MartinT]

what devices do you have?

 

Kyocera copiers. Very good, very reliable.

[rogerdnixon]

Just got a version today that patches the client cache issue. Will try later.

[NetworkServices]

Just got a version today that patches the client cache issue. Will try later.

 

We've started getting the 'unable to create the local cache' error since upgrading to 19.0.3. Was your patch successful?

[ITGURU]

We've started getting the 'unable to create the local cache' error since upgrading to 19.0.3. Was your patch successful?

 

I applied the patch and not heard any users complain still.

 

I did notice however the naming convention for the cache folders has changed on the latest releases showing 100. rather than the papercut version.

 

[NetworkServices]

That sound promising. I'll contact PaperCut and see if they can send me the patch file.

 

Thanks.

[MYK-IT]

We've started getting the 'unable to create the local cache' error since upgrading to 19.0.3. Was your patch successful?

 

Previously had the 'hot-fix' installed, and now 19.0.3.

 

I have, and still only get the 'unable to create the local cache' error appearing (not all the time) on Windows 10 computers, not seen the error on our Windows 7 computers (yet).

[rogerdnixon]

The latest patch fixes the client issue.

[Jaan]

I applied the patch and not heard any users complain still.

 

I did notice however the naming convention for the cache folders has changed on the latest releases showing 100. rather than the papercut version.

 

[ATTACH=CONFIG]53257[/ATTACH]

 

I'm running:

 

PaperCut MF

Version: 19.0.3 (Build 49324)

 

Built on: Apr 26, 2019

 

and still have the client caching issue.

 

My client pcs have version "pc-client.exe-100.9.0.868-697855A" but you seem to also have a later one.

 

Can you confirm if you're still having the cache issue on the version of papercut your running please?

 

Cheers

[rogerdnixon]

We are on pc-client.exe-100.10.0.927-2382DF8 and the local cache issue has gone.

[Jaan]

I don't seem to have that version, even though i have a upto date papercut server instance

[rogerdnixon]

I got it direct from Papercut following out support ticket with them.

[Jaan]

ah, so it's not part of the 19.0.3 release?

[rogerdnixon]

No - they said it would be in 19.0.4 - but you can request it.

[MartinT]

Are you running pc-client from the PaperCut server or do you copy it locally?

 

We group policy it directly from the PC server, so the client is always updated.

[rogerdnixon]

We use the local cache version - so its set to run from a network share and it checks if there is a local copy and if there is runs from the local cache - live is C:/cache. If there is a new version in the network share it puts the new version into C:/cache. Found this to be the best option.

[MartinT]

We ran that for a while, found it was less reliable. It doesn't seem to make much speed improvement.