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

Question

Question

Windows NT event error for LFS

asked on June 2, 2015

Hello Good People,

 

I didn't see anything on the Answers site, the old Laserfiche support site, nor the Microsoft Knowledge base for this error I am having. I first saw in in my event log. The content of the message appears to be a SQL query in the Laserfiche tables, but there is no distinct entry ID, TOC, etc.

An associate of mine cautioned me about searches that continue on indefinitely that need to be stopped manually. Could this be a reoccurring search that always fails? There were no Workflows that occurred at the time this error was created. 

 

Any guidance is greatly appreciated. Here is the content of the event log error:

Date        6/2/2015 3:56:44 PM
Log        Windows NT (Application)

Source        LFS
Category        (0)
Event        1074014018
Computer        PALMLSF.palmbeach.local

Message
Database statement execution error encountered.

Session ID: ;
Dialog ID: 79968147;
Repository: 'Palm-Beach';
CLI routine: SearchExecuteThread;
Message: [Microsoft][SQL Native Client]Operation canceled;
SQL Statement: 'select distinct t.tocid, t.parentid from toc t join propval pv on pv.tocid = t.tocid join propdef pd on pv.prop_id = pd.prop_id where (t.toc_flags & 2048) = 0 and t.tocid <> 2 and exists(select * from propacl where propacl.prop_id = pv.prop_id and propacl.sid in (select sid from sess_sid where sess_id = :rsid2<int> ) and ace_type = 0 and mask & 1 = 1) and not exists(select * from propacl where propacl.prop_id = pv.prop_id and propacl.sid in (select sid from sess_sid where sess_id = :rsid3<int> ) and ace_type = 1 and mask & 1 = 1)and ((exists(select * from psetacl where psetacl.pset_id = t.pset_id and psetacl.sid in (select sid from sess_sid where sess_id = :rsid4<int> ) and ace_type = 0 and mask & 1 = 1) and not exists(select * from psetacl where psetacl.pset_id = t.pset_id and psetacl.sid in (select sid from sess_sid where sess_id = :rsid5<int> ) and ace_type = 1 and mask & 1 = 1)) or t.pset_id is null or t.pset_id not in (select pset_id from pset_props where prop_id = pv.prop_id)) and ((((pv.str_val like :str6<char[6]> ) and pd.prop_type in ('S','L'))))';
SQL variable: '';
SQL State: HY008.

 

Thank you in advance!

0 0

Replies

replied on June 2, 2015 Show version history

The error you mention above only shows up for earlier versions of Laserfiche. Please confirm the version you have by going to Help > about in the client.  Also go to the LF server folder and get the version of the file lfs.exe by right clicking on it, selecting "properties" and the "Details" tab.  The version should appear as something like this 9.x.x.xxx. 

Also, what OS and service pack is your server running with?  What version of SQL are you using?

1 0
replied on June 3, 2015

Does the message occur on a regular basis? It looks like a cancelled search. 

You can try running an audit report and look for search activities for the time that the message occurs.  It might return a user and you can ask if they are cancelling field searches.

1 0
replied on June 4, 2015

If you suspect it is a Workflow, run an Audit trail report against your Workflow Profile user and compare those results against the time that the errors occurred.  You can then probably isolate the issue to a particular workflow. 

1 0
replied on September 28, 2015

I am also seeing this at a customer site - same error. Once we see this error a couple of times it brings LFS to its knees and requires a service restart. They are running LFS 9.1.1.584. Chris Cartett - were you able to resolve this issue?

 

1 0
replied on February 10, 2016 Show version history

Hey Chris... 

We are experiencing the same issues over here.  Randomly occurring LFS 10050 errors with an included SQL statement.  The only difference is that some (not all) of our errors include session IDs.

I have ran an audit attempting to match any scheduled or conditionally based workflows with the times these errors occur and have come up empty handed.  Using the included session ID, i was able to trace the error back to a user who was having issues on the Laserfiche client side.  Sometimes, the end user does not recognize an issue with Laserfiche but the majority of end users must restart their client in order to complete whatever task it was they were performing.

I have found this support article buried in the Laserfiche site and will try contacting our VAR for further assistance.

https://support.laserfiche.com/kb/1012566

Not sure if you have tried this or not, but I also ran across another article suggesting to grant sysadmin to the Laserfiche Server service account.  I DO NOT recommend granting those types of permissions, but if granting those "temporarily" works it could lead Laserfiche support to explain what server security rights in SQL the account actually requires other than dbowner on the db.

https://answers.laserfiche.com/questions/70557/SQL-connectivity-issue-

Will keep you posted

1 0
replied on June 2, 2015

What version of LF are you on? 

0 0
replied on June 2, 2015

9.1

0 0
replied on June 3, 2015

From the Client:

LFS Details:

OS Service Pack:

SQL Version:

 

Thank you for your time!

0 0
replied on June 4, 2015 Show version history

I filtered the entry log for the past 30 days. There are a few similar looking errors on the LFS. There is no consistency with the time they occur. The SQL query varies quite a bit also.

Can a cancelled search impact the LFS so much? If a user is running a search and then forces the client to close, that can be a cause.

If that is what is causing this error, then it does not sound like a big issue, except that it locked out users trying to log in while the LFS recovered.

I would suspect it is a Workflow search that runs if I had to guess a likely suspect. I have many scheduled Workflows that run every hour. Do you have any other suggestions for trying to find a user name? Will the SQL logs track who ran a particular query?

Thanks so much for the tips so far.

0 0
replied on June 4, 2015 Show version history

There was an ASP.NET warning that occurred 5 minutes prior to the LFS error. This makes me also entertain the idea that WebLink is a likely suspect as well. There are more variable that can lead to a browser page closing in the middle of a search.

I looked at the other similar LFS errors and found no consistency with the ASP.NET error being present before the LFS error occurs.

0 0
replied on June 4, 2015

I had to turn on auditing for the Workflow user. I will keep an eye on it. Good suggestion, thanks.

0 0
replied on September 29, 2015

I have let the Audit Trail compile data about the Workflow user. I have not checked back yet. No time, unfortunately. The note you made will help remind me. Thanks!

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

Sign in to reply to this post.