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

Question

Question

Entry Not found. [9001] when trying to do a customized search.

asked on February 16, 2016 Show version history

We recently upgraded Laserfiche from 9.2 to 10 yesterday. When users try to do a customized search, we are getting the following error. Entry Not Found 9001. 

 

Has anyone ran into this issue? if so, how can we resolve it?

 

thank you

Capture.JPG
Capture.JPG (50.63 KB)
0 0

Answer

APPROVED ANSWER
replied on February 25, 2016

The issue was that there were entries in the recycle bin, but weren't properly flagged as such in the database. So when running a search, it was trying to return applicable results that included those recycle bin entries. The SQL script provided cleaned up the issue and properly flags the recycle bin entries. Now they are correctly ignored when the Laserfiche Server processes the search results.

This issue will also be addressed in the next update of the Laserfiche Server and won't require running any SQL queries. The query mentioned previously is to address the matter now, before the next update.

2 0

Replies

replied on February 16, 2016

Maybe the search contains a "within folder" section that isn't finding the folder? Can you provide more information about the search being run?

0 0
replied on February 25, 2016

Robert thanks for your reply. Our vendor got a hold of us to troubleshoot this. We had to get Laserfiche involved. I had to run a script on our SQL Server that changed the tags of our Recycle Bin items. 

0 0
APPROVED ANSWER
replied on February 25, 2016

The issue was that there were entries in the recycle bin, but weren't properly flagged as such in the database. So when running a search, it was trying to return applicable results that included those recycle bin entries. The SQL script provided cleaned up the issue and properly flags the recycle bin entries. Now they are correctly ignored when the Laserfiche Server processes the search results.

This issue will also be addressed in the next update of the Laserfiche Server and won't require running any SQL queries. The query mentioned previously is to address the matter now, before the next update.

2 0
replied on February 25, 2016

I appreciate your help Alexander. 

0 0
replied on April 26, 2016

This has been addressed in the Laserfiche Server 10.1.

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

Sign in to reply to this post.