We are experiencing critical, random website outages. The site goes down completely, returning 500 Internal Server Errors to all visitors. We urgently need your assistance to review our architecture and pinpoint the cause of these database disconnections. Here are the specific fatal errors we are capturing simultaneously during a crash:
1. Hard Network Drop (Named Pipes Error)
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available
2. Connection Pool Exhaustion (Cascading Effect)
System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
3. Cascading Application Failure
DotNetNuke.Common.Initialize - The connection to the database has failed, however, the application is already completely installed, a 500 error page will be shown to visitors
What we have verified/attempted so far:
Connection Strings: Verified and tested. The site runs perfectly fine until these random drops occur.
Pool Size: We have already increased our Max Pool Size to 500, but the pool is still maxing out entirely when the network drop occurs.
Max Pool Size
I realize you posted this a few days ago and I hope you've already made progress. If not, its obviously hard to tell much from those errors without better understanding your setup. Is the SQL Server local or remote?
In general it looks like the problem is not DNN related and instead, the initial connection cannot even be established. So focus on debugging your networking first. If the connection is SMB/Named Pipes, check DNS, the path, or is their simply a LAN issue. If its not network, then something is causing SQL to stop listening. I would dig in an after noting the exact time the problem starts, carefully examine your SQL logs to see what is going on.
Please share more details as you never know what clue is going to trigger someone's memory of a similar situation. Cheers!
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.