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

Question

Question

Scanned documents not being transferred to repository

asked on January 29, 2014

 I have a user that once she scans the documents and tries o store them, nothing happens. The documents are still in the scan window and when you look in the repository, the document name is there with a page count of 0. There are times when the documents get stored but then it reverts to not storing anything. Has anyone experienced this issue. It's a Kodak i2600 scanner.

0 0

Answer

APPROVED ANSWER
replied on January 29, 2014

Check the output pane and the application errors pane in Laserfiche Scanning for more details regarding a possible error. One thought could be an I/O error caused by the hard disk where the volume is stored being full. You can test that by doing a basic file import via the LF Client and specifying the same volume that you're scanning new documents into.

0 0
replied on January 29, 2014

Thanks, i'll go in and try your recommendations.

0 0
replied on March 3, 2014

My issue is similar. We just switched to the Web Client, and now our scanners sporadically get this in the output log:

"The object is not identified, and cannot be locked or read from."

 

The solution is to close scanning and open it back up. The users are used to leaving the LF Scanning window open at all times, and scanning on demand. Is there a timeout feature in the LF Web version of it?

1 1
replied on July 31, 2014

I have a person scanning a large number of documents for us related to a digitization project and we are receiving the same error as Jason: 

 

"The object is not identified, and cannot be locked or read from." 

 

It happens sporadically and the only way to get documents to store is to close down Laserfiche Scanning and then re-open it, however this means that they have to scan the document again. 

 

Also, it only occurs when we use the Web version (we are running LF 9.1). 

0 0

Replies

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

Sign in to reply to this post.