You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-user@logging.apache.org by Mike <mi...@btinternet.com> on 2005/04/12 18:40:14 UTC

Re: General Network Error after MSCS Failover

Vincent Ramona <vincent.ramona <at> unilog.fr> writes:

> 
> Hello,
> 
> I've installed Log4Net with a database appender on SQL Server 2000 on
> windows 2003 MSCS Cluster.
> When the first SQL node is active, everything works fine. If I stop my
> program, than activate the second SQL Node, and then start my program,
> everything works fine.
> The problem is that le active node is changing when my program is working.
> In this case, I'm getting the "General Network Error" from ADO.Net.
> 
> Can anyone helps me ?
> 
> Vincent Ramona
> 
> 

Try turning off connection pooling. I think this is turned on by default with 
ADO.Net. This might make you app slower but for some reason you cannot use 
Connection pooling when using an Application role to connect to SQL server 2000.

This person had the simlar problem:

http://sqljunkies.com/WebLog/orfda/archive/2003/10/22/295.aspx

Mike