I was eager to see what Microsoft has done with reports in new SharePoint. But when I tried to enable and see these reports, I got an error 403 saying this page is forbidden. (I’m SharePoint administrator.)

This problem is known and is explained here: http://support.microsoft.com/kb/913384.
The article references a patch for solving this problem. I downloaded it but the problem was still present.

The workaround solution is described here by Matthew McDermott: http://mindsharpblogs.com/matthew/archive/2007/01/27/1506.aspx

To fix it: log in to your SharePoint Central Administration page with the account that is running your SharePoint application pool. This is the only account that will allow you to enable „Enable advanced usage analysis processing”.
The usage reports can be found on Site Settings for your site collection.

12 Comments

  1. http:// Says

    Though i have configured portal usage reporting as per the below mentioned article

    http://technet2.microsoft.com/Office/en-us/library/5233cf43-6a8f-40cb-9014-0724600e7e381033.mspx?mfr=true

    still my usage report is blank….
    what else do i need to do besides this ?

  2. toni Says

    Well, that is all you need to configure for use analysis.

    Data will not be displayed right away, but after usage analysis processing.

    If you report is still missing make sure that all SharePoint services are running and that there are not reporting or services related errors in your event log.

  3. http:// Says

    Hi, we got another problem with the usage analysis tools. Our works council does not want stats on which user visits a site to be displayed in the site usage report (due to privacy reasons).

    This means that we only want to have Pages, OS, Browser and Referrerer Url in the dropdown menu and remove user. An alternative would be to have the user name made anonymous somehow in the view.

    Apperantly the logging process and usage analysis processing are deeply integrated into Microsoft.SharePoint.ApplicationPages.dll and sharepoint.dll so I see no direct way to change it.

    Does anyone have an idea for a workaround?

  4. http:// Says

    I don’t know your configuration, but logging in with the SSP application pool account didn’t do the trick for me. What did work, though, was logging in with the SSP service account.

    Perhaps you’re running your app pool and SSP service with the same account?

  5. http:// Says

    This was bugging me, so I played around a little more. The “workaround” (actually not a workaround, since this is how things should work) is to grant the account under which you want to operate the “Manage Usage Analytics” permission (from “Personalization services permissions”) from within the SSP. Once you do so, the 403 permission errors will disappear when trying to change the advanced processing checkbox.

  6. http:// Says

    THANK YOU SEAN!!! The September 14th post was what worked for me! Our site had a person who was the original SSP and only his name was set up for this permission. Once I added our System Account and gave it the permissions shown, it allowed me to check the box!!! THANK YOU!!!

  7. http:// Says

    THANKS Sean – I was getting a 403 Forbidden error until I allowed myself(!) Manage Usage Analytics permission.

  8. http:// Says

    THANKS Sean – I was getting a 403 Forbidden error until I allowed myself(!) Manage Usage Analytics permission.

  9. SharePoint Usage Says

    When it comes to SharePoint Usage Reports – see “CardioLog” , it’s like webtrend, but specfically designed for SharePoint, and a free version of the solution is about to be released.

    Uri,
    Intlock.

  10. http:// Says

    Hi All,
    I am able to see the Search Usage Reports, and am trying to figure out if there is a programmatic way to retrieve these reports and display them using SSRS. Any light on this front will be appreciated.

    Thanks!

  11. http:// Says

    @Shubham: Haven’t tried that, but there are some classes that might help. Check your WSS/SharePoint SDK.

    Here is sample code:
    SPSite oSiteCollection = SPContext.Current.Site;
    SPSite.UsageInfo oUsageInfo = oSiteCollection.Usage;
    Int64 int64DiscussionStorage = oUsageInfo.DiscussionStorage;
    Int64 int64Storage = oUsageInfo.Storage;
    Int64 int64Bandwidth = oUsageInfo.Bandwidth;
    Int64 int64Hits = oUsageInfo.Hits;
    Int64 int64Visits = oUsageInfo.Visits;

  12. lds1ph Says

    Thanks to post#8 above. Been looking for a solution for this issue. It works.

Leave a Reply