none
Microsoft exception management block dlls not compatible with .Net framework 4.6.2 RRS feed

  • Question

  • My web application uses Microsoft exception manager to log exceptions into the eventvwr. The application works fine till framework 4.6.1 but if the application is deployed on a server with framework 4.6.2, the application stops working and the w3wp process crashes causing the app pool to stop. For now, we have changed the code and used log4net instead. The applications work fine on framework 4.6.2 once the exception manager code is removed. Is there a work around to get the previously deployed applications to work simultaneously with the new applications on 4.6.2? We have the target framework key added in the web.config but that is no good.
    Friday, July 7, 2017 12:30 PM

All replies

  • Hi nijcapur,

    Thank you for posting here.

    For your question, when the application is deployed on a server with .net framework 4.6.2, the application stops working, could you provide the error message? 

    As we know, we suggest you to use log4net.

    log4net offers much greater flexibility with regards to the logging output. log4net allows you to configure where your logging output should go (for example: to a file, to the event log, etc.) and allows you to fine-tune what you want to see logged.

    For instance, you want much more diagnostic information on development and test environments while you're only interested in warnings and fatal errors on the acceptance and production environments. With log4net, you can simply configure what you want to be logged, and this can be changed at any time after an application has been deployed.

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, July 11, 2017 10:26 AM
    Moderator
  • Hi Wendy,

    Thank you for your response. We are now using log4Net in our application and it is working fine for us on framework 4.6.2. The problem is that we have multiple applications from our previous versions installed on the same server. So now, when we upgrade the .Net framework to v4.6.2, the new application works fine, but the previous ones fail.

    Since these are previously deployed applications, we cannot really change the logging code for them. We need a workaround to get the previously applications to work with framework 4.6.2.

    Also, our recent findings show that the conflict is with telerik dlls and and the microsoft exception management block dlls(Microsoft.ApplicationBlocks.ExceptionManagement.dll). When we even place a the exception management dlls in the bin of a simple web application with a telerik control, the same issue can be replicated on framework 4.6.2.

    I have attached the application for your refence here https://webfs.protiviti.com/file_pickup/RTS_Support/900c10e217b24122a8cb603059aa932a/

    Regards,

    Nij

    Wednesday, July 12, 2017 6:48 AM
  • Hi nijcapur,

    Does the application with log4Net could be used in .Net Framework 4.6.1?

    For the conflict, we could not solve that, it depends on the telerik dlls and Microsoft.ApplicationBlocks.ExceptionManagement.dll. You could try to use .net framework 4.6.1. 

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, July 14, 2017 6:41 AM
    Moderator