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

Question

Question

Several Database Connection error on LF Server

Laserfiche
Updated October 24, 2014
asked on September 10, 2014 • Show version history

 Hi Everyone,

 

I have a client using Laserfiche Rio 9.1.1

 

They have a Server for Laserfiche server, a DB server (SQL Server 2008 R2) and a Web Server for Audit Trail and Web Access. Audit Trail uses same database server as LF server.

 

We are receiving below error messages in LF Server Application logs in event Viewer:

 

Database statement execution error encountered.  Session ID: xxxx; Dialog ID: xxxx; Repository: 'xxxx'; CLI routine: SysIndexSetFlagBatch; Message: Failed to retrieve error information!; 

Database statement execution error encountered.  Session ID: xxxx; Dialog ID: xxxx; Repository: 'xxxx'; CLI routine: SysLookupEntryID; Message: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53]. 

Database statement execution error encountered.  Session ID: xxxx; Dialog ID: xxxxx; Repository: 'xxxx'; CLI routine: SysIndexSetFlagBatch; Message: [Microsoft][SQL Native Client]TCP Provider: The semaphore timeout period has expired.

The VSS writer LF_VSS_WRITER failed with status 8 and writer specific failure code 0x800423F2.

Database statement execution error encountered.  Session ID: xxxx; Dialog ID: xxxx; Repository: 'xxxx'; CLI routine: SysLookupEntryID; Message: [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.

 

On 2 days earlier we got a list of aprox. 30 users complaining error 9008 while browsing, uploading, opening documents and I can see above error the time they got this error. Today only 1 user got the error :An existing connection was forcibly closed by the remote host. I used the session ID in the error message to identify the error and saw that the user got error 9008 on screen while uploading a document on Laserfiche.

 

Can anybody help me identify the exact cause/ root cause of  this error. 

 

Thanks

Sweety

 

0 0

Answer

SELECTED ANSWER
replied on September 17, 2014

Right, like I said, the other possibility is that SQL was under heavy load. You'd want to look at CPU and memory usage on SQL when this happens, the SQL Activity Monitor and possibly the SQL logs. There isn't a single cause for the error, it has to be tracked down by correlating information from the various sources. You can open a support case if you need help.

The Laserfiche VSS Writer service is used to ensure that LF Server data is available for backups through the Volume Shadow Copy Service (VSS). If you're not using VSS for backups, it does not need to run.

0 0

Replies

replied on September 10, 2014

The errors above can be ignored. They look like SQL was restarted while Audit Trail/Laserfiche Server was still running. Both services would recover and resume normal operations once SQL is back up.

 

If the 9008 error happened when SQL was running, there should be a separate error message indicating what went wrong (and that would mention the 9008 error code).

 

 

0 0
View 1 previous reply
replied on September 10, 2014

The SQL server service was on running mode when the error occurred. The detailed message for error 9008 is:

 

on LF server event viewer

----------------------------------------

Database statement execution error encountered.  Session ID: xxxx; Dialog ID: xxxx; Repository: 'xxxx'; CLI routine: SysLookupEntryID; Message: [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.

 

Error message from LF Client

Detail for above error

0 0
replied on September 11, 2014

"An existing connection was forcibly closed by the remote host." usually indicates that the SQL Server is shutting down although you could also get the same message when SQL Server is under heavy load.

0 0
replied on September 16, 2014

Note that SQL Server service was running when I got these error. We also got an error: communication link failure to DB server

How about the other four errors occurred at the same time. Are they related?

 

 What is the purpose of LF_VSS_WRITER service? When do I have to enable it. note that I've disabled it on LF server.

0 0
SELECTED ANSWER
replied on September 17, 2014

Right, like I said, the other possibility is that SQL was under heavy load. You'd want to look at CPU and memory usage on SQL when this happens, the SQL Activity Monitor and possibly the SQL logs. There isn't a single cause for the error, it has to be tracked down by correlating information from the various sources. You can open a support case if you need help.

The Laserfiche VSS Writer service is used to ensure that LF Server data is available for backups through the Volume Shadow Copy Service (VSS). If you're not using VSS for backups, it does not need to run.

0 0
replied on September 15, 2014

Hi Sweety, 

 

If your question has been answered, please let us know by clicking the "This answered my question" button on the response.

 

If you still need assistance with this matter, just update this thread. Thanks!

0 0
replied on October 24, 2014

I have this problem as well in several isolated environments. Restart LF service temporarily fixes it but it keeps coming up again and again.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...