Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 96899 invoked from network); 6 Nov 2008 13:06:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Nov 2008 13:06:46 -0000 Received: (qmail 28397 invoked by uid 500); 6 Nov 2008 13:06:51 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 28376 invoked by uid 500); 6 Nov 2008 13:06:51 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 28361 invoked by uid 99); 6 Nov 2008 13:06:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Nov 2008 05:06:51 -0800 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [195.18.128.130] (HELO vbdtrend2.vbd.no) (195.18.128.130) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Nov 2008 13:05:30 +0000 Received: from vbdex.vbd.no ([172.20.1.31]) by vbdtrend2 with InterScan Messaging Security Suite; Thu, 06 Nov 2008 14:06:06 +0100 Keywords: disclaimer X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C94010.6D2C7A1D" Subject: RE: SQL 2005 Database Mirroring Support Date: Thu, 6 Nov 2008 14:06:05 +0100 Message-ID: In-Reply-To: <7E418EB425E58A49BCCEC5A4450F7B1E24093DAC85@ebs-exch01.EBSGlobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SQL 2005 Database Mirroring Support thread-index: AclABx7LeDKSeqlERRG9sxB5cvHsKgABgAbw References: <7E418EB425E58A49BCCEC5A4450F7B1E24093DAC85@ebs-exch01.EBSGlobal.net> From: "Dag Christensen" To: "Log4NET User" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C94010.6D2C7A1D Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Should be handled transparently if you're using SqlClient or native client and a correct connection string. I think log4net uses OLE DB by default, you might want to try changing this to SqlClient. =20 If it still doesn't work, try setting your appender's ReconnectOnError to true. =20 It would also be helpful if you posted the versions you're using (log4net, SQL server 2005 service pack?, .NET framework version and service pack?) and your log4net configuration. =20 Best wishes, Dag =20 =20 From: Gourlay, Colin [mailto:cg1@ebs.hw.ac.uk]=20 Sent: Thursday, November 06, 2008 12:59 PM To: Log4NET User Subject: SQL 2005 Database Mirroring Support =20 Does log4net support the database mirroring feature in SQL 2005?=20 =20 It logs quite happily when logging to our primary database but when I failover logging ceases to work - in that nothing is logged - when I failback logging works as before. The mirroring has been configured correctly (test has been done to verify this) so I think I can rule this out. =20 Other than the following entry (as per http://blogs.technet.com/johnbaker/archive/2005/10/06/412126.aspx) included in my connection string is there something else required? =20 failover partner=3DMyFailoverDatabaseServer =20 Is there anything else I should be considering? =20 Thanks in advance. =20 Colin =20 =20 =20 =20 =20 ________________________________ Edinburgh Business School is a Charity Registered in Scotland, SC026900 ###########################################=0A= =0A= This message has been scanned by F-Secure Anti-Virus for Microsoft = Exchange.=0A= For more information, connect to http://www.f-secure.com/ ------_=_NextPart_001_01C94010.6D2C7A1D Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Should be handled transparently if you’re using SqlClient or native = client and a correct connection string. I think log4net uses OLE DB by default, you = might want to try changing this to SqlClient.

 

If it still doesn’t work, try setting your appender’s = ReconnectOnError to true.

 

It would also be helpful if you posted the versions you’re using = (log4net, SQL server 2005 service pack?, .NET framework version and service pack?) and = your log4net configuration.

 

Best wishes,

Dag

 

 

From: Gourlay, Colin [mailto:cg1@ebs.hw.ac.uk]
Sent: Thursday, November = 06, 2008 12:59 PM
To: Log4NET User
Subject: SQL 2005 = Database Mirroring Support

 

Does log4net support the database mirroring feature in SQL 2005? =

 

It logs quite happily when logging to our primary database but when I = failover logging ceases to work – in that nothing is logged – when I failback logging works as before.  The mirroring has been = configured correctly (test has been done to verify this) so I think I can rule this = out.

 

Other than the following entry (as per http://blogs.technet.com/johnbaker/archive/2005/10/06/412126.aspx) included in my connection string is there something else = required?

 

failover = partner=3DMyFailoverDatabaseServer

 

Is there anything else I should be = considering?

 

Thanks in advance.

 

Colin

 

 

 

 

 


Edinburgh Business School is a Charity Registered in Scotland, = SC026900

###########################################

This message has been = scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more = information, connect to http://www.f-secure.com/ ------_=_NextPart_001_01C94010.6D2C7A1D--