hey there,
I tried the same code configured for SQL Server and this problem did not occur. I am starting to think that this could be a problem, however I am unsure if it is an issue with log4net or an issue with the MySql connector. I also tried this with the latest version of the connector for MySql and got the same problem... From: kar...@hotmail.com To: log4net-user@logging.apache.org Subject: RE: Key cannot be null error Date: Fri, 22 May 2009 14:45:33 +0100 Hi Gary, I have access to an SQL Server, so I will try out my code against it later this evening. If you did follow my post on DevShed, then we will more or less have the same code. If it produces the same error or not, I will post back the results here. Date: Thu, 21 May 2009 20:57:14 +0000 From: lewd_revel...@yahoo.co.uk Subject: Re: Key cannot be null error To: log4net-user@logging.apache.org Thanks for your replies Karim & Radovan. I have attempted to track down the problem with the log4net source, but this doesnt seem to have yielded much success. I am thinking that this could possibly be an error with MySql connector as opposed to log4net, after all this doesnt seem to be happening with SQL Server or Oracle (or at least it isnt being reported). Karim, I think I followed your example on DevShed concerning this setup, I would like to thankyou for putting that together and I look forward to reading your blog article on this, I hope one of us will be able to overcome this problem - unfortunately, I dont have access to another DB to test this out on, but it would be nice to hear back from someone using the same code with Oracle or SQL Server. From: Karim Bourouba <kar...@hotmail.com> To: log4net-user@logging.apache.org Sent: Thursday, 21 May, 2009 11:52:56 Subject: RE: Key cannot be null error Hi Radovan, thats a great idea, I will give it a go and report back. Many thanks Subject: RE: Key cannot be null error Date: Thu, 21 May 2009 12:43:15 +0200 From: ras...@hasam.cz To: log4net-user@logging.apache.org Hello, you can try this: download log4net sources and attach them to your project instead of reference to log4net.dll. Now you'll be able to debug inside of AdonetAppender and you can find what exactly is null and guess the correct value, I hope. Radovan Raszka Od: Karim Bourouba [mailto:kar...@hotmail.com] Odesláno: 21. května 2009 10:43 Komu: log4net-user@logging.apache.org Předmět: RE: Key cannot be null error Hi Gary, I am actually having the same problem as you - I think. I definitely get the same error as you. Can I ask if you are using MySql at all? Unfortunately though, I havent had any luck with asking this question on this list, it would appear that the list is not as busy as I thought it initially was, or the other subscribers are unable to comment. To help you with your problem, if it isnt the same as mine, would be to post your code on the list itself. That gives everyone the chance to take a look and see if they can spot the issue. If you do have the same problem as me, could you post your solution should you fix it? That way others, including myself will be able to resolve this in future. Date: Wed, 20 May 2009 22:02:14 +0000 From: lewd_revel...@yahoo.co.uk Subject: Key cannot be null error To: log4net-user@logging.apache.org Hello, Could someone explain to me what the following error means please? log4net:ERROR [AdoNetAppender] Could not open database connection [] System.ArgumentNullException: Key cannot be null. Parameter name: key I encounter this error when trying to log to my database. The rows are updated, but I get this message pop up on the console. I dont know how busy this list is, but I would really appreciate it if someone could lend a hand. TIA Share your photos with Windows Live Photos - Free. Try it Now! Windows Live Messenger just got better. Find out more! Share your photos with Windows Live Photos - Free. Try it Now! _________________________________________________________________ Share your photos with Windows Live Photos - Free. http://clk.atdmt.com/UKM/go/134665338/direct/01/
