More in this section

Forums / Bugs & Issues / Unexplained errors

Unexplained errors

2 posts, 0 answered
  1. Nick
    Nick avatar
    113 posts
    Registered:
    21 Oct 2008
    13 Jul 2011
    Link to this post
    Hi

    We recently launched a Sitefinity site (4.1.1395.0) and whilst mostly ok we are getting unexplained errors:

    This one happened after one of the admins edited an existing page title and published the page: On publish the whole site broke with this error:

    The type ExceptionManager cannot be constructed. You must configure the container to supply this value.

    Stack Trace: 

    [InvalidOperationException: The type ExceptionManager cannot be constructed. You must configure the container to supply this value.]
       Telerik.Microsoft.Practices.ObjectBuilder2.DynamicMethodConstructorStrategy.GuardTypeIsNonPrimitive(IBuilderContext context, SelectedConstructor selectedConstructor) +161
       Telerik.Microsoft.Practices.ObjectBuilder2.DynamicMethodConstructorStrategy.PreBuildUp(IBuilderContext context) +136
       Telerik.Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context) +194
       Telerik.Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlanCreatorPolicy.CreatePlan(IBuilderContext context, NamedTypeBuildKey buildKey) +108
       Telerik.Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context) +137
       Telerik.Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context) +194
       Telerik.Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides) +163
    
    [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)
    etc...

    The other issue that has happened a couple of times is the site suddenly and without any trigger that we can identify is this an object not set to reference of an object error:

    Object reference not set to an instance of an object.
       at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
       at System.Collections.ObjectModel.KeyedCollection`2.AddKey(TKey key, TItem item)
       at System.Collections.ObjectModel.KeyedCollection`2.InsertItem(Int32 index, TItem item)
       at Telerik.Sitefinity.Abstractions.ProvidersCollection`1.InsertItem(Int32 index, TProvider item)
       at System.Collections.ObjectModel.Collection`1.Add(T item)
       at Telerik.Sitefinity.Data.ManagerBase`1.SetProvider(String providerName, String transactionName)
       at Telerik.Sitefinity.Data.ManagerBase`1..ctor(String providerName, String transactionName)
       at Telerik.Sitefinity.Configuration.ConfigManager..ctor()

    In both these cases recycling the application pool has immediately got the site up and running again. 

    However, this is a corporate website for a big UK clinet of ours, and they want to know why the site appears to just break, and I haven't got any answers for them.

    Does anyone know what the cause of either of these might be?

    Thanks
  2. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    13 Jul 2011
    Link to this post
    Hi Nick,

    There was an issue in 4.1 SP1 which seems to be related to your scenario and has been fixed in 4.1 SP2 ( build 1501 ). In order to be sure that this is the same issue, please look for the following line at the bottom of the stack trace when you get one of the exceptions:

    Telerik.Sitefinity.Security.SecurityManager.UpdateCookies

    If you can see the line ( if you don't please make a screenshot of the full stack trace and attach it to your reply ) it means that you are encountering the bug we discovered in 1395 and was fixed in 1501.

    Kind regards,
    Victor Velev
    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
2 posts, 0 answered