[ https://issues.apache.org/jira/browse/LOG4NET-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157062#comment-14157062 ]
Dominik Psenner commented on LOG4NET-442: ----------------------------------------- A little bit of googling brought up this: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c488cf76-2515-440f-b3f8-9cfad689c5b6/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server?forum=sqldataaccess It might be an issue that your client provider uses named pipes to communicate and thus does behave somewhat strange to disconnections. Have you enabled TCP/IP connections on the SQL server? > ReconnectOnError > ----------------- > > Key: LOG4NET-442 > URL: https://issues.apache.org/jira/browse/LOG4NET-442 > Project: Log4net > Issue Type: Bug > Components: Builds > Affects Versions: 1.2.13 > Environment: Microsoft .NET 4.5 > Reporter: Alessio Sanguineti > Attachments: log4net.txt > > > Hello, in our .NET application using Log4Net to log on a Sql Server 2014 > database, we set the parameter "ReconnectOnError" to true in the ADO.Net > Appender configuration. > Even if the property seems to be read correctly (as visible on the log), > whenever the server is not reachable for a while the appender does not > reconnect anymore thus not logging anything else. > We get the log file attached of a test where we turned off SQL Server for > about 1 minute before restarting it. > Thank you. > Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)