Can't comment on v1.2.8, Simon, but I've been working with AdoNetAppender a fair amount in v.1.2.9 and that appender has been around a while, methinks. If you can successfully connect using one method, then the odds are you've just got a problem with your connection string syntax using the other one, wouldn't you think?
Anyway, why don't you tell us what specific dbms provider you're using and what connection string you're passing? Also turn on internal log4net debugging and let's get at the actual error msg coming back from the dbms provider. Perhaps your dbms network client aliasing ain't right for that IP, or you've got "named instances", or some such. -BillyB WILLIAM BARNUM 14076 Rosario Rd. Anacortes, WA 98221-8559 Phone: 360.299.3830 Cell: 360.202.3670 [EMAIL PROTECTED] -----Original Message----- From: Simon Wallis [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 03, 2006 7:45 AM To: Log4NET User Subject: Re: ADONetAppender - can only use IP in connection string? Thanks. Can anyone comment on log4net 1.2.8? 1.2.9 was a significant upgrade. Simon. -----Original message----- From: si [EMAIL PROTECTED] Date: Mon, 02 Jan 2006 23:34:20 -0800 To: Log4NET User [email protected] Subject: Re: ADONetAppender - can only use IP in connection string? > Hi Simon, > > > Hi, it seems that we can only use the IP,port of our database in the ADON> etAppender > > connection string (log4net 1.2.8). Is there a limitation that is preventi> ng us from using the > > database name, or should the database name work as well as IP,port? > > No problems here using database name for SQL Server on log4net 1.2.9. > > <appender name="AdoNetAppender_SqlServer" > type="log4net.Appender.AdoNetAppender"> > <connectionType value="System.Data.SqlClient.SqlConnection, > System.Data, Version=1.0.3300.0, Culture=neutral, > PublicKeyToken=b77a5c561934e089" /> > <connectionString value="Server=BLAH; database=BLAHBLAH; Integrate> d > Security=SSPI;" />
