Error FindSiteMapNodeFromKey : parameter cannot be null afte

Posted by Community Admin on 05-Aug-2018 08:06

Error FindSiteMapNodeFromKey : parameter cannot be null after migration

All Replies

Posted by Community Admin on 29-Mar-2012 00:00

  • I work with a Web application in asp.net with sitefinity included. I work like this with the sitefinity 3.7 sp4 with no problem. Last week I did the migration to sitefinity 5.0, I did the method explain there http://www.sitefinity.com/blogs/joshmorales/posts/11-11-22/migrating_sitefinity_3_to_4_deep_dive_preparation.aspx .

    The migration was completed and I retrieve all my pages and the blog.

    After the migration, I create a new page and publish it without error. But when I tried to create/ edit or simply display my site, I received this error message

    I don’t know if the problem is during the migration or after but to fixed this, I need to restart my iis.



    Value cannot be null.
    Parameter name: key

    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: key

    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: key]

       Telerik.Sitefinity.Web.SiteMapBase.FindSiteMapNodeFromKey(String key, Boolean ifAccessible) +1594

       Telerik.Sitefinity.Web.PageSiteNodeCollection.UpdateNode(PageSiteNode& node) +228

       Telerik.Sitefinity.Web.PageSiteNodeCollection.get_Item(Int32 index) +120

       Telerik.Sitefinity.Web.InnerEnumerator.get_Current() +25

       Telerik.Sitefinity.Web.SiteMapBase.GetChildNode(PageSiteNode parent, String urlName) +161

       Telerik.Sitefinity.Web.SiteMapBase.FindSiteMapNode(String rawUrl, Boolean ifAccessible, Boolean& isAdditionalUrl, String[]& urlParameters) +1016

       Telerik.Sitefinity.Web.SitefinityRoute.GetRouteData(HttpContextBase httpContext) +184

       System.Web.Routing.RouteCollection.GetRouteData(HttpContextBase httpContext) +355

       System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context) +75

       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80

       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +270

     


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

Posted by Community Admin on 02-Apr-2012 00:00

Hi Jan,

I have answered you in the support ticket.

All the best,
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

Posted by Community Admin on 02-Jul-2012 00:00

can you pls provide the link to the answer

Posted by Community Admin on 12-Aug-2012 00:00

What is the answer for this? Running into this and could use the answer instead of buried in someone's private support ticket.

Posted by Community Admin on 15-Aug-2012 00:00

Hello guys,

The problem in this case was related to the page nodes, specifically having more than 100 page nodes under one node. 

So in order to fix the issue, a modification to the webconfig needs to be made, so the section between the sitemap tags looks like this:

<siteMap defaultProvider="SitefinitySiteMap">
     <providers>
       <add name="SitefinitySiteMap" type="Telerik.Sitefinity.Web.SitefinitySiteMap, Telerik.Sitefinity" taxonomyProvider="OpenAccessDataProvider" pageTaxonomy="Pages" rootNode="FrontendSiteMap" pageProvider="OpenAccessDataProvider" maxPageNodes ="11900"/>
     </providers>
   </siteMap>

Basically the property called maxPageNodes is added, which allows to have more than 100 page nodes under a single node.

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

This thread is closed