SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've made a custom master page for my SharePoint site and it works fine on all the pages that I've checked except for the Web Analytics pages. I get the following error in the logs when I go there:

System.ArgumentException: Could not find the sitemap node with URL '/_layouts/WebAnalytics/WebAppSelection.aspx'

How can I fix my master page so that this error does not occur?

share|improve this question

if you're using custom master page and sharepoint 2010, just remove the control that used '/_layouts/WebAnalytics/WebAppSelection.aspx' as StartingNodeUrl.

<%--<asp:Content ID="Content1" runat="server" ContentPlaceHolderID="PlaceHolderLeftNavBar">
    <SharePoint:VersionedPlaceHolder UIVersion="4" runat="server">
        <div class="ms-quicklaunchouter">
            <div class="ms-quickLaunch" style="width:100%">
                <asp:SiteMapDataSource ID="siteMapDataSource" runat="server" SiteMapProvider="SPXmlContentMapProvider" StartingNodeUrl ="/_layouts/WebAnalytics/WebAppSelection.aspx" ShowStartingNode="false"/>

Control Location:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\WebAnalytics\Report.aspx

share|improve this answer

Here's a quick fix

Open this file:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\WebAnalytics\Report.aspx





Note: This will force the analytics report to use v4.master instead of your custom master page, so you will lose your customized UI/branding when viewing analytics.

share|improve this answer
up vote 0 down vote accepted

I found instructions in this post on how to fix the problem. It turns out that I had moved my QuickLaunchDataSource before the TopNavigationDataSource. Once I moved the two controls into the correct order everything worked fine on that page.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.