Site Web Analytics reports - unexpected error
-
Monday, May 21, 2012 10:19 AM
Hello,
After clicking on "Site Web Analytics reports", I get "An unexpected error has occured". Here is detailed error description:
05/21/2012 11:50:12.13 w3wp.exe (0x0718) 0x1600 SharePoint Foundation Runtime tkau Unexpected
System.ArgumentException: Value does not fall within the expected range.
at Microsoft.SharePoint.Utilities.SPUtility.ParseDate(SPWeb web, String stDateTime, SPDateFormat format, Boolean bToUTC)
at Microsoft.SharePoint.Administration.SPUsage.UsageDetailsInfo.get_Dt()
at Microsoft.SharePoint.SPWeb.GetUsageData(SPUsageReportType itemType, SPUsagePeriodType periodType)
at Microsoft.SharePoint.ApplicationPages.UsageDetailsPage.GetReportData()
at Microsoft.SharePoint.ApplicationPages.UsageDetailsPage.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ad3714f8-52a3-405c-a25b-aa66b9deffb6Has anyone ever stumbled upon this one or something similar?
Thanks, MiToZ
All Replies
-
Monday, May 21, 2012 2:46 PM
Hello Mitoz,
make sure that you have web analytics configured in Central Administration.
Central Admin > Monitoring > Configure usage and health report and make sure that the "Enable usage data collection" is checked.
Cheers,
Daniel Bugday
Microsoft Community Contributor, Member of Microsoft Extended Expert Team, MCT, MCTS/MCPD SharePoint 2007/2010, SQL MCDBA, MCSE
Blog: SharePoint By Bugday
Twitter: Follow me on Twitter
Technet: My Ask The Expert Area On Technet
Founder of SharePoint Forum -
Monday, May 21, 2012 7:05 PM
Hello Daniel,
Everything is configured as it should be on that page. I can see that data is available through Central Administration "Slowest Pages" and "Top Active Users" page, but accessing Web Analytics Report through regular site throws "Unexpected error". Any other idea?
Thanks, MiToZ
- Edited by MiToZ Thursday, September 27, 2012 4:06 PM
-
Thursday, September 27, 2012 4:07 PMWe still didn't manage to solve this problem. Does anyone else have an idea?

