So this happened AGAIN and this time we noticed right away. It was after a server update from Windows. We suspected something in the firewall or antivirus. And indeed it appears it was related to windows firewall.

On the machine running Laserfiche server service -

Disable the BranchCache service by running the (as Admin) PowerShell command: netsh branchcache set service disabled After running the command, restart the LFS service. Once that's done, run Get-BCClientConfiguration and confirm that the CurrentClientMode value is set to "Disabled"

And voila problem solved.

This happens for different documents. When scanning in new documents using Laserfiche Scanning, it is a hit or miss. Even documents that were already in the repository are affected.  

What kind of antivirus application are you running? Did you make all the Laserfiche files, folders, executables and processes exceptions?

As a test, temporarily remove it from the client machine then LF test without it. 

Was there ever a resolution on this? This is happening to us now on users running the 10.2 client randomly. When a user gets the error on a given document, they get it consistently for that document. Some users; however, don't get that error for the same document. Both users in this case are running the same version of the client. Also, a user may get an error on one document and then successfully open another document, even though both are on the same volume (so it doesn't seem to be an issue with volume security).

Thanks,

Julie

I am having this error now also - and it's very weird. The first time I open a document, it's fine. I close it and re-open it and the image fails to load. Some documents are not affected at all. Some are different WITHIN the same document - one page loads fine, another does not. Once a page/image fails to load it won't come back. However, some that load okay 1 time, do not load the next time. I've restarted the laserfiche server. It appears to only be images scanned from a particular scanning station. And only things from today.

We will reboot the scanning station, but because the error is so inconsistent, I wonder if it's even related to the scanning station.

For what it's worth ... inexplicably the problem disappeared today (so far). Prior to it getting fixed, we deleted my user attributes. We didn't touch anyone else's attributes. But after that, it worked for me AND OTHERS. We re-imported my user attributes and it STILL WORKS.

We will be watching closely to see if it reoccurs at all.

Thank you to MCCi and City of Charlottesville IT dept for assistance and cooperation!