locked
How to troubleshoot issue with Usage analysis processing RRS feed

  • Question

  • We seem to having problem with Office SharePoint Usage Analytics Log Import & ce SharePoint Usage Analytics Processing. This seems to have been caused after OS patching by Infrastructure team last weekend, wherein we do had problem with accessibility to 2 of WFE servers while the other 2 WFE were serving to user requests. Current status of jobs are;

    Office SharePoint Usage Analytics Log Import  Aborted  0% 
    Office SharePoint Usage Analytics Processing  Initialized  0%

    Upon checking SSP DB, table ANLDay shows saturday's date, as indicated processing stopped working since patching.

    Options i think might help are;

    1. Restart the Usage analysis processing from SSP & Central admin pages
    2. Disable and enable the respective jobs from Timer job definition page

    Anything else please suggest.

    Thank you in advance for your taking time to read & answer.

    Regards,
    Ram


    Ramakrishna Pulipati SharePoint Consultant Logica Bangalore, INDIA
    Wednesday, August 24, 2011 6:52 AM

Answers

  • Hi Ram,

     

    Please try the following steps to check whether it works:

    1.       Stop the Timer services (Click Start->Administrative Tools->Services->Windows SharePoint Services Timer, click stop)

    2.       Back up and edit the Cache.ini file
    a. Locate and then double-click the following folder:  \Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID(set to show the hidden files and folders)
    b. Back up the Cache.ini file.
    c. Delete all the XML configuration files in the GUID folder (do a backup to other folder before delete).
    d. Double-click the Cache.ini file, select All and click delete, click Save and exit.

    3.       Start the Timer service (Click Start->Administrative Tools->Services->Windows SharePoint Services Timer, click start)

    The file system cache is re-created after performing this procedure, make sure that you perform this procedure on all servers in the server farm.

     

    Go to Central Administration->Operations->Timer job status to check whether the status is Succeeded.

     

    Thanks,
    Qiao Wei

    • Marked as answer by Reach Ram Wednesday, September 21, 2011 4:12 AM
    Monday, August 29, 2011 10:35 AM
    Moderator
  • Hi,

    Restrat timer services on all servers in your farm. When this timer job runs check switch to verbose mode of logging.

    In the ULS logs check if you get any warning or error.

    I hope this will help you out.


    Thanks, Rahul Rashu
    • Marked as answer by Reach Ram Wednesday, September 21, 2011 4:12 AM
    Wednesday, September 7, 2011 5:40 AM

All replies

  • Hi Ram,

     

    Please try the following steps to check whether it works:

    1.       Stop the Timer services (Click Start->Administrative Tools->Services->Windows SharePoint Services Timer, click stop)

    2.       Back up and edit the Cache.ini file
    a. Locate and then double-click the following folder:  \Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID(set to show the hidden files and folders)
    b. Back up the Cache.ini file.
    c. Delete all the XML configuration files in the GUID folder (do a backup to other folder before delete).
    d. Double-click the Cache.ini file, select All and click delete, click Save and exit.

    3.       Start the Timer service (Click Start->Administrative Tools->Services->Windows SharePoint Services Timer, click start)

    The file system cache is re-created after performing this procedure, make sure that you perform this procedure on all servers in the server farm.

     

    Go to Central Administration->Operations->Timer job status to check whether the status is Succeeded.

     

    Thanks,
    Qiao Wei

    • Marked as answer by Reach Ram Wednesday, September 21, 2011 4:12 AM
    Monday, August 29, 2011 10:35 AM
    Moderator
  • Hi Qiao Wei,

    Thank you

    We tried this method, it didn;t help. Status didn't change, it stays in 'Initializing...'

    Regards,
    Ram


    Ramakrishna Pulipati SharePoint Consultant Logica Bangalore, INDIA
    Tuesday, August 30, 2011 8:48 AM
  • Hi,

    Check if the farm account(used to run the timer job) has sufficient priviladges in the database or not.

     


    Thanks, Rahul Rashu
    • Marked as answer by Emir Liu Monday, September 5, 2011 3:33 AM
    • Unmarked as answer by Reach Ram Wednesday, September 7, 2011 5:12 AM
    Tuesday, August 30, 2011 10:09 AM
  • Hi Rahul.

    Thank you.

    Checked! There is no change in the Farm admin a/c or privilages.

    Regards,

    Ram


    Ramakrishna Pulipati SharePoint Consultant Logica Bangalore, INDIA
    Wednesday, September 7, 2011 5:13 AM
  • Hi,

    Restrat timer services on all servers in your farm. When this timer job runs check switch to verbose mode of logging.

    In the ULS logs check if you get any warning or error.

    I hope this will help you out.


    Thanks, Rahul Rashu
    • Marked as answer by Reach Ram Wednesday, September 21, 2011 4:12 AM
    Wednesday, September 7, 2011 5:40 AM