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.