Troubleshooting SharePoint 2013 Web Analytics

Examining SharePoint’s Popularity Trends & Popularity and Search Reports


Web Analytics in SharePoint 2010 is now known as Popularity Trends, and, in SharePoint 2013, it’s known as Popularity and Search Reports. The rename comes at a time when Microsoft moved the analytics functionality to be a part of the search component.

This is a troubleshooting guide that will give you an overview of all the different components for the analytics, hopefully aiding in identifying where the break down is inside of the process. I will focus mainly on the Popular Trend’s Usage Reports.


Ensure that there is traffic to the site, not just from administrative users. In some cases, SharePoint will not log administrative accounts page requests. If this is the case, browse the site with a non-administrative or non-service account and make sure to traverse the sites content pages and libraries and lists.

Make sure Alternate Access Mapping is configured correctly.

(SharePoint 2013 Server) Ensure that Reporting is turned on.  This can be found under Site Settings -> Manage site Features. Look for Reporting, not Reporting Service. If it is not Active, turn it on. If you do not see it, don’t worry – it should be fine as I’ve seen sites function without this feature.

Ensure that Reporting is turned on

Configure usage and health data collection:

Ensure that Enable usage data collection is enabled.

Check under the Events to Log: that Analytics Usage, Feature Use, and Page Requests are also selected.

Configure usage and health data collection

Ensure that Enable health data collection is enabled.

Enable health data collection is enabled

Ensure that under Log Collection Schedule the two jobs Microsoft SharePoint Foundation Usage Data Import and Microsoft SharePoint Foundation Usage Data Processing are both there.

Check their jobs schedule: Microsoft SharePoint Foundation Usage Data Import should run every five minutes and Microsoft SharePoint Foundation Usage Data Processing runs daily.

Check if those two jobs are failing: While still on the same screen where we checked the schedule, go to Job History on the left. If you look at the view and it says Service change it to Failed Jobs. Go through the failed jobs and look to see if you see the two jobs listed above.


After we checked and made sure the jobs are healthy and running, let’s make sure Search is functioning properly. Since the search function now does the Analytics, it is vital that the site collection is crawled and search results are coming up fine on the site.

To check Search: Go to System Settings, under Servers, click Manage Services on Server. On the Service on Server, find SharePoint Server Search and click it. On the next screen, under Search Service Applications select the Search Service Application. Now you should be on the Search Service Application: Search Administration menu.
On this screen look under the Search Application Topology for your Analytics Reporting Database.

On the left side of the page, look for Content Sources under Crawling. Select it to go to the Search Service Application: Mange Content Sources page.

Mange Content Sources

Select the Local SharePoint Site and make sure that the URL of the site in question is in the Start Address box. Make sure if the site is httpS that it is httpS in the box as well.

Make sure the site is httpS

After we made sure search is set up correctly, make sure that the site is returning results when you run a do a search on the site.

Lastly, we need to make sure that the search service account is a member of WSS_WPG group.

So, after checking all of those components, we will need to dig deeper to find out what is going on with the Analytics.

Usage File Creation

(typically found C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\RequestUsage)

In the logging folder, we need to find a folder called RequestUsage. In this folder, if healthy and working correctly, we will see a *.tmp file and periodically a *.usage file being generated. If there is no file being created in here then the site is not listening for page requests.

If there is no file in here being generated make sure the site has some traffic to it, so browse the site, and check the folder periodically.

RequestUsage folder

The Microsoft SharePoint Foundation Usage Data Import timer job looks in this folder and takes *.usage file and imports the data to the Event Store.

The Event Store

(typically found at C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\)

The Event Store can be a chore to find, because the folder before it consists of a name with a GUID in it. If you look at your server’s shares, you’ll see it in there. In some cases, you can navigate directly from there to folder, but in other cases you cannot and will have to find it manually. Usually, I run a search for this folder by searching the computer for Analytics or EventStore. In the picture below you can see the “Analytics_(GUID)” share.

The Event Store Analytics_(GUID)

Once you find the event store, we want to make sure that it is creating folders with data in them. The folders are names based on their date. Inside the folders, you should find some .log files.

Event Store .log files

Not everything that gets passed from the RequestUsage folder gets put into the Event Store data files. Some of the information does get filtered out.


Next we must check that SQL is logging analytics data. To do this open up SQL and create a new query your logging database. We want to see if this is getting updated every five minutes by the data import timer job, so re-run the query below every five minutes to check for an increase in the row count.

Select userlogin,* from dbo.RequestUsage (nolock) where RequestType=’GET’ order by RowCreatedTime desc

Select count (*) from RequestUsage (nolock)


We broke down the analytics reporting function into Configuration of the Health and Data Collection, Search, Usage Request, Event Store, and SQL. Reviewing each competent can determine a point of failure in the process and focus on fixing the broken component. There is still much more to the reporting process that I haven’t gone into such as the Search Queries, but that is for a different day…

2014-04-18T09:45:55+00:00 April 18th, 2014|


  1. Badajoz April 29, 2014 at 9:24 pm - Reply

    Very helpful – thanks.

  2. Google July 13, 2014 at 2:58 pm - Reply

    Good article. I’m facing some of these issues as well..

  3. Paul September 2, 2014 at 5:17 pm - Reply

    Do you have to have your SharePoint visual interface in 2013? I have SharePoint 2013 sites, but they still have the 2010 visual interface. I can see to get the Popularity Trends menu options to appear in the 2010 interface.

  4. Mike September 10, 2014 at 2:41 pm - Reply

    Thanks for this great article! Easy to follow, makes sense, etc. Perfect for those of us new to SP2013… and not assuming that we are all knowing when you mention a folder, service, or other location.

  5. Kieran Sullivan November 21, 2014 at 11:46 am - Reply

    Thanks for this info – this helps but the reports are still missing something. It’s as if Microsoft decided to concede the analytics market to Google.

    We use SharePoint on prem and Google Analytics isn’t an option for us because there’s no data security. We now use Angelfish Software for web analytics – you mentioned it in one of your other articles:

  6. saritha December 16, 2014 at 10:46 am - Reply

    Great Post. I was facing the issue that till 12th of dec all my usage was logging but after i cleaned up the log files from 15/logs from 13th the usage.aspx is showing all are 0’s.
    I followed all of the above steps and looks like everything is looks good *.usage file is not present in 15/logs/RequestUsage. It is not generating automatically. Can you suggest what would be the problem and solution for this.

  7. SJ February 25, 2015 at 3:33 pm - Reply

    You have writen a great article.
    I was having this issue where my usage reports show 0 hits.
    I followed your article and checked all the pointers and upto Event Store thing everything works fine. But in the event store there are not files that are being created. I see data in SQL Database, but i guess other than event Store nothing is working.
    I would appreciate if you can help me in that.
    Thanks in Advance.

  8. Gus June 11, 2015 at 8:10 pm - Reply

    Thanks for sharing and great write-up. What ended up fixing my problem is to change the log folder to a different location. I am not sure exactly why but it worked, as I verified the log database started populating with data along with RequestUsage folder. Hope this helps others as well.

  9. Mary November 9, 2015 at 9:27 am - Reply

    Hi Great information on how to troubleshoot analytics reporting in SP2013.
    I am working with foundation version – and was told by Microsoft Directly 2 different stories about this feature:
    1. it is available – got it configured correctly but did not get it working: error message: A web analytics report is not available for this site. Usage processing may be disabled on this server or the usage data for this site has not been processed yet.
    2. I called back via a service call told the analytics feature is not available by Microsoft Foundation 2013. I followed your steps and all configured correctly and I am getting Data in the ReportUsage table of the logging database.

    However there is no data being transmitted in or out of the EventStore folder on the Server.

    This is the only site I seem to be remotely close to an answer.
    Any advice greatly appreciated.


  10. Hugo van Dokkum November 24, 2015 at 8:28 am - Reply


    Hi Mary,

    I had the same issue. I solved it by following the work-around in this article:

    It seems that you have no receiver.

    This solved the Eventstore issue for me, I have data coming in my database. But still I cannot get any reports out of SharePoint 2013. They are empty or not generating at all. So frustrating…

  11. Cannot Find "Popularity Trends" and "Popularity and Search Reports" » Rent in London July 31, 2016 at 8:04 am - Reply

    […] I cannot find it in my farm. Google provided me with this usefule article on how to troubleshoot Popularity Trends issues But even after I applied every single step in the […]

  12. Joel September 29, 2016 at 11:09 am - Reply

    What’s the issue is the wss_logging DB is empty and there are no usage files in the RequestUsage folder? I’ve confirmed the permissions for the folder and the DB. I’ve already tried re-creating the usage service.

Leave A Comment