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

Question

Question

Performance warning: connecting to the database server did not complete in a timely fashion. This event usually indicates that the database server is overloaded.

asked on September 28, 2019

Hi all,

 

I recently moved the Hyper V Vms that I had my Laserfiche installations on (1 for LF server, Web Access and Mobile Server, Another for database and one for workflow and forms.

All of sudden I keep getting this warning "Performance warning: connecting to the database server did not complete in a timely fashion. This event usually indicates that the database server is overloaded." and performance is dreadful while navigating through the repository. I tested moving the VMs back to the old server and performance is great again.

All VMs are on the same server, same as before so I'm quite lost as to why this is happening all of a sudden. Any feedback would be great. LF version is Avante 10.2

Thanks in advance.

0 0

Replies

replied on September 30, 2019

So you're saying you changed Hyper V servers? What is the difference between the 2 servers? Have you looked at your SQL Server stats? Is it overloaded?

0 0
replied on September 30, 2019

That's correct, old server was out of warranty.

 

They both have 16 GB of RAM,

 

The old server has 2 x AMD Opteron 6128 2.00 GHz Processors and 4 NICs  

The new server has 1 x Intel Xeon Silver 4114 2.2GHz Processor and 2 NICs

The sql server VM seems normal, no massive use of RAM and no errors in the event viewer. 

It just seems like the Laserfiche Server VM takes a long time to contact the database on the database VM.

I've tested the network connectivity between the two and everything also seems normal (file transfers work as normal etc)

0 0
replied on August 25, 2020

Hi Ruel, 

Were you able to resolve this issue? We are seeing this error with a client on 10.4.1 and just beginning to investigate it. Your resolution may be helpful. 

Thanks

0 0
replied on October 27, 2022

Hi, did you find a resolution?  We are having this issue.

0 0
replied on October 27, 2022

Stacy, please don't post the same question multiple times. We are aware that you and Merlin are experiencing issues. Laserfiche Support is already in communication with your solution provider.

0 1
replied on October 28, 2022

When will they be in touch with me because this is a production problem. I was hoping to find a solution here from other users as well.  

0 0
replied on October 27, 2022 Show version history

Was Laserfiche able to resolve this issue? I am seeing the same warning in the event viewer even though our SQL server is not overloaded. We run Laserfiche Server service on its' own VM server which has 32 cores and 128 gig of ram. 

 

Also our SQL Server VM is 32 Core with 875 Gig of RAM.

 

0 0
replied on October 27, 2022

There isn't enough information in this thread or your post to hazard a guess. The message is reported by the Laserfiche Server if it takes more than 1 second to establish a connection with SQL Server. There could be various reasons why the connection between 2 machines is slow, the message indicates the most common one. Given your server specs it's possible that it may be a network issue rather than load on SQL, but we can't rule it out.

Please work with your solution provider to troubleshoot the issue with Laserfiche Support.

0 1
replied on October 27, 2022

Any resolution?  We are having the same issue.

0 0
replied on October 28, 2022

The connection taking a long time is just a symptom, so the resolution is going to depend on the underlying cause. In the original post, performance is uniformly bad, so that at least rules out that it's something specific to establishing a connection. From the Laserfiche server, all it knows is that responses aren't coming back as quickly as they should. The obvious places for the time to be lost is 1) queries are executed slowly, and if so the most likely cause is that the server is overwhelmed - this is what the error message gets at - or 2) general network slowness between the Laserfiche server and the SQL server.

If load is light on the SQL server, and a tool like Profiler indicates that the queries are executing quickly, then you're probably looking at a network problem. In that case, you'll fallback on the typical troubleshooting process for that: ping, Wireshark, firewall logs, testing latency from/to other machines, etc.

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

Sign in to reply to this post.