Last post Apr 14, 2008 09:58 AM by zVinod
Aug 24, 2006 12:54 PM|bmains|LINK
I have the Exception handler defined in my code, and I have this configuration:
But I am getting an error with the <add logCategory="UI" ..> statement. The EL Config Tool says it is fine, but after running it, I get the following error:
The type Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.LoggingExceptionHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging, Version=22.214.171.124, Culture=neutral, PublicKeyToken=null from configuration
could not be created.
Aug 29, 2006 03:41 PM|mamoonseth|LINK
Did you solve your issue? or did u give up on it :)
I'm having a similar problem
Thank you for your help!
Aug 29, 2006 07:44 PM|bmains|LINK
Gave up so far... I don't have the time... I could easily create my own custom component to do this... All you need is a class with a static method to write, and do a database write like any other DAC object.
Oct 02, 2006 10:42 AM|ruimelo|LINK
I had the same problem.
It has to do with the instantiation of the class, so it must be a problem of a DLL, I figured.
So in a brute force atempt, i added references to all the DLLs in the instalation dir\bin of the Ent Lib (in my case it is C:\Program Files\Microsoft Enterprise Library January 2006\bin) to the project, and now it runs smoothly.
I will try to figure the exact class(es) and when I do, I'll add a new message here.
Hope it helps!
Oct 05, 2006 07:45 PM|rboarman|LINK
Any luck on this? I'm having the same issue.
Oct 09, 2006 12:42 PM|kgayda|LINK
I found that the solution to the problem was that you need 2 references. The documentation for the PuzzlerUI lab only mentions that you need a reference to the exception handling DLL. You must also add a reference to the Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging
as well to avoid the unhandled exception.
Dec 04, 2006 06:47 AM|jbanx|LINK
I had the same problem and I resolved it by first referencing the Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging; and then using the namespace in the necessary page.
For any clarification get back to me...
Jan 08, 2007 09:44 AM|TheRave|LINK
Same problem here, I tried all of the above things, but they dind't worked for me.
What did worked is very strange, I create a LoggingExceptionHandler, but don't use it.
I'm guessing that it forces the loading of the DLL and therefore it works. If I comment out the line: LoggingExceptionHandler han=null; it gives me the error that was mentioned in the first post.
public class ExceptionManager
public static void HandleExceptionNoLogging(Exception Ex)
ExceptionPolicy.HandleException(Ex, "Global Policy");
It's not a clean way, but creating an empty LoggingExceptionHandler hasn't got a huge impact and it works...
Jun 27, 2007 05:52 PM|ennganesh|LINK
Thanks ..I too faced the same probs It works[:)]
Aug 15, 2007 12:07 PM|mosius|LINK
I had the same problem. I added to my references
and it worked like a charm.
Nov 30, 2007 06:31 AM|Prasanth_gold8|LINK
me too got the same problem
I was solved
Apr 14, 2008 09:58 AM|zVinod|LINK
Well I did have the same problem. The following dll need to be referenced which resolves this problem.