Work Item Manager - Unhandled exception on startup (I know why!)

3 posts, 1 answers
  1. Jake
    Jake avatar
    4 posts
    Member since:
    Jul 2012

    Posted 26 Mar 2012 Link to this post

    The Telerik Work Item Manager application uses Log4Net as its logging component. It defines a configuration section for Log4Net inside the app.config file. The problem I'm having is, we use Log4Net extensively here at this company, and we've already defined Log4Net blocks inside our machine.config files. When Work Item Manager starts up, it sees these conflicting configuration blocks and throws an exception.

    Can someone explain how I can work around this to start up Work Item Manager? Perhaps there's a way to disable Log4Net for WIM so it doesn't initialize those components? It seems silly that just because I have Log4Net preconfigured on my machine that I'm not allowed to use this application.
  2. Answer
    Joel
    Admin
    Joel avatar
    300 posts

    Posted 28 Mar 2012 Link to this post

    Hi Jake,

    If you have log4net configured in the machine.config, to get the app to start you will need to comment out or remove the log4net config sections from the WIM.exe.config and Dashboard.exe.config files.  This would include the <section name="log4net"...> element as well as the <log4net> element.  These config files are located in the installation folder which is usually c:\Program Files (x86)\Telerik\Work Item Item Manager 2010.

    WIM and Dashboard both look to their own config files to for the logging configuration so removing these elements will effectively turn off logging for these applications.  The apps should run fine without logging, however, if logging is turned off it will be much more difficult for us to troubleshoot any issues you run into in the future.

    Regards,
    Joel
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

  3. UI for WPF is Visual Studio 2017 Ready
  4. Jake
    Jake avatar
    4 posts
    Member since:
    Jul 2012

    Posted 28 Mar 2012 Link to this post

    Oh, cool... I thought I had done that already, but maybe I mangled one of the .config files because it didn't work the first time I tried it. I repaired the installation and tried it just now, though, and it works!

    Thanks for your help!
Back to Top