You are viewing limited content. For full access, please sign in.

Question

Question

Value cannot be null. Perameter Name: s

asked on July 5, 2016

My client is getting this error when opening LFScanning in version 10, "Value cannot be null. Parameter Name: s" and then after clicking ok, "Object reference not set to an instance of an object.". I haven't been able to find any information on the first error, but so far repairing has not fixed the issue. I'm going to clear attributes but wanted to know if anyone had a solution other than that. Their client is version 10.0.0.994 and they are on Windows 10.

FirstError.PNG
SecondError.PNG
FirstError.PNG (14.95 KB)
SecondError.PNG (23.37 KB)
0 0

Replies

replied on July 6, 2016

Please open a case for this issue.

0 0
replied on May 12, 2017

Ricardo,

We are having the same problem (both error messages) after an upgrade to Laserfiche 10.1. Could you please comment how have you solved this issue?

 

Thanks in advance,

 

Paula.

0 0
replied on May 12, 2017

I can't find my notes from that case, but I can say with 70% certainty that clearing their attributes fixed the issue. Otherwise possibly going to C:\Users\*username*\AppData\Local\Temp\Laserfiche Scanning and the error logs there might reveal more information.

1 0
replied on May 15, 2017

Thank you, local temp files deleted is the one!

0 0
replied on September 22, 2017

Hi Paula,

I'm having the same issue,. Could you clarify the deletion of the local temp files that seemed to work for you?

 

Thanks!

0 0
replied on May 1, 2019 Show version history

Hello,

I am having the same issue after we upgraded all our users to their own named license in LFDS. I imported their attributes from their old repository named user and now they can't scan. What file exactly did you delete in the local temp files to fix this issue?

Thanks!

0 0
replied on May 7, 2019

Hi Paula,

 

Resetting the user attributes back to default (removing them all) and resetting the settings back to default (Tools-Options-Reset-Restore) solved this issue for me. Hope this helps!

 

Thanks!

1 0
replied on July 1, 2020

I faced this error before, and it was related to OCR settings, as OCR was not installed, after installing OCR, the issue was solved and all users are working fine

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.