none
Usage reports no data RRS feed

  • Question

  • Hello,

    Hope someone can shed some light as I'm out of options here. In a SharePoint 2013 farm (June 2015 CU) Usage reports started to show 0 (no data) for the last 2 months.

    Below are the steps I've confirmed with no luck. 

    1. Confirmed 2 timer jobs  "Microsoft SharePoint Foundation Usage Data Import" and "Microsoft SharePoint Foundation Usage Data Processing" are running and not failing. Manually re-ran both of these timer jobs
    2. Enabled Usage data collection is checked
    3. Some events checked
    4.  Search Service Account does have 'read access to term store'
    5. Search Host Controller Service running on the Servers (4 out of the 7 servers farm) where there is a Search Component(s)
    6. Crawling is working fine hence search is working as expected
    7. Went through Matt's article to confirm EventStore is getting populated. Don't know any easy way of checking the Logging database. SQL statement he has takes way too long to let it run in Prod...which might be an indication I've data :-) 
    8. Confirmed ImportProgress.ini files has -1 value as per this article. 
    9. Receivers defined as per this one. 
    10. Tried switching retention period from default 14 to 7 days as I originally had 8319 errors. 
    11. Also changed MaxTotalSizeInBytes to 12 GB from default 6....while created a new SQL usage DB
    12. Found out 'Usage and Health Data Collection Service Application Proxy' was stopped ... re-provisioned with no luck
    13. performed IISRESET on Search service servers
    14. Deleted the "Usage and Health Data Collection Service Application" from CA and re-enabled through 'Configure Usage and health data collection' ... re-ran timer jobs in step 1 above. Still no usage data
    15. it's a Production farm and there are tons of users hitting constantly

    Some observations: 

    1. Two timer jobs are failing ... could not figure out a resolution to those yet. Included the ULS logs below. 

    Search Custom Dictionaries Update and Query Classification Dictionary Update for Search Application. 

    2. When running Get-SPUsageApplication | fl. 

    it shows my current UsageDatabase name correct but under the attribute Name and Displayname it shows "WSS_UsageApplication" which I believe is the default DB name for this service application. Not sure why?. 

    Appreciate any suggestion!

    UpdatedConcurrencyException: The object PersistedCustomDictionaryDeploymentSettings Name=Search Custom Dictionaries Update for Search Application 52479686-6252-440e-b7bc-6dd3845c978a. was updated by another user.  Determine if these changes will conflict, resolve any differences, and reapply the second change.  This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread. Previous update information: User: Domain\svc_spfarm Process:OWSTIMER (11644) Machine:DETMSSP13APP01 Time:January 24, 2016 12:10:43.0000  Current update information: User: Domain\svc_spfarm Process:OWSTIMER (11696) Machine:DETMSSP13APP01 Time:June 22, 2016 03:30:06.4005
    
    Custom dictionary deployment timer job failed. SearchComponent: OWSTIMER.EXE, SearchServiceApplication: {52479686-6252-440e-b7bc-6dd3845c978a}, FlowName: Microsoft.CustomDictionaryDeployment, CorrelationId: {42bc889d-1439-2049-35b0-6271e363c4bb}, Failure: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object PersistedCustomDictionaryDeploymentSettings Name=Search Custom Dictionaries Update for Search Application 52479686-6252-440e-b7bc-6dd3845c978a. was updated by Domain\svc_spfarm, in the OWSTIMER (11644) process, on machine DETMSSP13APP01.  View the tracing log for more information about the conflict.    
     at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)    
     at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()    
     at Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition.DoExecute(CtsConnection connection)    
     at Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition.ExecuteTimerJob().
    
    Custom dictionary deployment timer job failed. SearchComponent: OWSTIMER.EXE, SearchServiceApplication: {52479686-6252-440e-b7bc-6dd3845c978a}, FlowName: Microsoft.CustomDictionaryDeployment, CorrelationId: {42bc889d-1439-2049-35b0-6271e363c4bb}, Failure: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object PersistedCustomDictionaryDeploymentSettings Name=Search Custom Dictionaries Update for Search Application 52479686-6252-440e-b7bc-6dd3845c978a. was updated by Domain\svc_spfarm, in the OWSTIMER (11644) process, on machine DETMSSP13APP01.  View the tracing log for more information about the conflict.    
     at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)    
     at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()    
     at Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition.DoExecute(CtsConnection connection)    
     at Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition.ExecuteTimerJob().
    
    The Execute method of job definition Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition (ID 56990f97-3387-404b-ba1c-85baf03953d9) threw an exception. More information is included below.  Failed to run flow Microsoft.CustomDictionaryDeployment. Correlation Id: 42bc889d-1439-2049-35b0-6271e363c4bb.



    BlueSky2010
    Please help and appreciate others by using forum features: "Propose As Answer", "Vote As Helpful" and "Mark As Answer"



    • Edited by BlueSky2010 Thursday, June 23, 2016 6:16 PM added few checked that I've already done
    Wednesday, June 22, 2016 9:23 PM

Answers

All replies

  • Hi,

    First of all check the SharePoint Search Host Controller Service started on every server In the farm. If not start if and do Full Crawl. Usages report service is depends on search service.
    Here please ensure that you have given your search service account read permission to the Managed Metadata Service Application as well.


    KRISHANA KUMAR

    SharePoint Architect

    Mosstechnet-kk.com

     

    Please click "Mark As Answer" if this post solves your problem or "Vote As Helpful" if it was useful


    Wednesday, June 22, 2016 10:02 PM
  • Thanks Krishana for your prompt response!

    I do have Search Host Controller Service running on the Servers (4 of them) where there is a Search Component(s) - not on the 3 servers where there is no Search components. I'm assuming this should be fine as Usage Reports were working fine 2 months before with this topology. Do you think otherwise?

    Sorry forgot to mention Search Service Account does have 'read access to term store'. I'd add these checks to the original post.  

    Anything else you can think of?

    Thanks!


    BlueSky2010
    Please help and appreciate others by using forum features: "Propose As Answer", "Vote As Helpful" and "Mark As Answer"

    Thursday, June 23, 2016 6:13 PM
  • Hi,

    In your error message it says there is some conflicts with data that is trying to access by your Farm Admin account means your configuration database and the Sharepoint server, here server means any WFE server where your request goes that hold the cache data so Can you check by clearing the cache from your WFE server on which the timer service is running needs to be cleared? here is the steps that you need to follow.

    http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance


    KRISHANA KUMAR

    SharePoint Architect

    Mosstechnet-kk.com

     

    Please click "Mark As Answer" if this post solves your problem or "Vote As Helpful" if it was useful

    • Marked as answer by BlueSky2010 Sunday, June 26, 2016 5:51 PM
    Thursday, June 23, 2016 8:47 PM
  • Clearing config cache seems to have done the trick! Million thanks Krishana!!!!

    BlueSky2010
    Please help and appreciate others by using forum features: "Propose As Answer", "Vote As Helpful" and "Mark As Answer"

    Sunday, June 26, 2016 5:51 PM
  • My pleasure and glad your issue resolved, thank you!!

    KRISHANA KUMAR

    SharePoint Architect

    Mosstechnet-kk.com

     

    Please click "Mark As Answer" if this post solves your problem or "Vote As Helpful" if it was useful

    Sunday, June 26, 2016 7:58 PM