1-888-365-2779
+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / 4.3.1885 Upgrade error from 4.1.1339

4.3.1885 Upgrade error from 4.1.1339

2 posts, 0 answered
  1. Larry Miclette
    Larry Miclette avatar
    10 posts
    Registered:
    19 Nov 2009
    18 Nov 2011
    Link to this post
    We are encountering an error updating our site from 4.1.1339  to 4.3.1885 and haven't been able to figure out what the root cause is.  We're hoping someone can help us pinpoint the problem and has a solution for us to apply.

    We were able to upgrade the site using Sitefinity Project Manager.  In VS 2010 the solution compiles correctly and we have no errors or warnings to review.

    So once we run the site (with or without debugging) we are getting this following screen error.

     

    Server Error in '/' Application.

    Value cannot be null.
    Parameter name: type

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.ArgumentNullException: Value cannot be null.
    Parameter name: type

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [ArgumentNullException: Value cannot be null.
    Parameter name: type]
       System.Activator.CreateInstance(Type type, Boolean nonPublic) +9643414
       System.Activator.CreateInstance(Type type) +6
       Telerik.Sitefinity.Data.CacheDependency.Initialize() +204
       Telerik.Sitefinity.Data.CacheDependency..cctor() +22
    
    [TypeInitializationException: The type initializer for 'Telerik.Sitefinity.Data.CacheDependency' threw an exception.]
       Telerik.Sitefinity.Data.CacheDependency.Notify(Object[] items) +0
       Telerik.Sitefinity.Configuration.Data.XmlConfigProvider.SaveSection(ConfigSection section) +221
       Telerik.Sitefinity.Configuration.ConfigManager.SaveSection(ConfigSection section) +58
       Telerik.Sitefinity.Services.InstallContext.SaveChanges(Boolean clean) +168
       Telerik.Sitefinity.Services.InstallContext.SaveChanges() +31
       Telerik.Sitefinity.Services.SystemManager.Initialize() +970
       Telerik.Sitefinity.Abstractions.Bootstrapper.RegisterRoutes(RouteCollection routes) +412
       Telerik.Sitefinity.Abstractions.Bootstrapper.Bootstrap() +324
       Telerik.Sitefinity.Web.SitefinityHttpModule.Init(HttpApplication context) +112
       System.Web.Routing.UrlRoutingModule.System.Web.IHttpModule.Init(HttpApplication application) +10
       System.Web.HttpApplication.InitModulesCommon() +80
       System.Web.HttpApplication.InitModules() +43
       System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +828
       System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +304
       System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107
       System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +327
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1


  2. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    23 Nov 2011
    Link to this post
    Hello Larry Miclette,

    Can you tell me what steps you followed when upgrading from 4.1?

    If you are using Sitefinity 4.1 and want to upgrade to 4.3, the correct procedure will be:

    4.1 1339 -> 4.1 SP3 1574 - then make sure the site is running, the modules are initialized.

    4.1 SP3 1574 - 4.2 / 4.2 SP1 - verify that everything works.

    4.2/4.2 SP1 - 4.3.

    This process is highly recommended due to the fact that there were a lot of changes during the different versions of Sitefinity. Skipping any of the steps or directly upgrading may result in corrupted project.

    The problem is most likely to be coming from some corrupted data in the project, as a result of the direct upgrade. Can you tell us if you have access to the backend?

    Best wishes,
    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