Solved

Microsoft Enterprise Library 6.0: ExceptionPolicyFactory does not create Exception Manager

Posted on 2013-12-17
3
2,599 Views
Last Modified: 2014-01-02
I started playing with Microsoft Enterprise Library 6.0 using .Net 4.5 and VS 2012.

I am trying to use the exception handling block and logging block to first log an exception and then replace the exception with another exception.

This is the configuration section:

<exceptionPolicies>
            <add name="ReplaceWithFriendlyMessage">
                <exceptionTypes>
                    <add name="All Exceptions" type="System.Exception, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                        postHandlingAction="ThrowNewException">
                        <exceptionHandlers>
                <add name="Logging Exception Handler" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.LoggingExceptionHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
                              logCategory="General" eventId="100" severity="Error" title="Enterprise Library Exception Handling"
                              formatterType="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.TextExceptionFormatter, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling"
                              priority="0" />
                            <add name="Wrap Handler" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.WrapHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
                                exceptionMessage="Unexpected Error Occurred" wrapExceptionType="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.ExceptionHandlingException, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
                        </exceptionHandlers>
                    </add>
                </exceptionTypes>
            </add>
</exceptionPolicies>

 

This is how the exception handling factory is used at initialization:

Dim config As IConfigurationSource = ConfigurationSourceFactory.Create()
Dim factory As ExceptionPolicyFactory = New ExceptionPolicyFactory(config)
exManager = factory.CreateManager

exManager is of the type ExceptionManager and defined as an instance variable of the form.

I noticed that the factory.CreateManager code returns a null object with the configuration defined above. So my code throws a null reference exception later when I call exManager.Process or exManager.HandleException.

If I comment out the logging exception handler section, the exception manager gets loaded and handles the exception using the wrap exception handler. So if I comment out this text, the code works fine.

<!--<add name="Logging Exception Handler" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.LoggingExceptionHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
                              logCategory="General" eventId="100" severity="Error" title="Enterprise Library Exception Handling"
                              formatterType="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.TextExceptionFormatter, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling"
                              priority="0" />-->

I am inclined to say something is wrong in the configuration of Logging Exception Handler. The configuration section was added using the Enterprise Library 6.0 configuration tool. I am not sure why Exception Policy Factory does not throw an exception if the configuration is incorrect. Also, I compared my configuration with several working samples on the internet and they are identical to my settings with the exception of an older version of Enterprise Library reference.

I'll retry this in Ent Library 5 and see if I can find out something. In the meantime, I'll really appreciate any help with this issue. Thanks in advance.
0
Comment
Question by:shekhar_shashi
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
3 Comments
 
LVL 3

Accepted Solution

by:
shekhar_shashi earned 0 total points
ID: 39725211
I tried the same solution in Enterprise Library 5 and it worked fine. I did not use the factory class, just used ExceptionPolicy.HandleException but I noticed how the original exception was logged and then wrapped with a custom exception. The configuration is provided below.

<exceptionPolicies>
            <add name="LogAndReplacePolicy">
                <exceptionTypes>
                    <add name="All Exceptions" type="System.Exception, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                        postHandlingAction="ThrowNewException">
                        <exceptionHandlers>
                            <add name="Logging Exception Handler" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.LoggingExceptionHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
                                logCategory="General" eventId="100" severity="Error" title="Enterprise Library Exception Handling"
                                formatterType="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.TextExceptionFormatter, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling"
                                priority="0" />
                            <add name="Wrap Handler" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.WrapHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
                                exceptionMessage="Unexpected Error Occurred." wrapExceptionType="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.ExceptionHandlingException, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
                        </exceptionHandlers>
                    </add>
                </exceptionTypes>
            </add>
        </exceptionPolicies>
0
 
LVL 3

Author Closing Comment

by:shekhar_shashi
ID: 39751529
The solution provided on MSDN worked for me.
0

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

IP addresses can be stored in a database in any of several ways.  These ways may vary based on the volume of the data.  I was dealing with quite a large amount of data for user authentication purpose, and needed a way to minimize the storage.   …
This document covers how to connect to SQL Server and browse its contents.  It is meant for those new to Visual Studio and/or working with Microsoft SQL Server.  It is not a guide to building SQL Server database connections in your code.  This is mo…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers. Hopes this gives you ideas on visualizing your data in new ways ~ Create a calculated field in a query: …

628 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question