Connection string Sitefinity 4

2 posts, 0 answers
  1. Gerrit
    Gerrit avatar
    33 posts
    Member since:
    Jul 2010

    Posted 24 May 2011 Link to this post

    Hi guys,

    I'm suddenly getting an error like this :

    Resolution of the dependency failed, type = "Telerik.Sitefinity.Configuration.ConfigManager", name = "XmlConfigProvider".
    Exception occurred while: Calling constructor Telerik.Sitefinity.Configuration.ConfigManager(System.String providerName).
    Exception is: ResolutionFailedException - Resolution of the dependency failed, type = "Telerik.Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.ExceptionManager", name = "(none)".
    Exception occurred while: while resolving.
    Exception is: InvalidOperationException - The type ExceptionManager cannot be constructed. You must configure the container to supply this value.
    -----------------------------------------------
    At the time of the exception, the container was:


      Resolving Telerik.Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.ExceptionManager,(none)


    -----------------------------------------------
    At the time of the exception, the container was:


      Resolving Telerik.Sitefinity.Configuration.ConfigManager,XmlConfigProvider
      Calling constructor Telerik.Sitefinity.Configuration.ConfigManager(System.String providerName)


    when trying to get the connection string, anyone else got the same error?
    It used to work fine, but since this morning I've been getting this, I did not upgrade of anything.

    The line where the code gives the error is:
    Telerik.Sitefinity.Configuration.ConfigManager cfgManager = Config.GetManager();

    I also tried :
    string a = Config.Get<DataConfig>().ConnectionStrings[ "Sitefinity" ].ConnectionString;

    Please help!!

    Thanks in advanced!

  2. Vlad
    Admin
    Vlad avatar
    1 posts

    Posted 27 May 2011 Link to this post

    Hi Gerrit,

    Can you provide more info about the scenario you are using:
    1. When this code is invoked in the Application life cycle?
    2. Do you have any custom code on application start, which overrides the default Sitefinity behavior? Maybe in the Global.asax?
    3. Do you know about any changes before this error started thrown?
    4. Which is the version of Sitefinity?

    Finally, you can send us your project, so we could investigate it locally.

    Best wishes,
    Vlad
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top