I'm seeing an error

 

But when I check the Job History, I see this:

I can't find anything on this error, does anyone else know?

did you search the ULS logs for the correlation token/ID?

Yes,I hope it pastes well here...

05/20/2015 11:41:01.24  OWSTIMER.EXE (0x25D8)                    0x27D0 SharePoint Foundation          Monitoring                     nasq Medium   Entering monitored scope (Timer Job Usage Analytics Timer Job for Search Application 2489c0ad-60dc-4198-b2ca-7f7941fa3f40). Parent No d0517e35-bd91-4781-8e6d-d61b6a788fd3
05/20/2015 11:41:01.24  OWSTIMER.EXE (0x25D8)                    0x27D0 SharePoint Foundation          Logging Correlation Data       xmnv Medium   Name=Timer Job Usage Analytics Timer Job for Search Application 2489c0ad-60dc-4198-b2ca-7f7941fa3f40 6e49089d-8f0b-a003-60f3-fb58326c4bbd
05/20/2015 11:41:01.24  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                ajjbc Critical UsageAnalyticsTimerJob-2489c0ad-60dc-4198-b2ca-7f7941fa3f40 : Usage Analytics has not completed successfully the last 658 hours. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.31  OWSTIMER.EXE (0x25D8)                    0x27D0 SharePoint Server Search       Analytics                      ag7hh Medium   AnalyticsEventStore.GetFileList: eventTypeId = -1, startTime = 05/20/2015 11:41:01, endTime = 05/20/2015 11:41:01. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.31  OWSTIMER.EXE (0x25D8)                    0x27D0 SharePoint Server Search       Analytics                      ag7hi Medium   AnalyticsEventStore.GetFiles begin: eventTypeId = -1, time = 05/20/2015 11:41:01. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.31  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                afncy High     It's about time to run analysis. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.31  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                afxw2 Information UsageAnalyticsTimerJob-2489c0ad-60dc-4198-b2ca-7f7941fa3f40 : Previous execution of the analysis succeeded. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.33  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                afncm High     Analysis has not started in 27 days. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.34  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                agwo7 Critical UsageAnalyticsTimerJob-2489c0ad-60dc-4198-b2ca-7f7941fa3f40 : Search Analytics has not completed for 36 days. Last completed at: 04/14/2015 00:27:04. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.34  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                agwo8 Critical UsageAnalyticsTimerJob-2489c0ad-60dc-4198-b2ca-7f7941fa3f40 : Failed to start Usage Analysis. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.34  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                agwo9 Monitorable Last successful SA analysis was run : 04/14/2015 00:27:04. This is more than 10 days, so we cannot run analysis 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.34  OWSTIMER.EXE (0x25D8)                    0x27D0 SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (Timer Job Usage Analytics Timer Job for Search Application 2489c0ad-60dc-4198-b2ca-7f7941fa3f40). Execution Time=110.0304 6e49089d-8f0b-a003-60f3-fb58326c4bbd

Hi,

Could you please provide detail steps which caused the error? Its will be helpful for us to reproduce the error and solve it.

About Search Usage Analytics failed to start, please confirm the things below:

1.The Search service application is up.

2.The analytics processing database and link databases are running, and are in healthy state.

3.There is no problem with the analytics processing component

4.There is no problem with disk space.

5.There is no network connectivity issue.

6.The usage analytics timer job is running.

7.The search analytics timer job is running.

8.Verify the status of the search analytics analysis.

An article about Search Usage Analytics for your reference:

https://technet.microsoft.com/en-us/library/ee513082(v=office.15)#AnaStart

Best Regards,

Dean Wang

Thanks for the assistance.  1, yes the Search Service, Proxy, and administration web service for search service are all running. 2.The Database shows all are on line and in good shape. 3   Get-SPEnterpriseSearchStatus returns all components ACTIVE (none degraded). 4. Plenty of hard drive space available, 5 network functionality is fine.6.  The usage analytics timer job for search service application shows no error history, runs every 10 minutes.7  The Analytics Timer Job for Search Service Application, shows no error history, runs every 10 minutes. 8 Im not sure what this means Verify the status of the Search Analytics Analysis, but the jobs are running and the status says online for everything.

Hello, It seems that something is wrong with analytics event store. It should not return eventid as -1.

05/20/2015 11:41:01.31  OWSTIMER.EXE (0x25D8)                    0x27D0 SharePoint Server Search       Analytics                      ag7hh Medium   AnalyticsEventStore.GetFileList: eventTypeId = -1, startTime = 05/20/2015 11:41:01, endTime = 05/20/2015 11:41:01. 987da413-9c53-49f6-9209-0dbc56444722
05/20/2015 11:41:01.31  OWSTIMER.EXE (0x25D8)                    0x27D0 SharePoint Server Search       Analytics                      ag7hi Medium   AnalyticsEventStore.GetFiles begin: eventTypeId = -1, time = 05/20/2015 11:41:01. 987da413-9c53-49f6-9209-0dbc56444722

Also, search analytics is not running fine but that might be due to overall usage analytics not running. From your ULS logs:

05/20/2015 11:41:01.34  OWSTIMER.EXE (0x25D8)                    0x27D0 Search                         Usage Analytics                agwo9 Monitorable Last successful SA analysis was run : 04/14/2015 00:27:04. This is more than 10 days, so we cannot run analysis 987da413-9c53-49f6-9209-0dbc56444722

So I would suggest to search more in this direction. Hope this helps.

Thanks, I'm amazed that when  I search for '

"AnalyticsEventStore.GetFileList: eventTypeId = -1"

The ONLY result I find is THIS message.  Nice catch.  Sadly nowhere to go from here.

1. You should verify that the usage events are recorded correctly. To do that, on the machine where SharePoint Server 2013 is installed, go to the Event store. In most cases you can find the Event store in this file directory:

C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Analytics_<GUID>\EventStore

If you cannot find this, just type for \\ServerName\ and it will open shared folder. Make sure you see a share named Analytics_GUID.

2. Verify that above share has read access to everyone.

3. In the Event store, the usage events of each day are stored in a separate folder. Check if you can see folders over there for each day. Also if you open any folder, you would be able to see some text files saved with .log extension.

In an ideal situation, you should have one .log file for each instance of SA timer job.

4. Open one of the files in a text editor, for example Notepad++. This file contains quite a bit of information, but you should really only be looking for two things:

• Verify that the usage events are logged correctly.
• Verify that different users have generated the usage event.

for Usage analytics to work, the usage event must be recorded on the URL of the item. In the Event store file, youll see many URLs. Look for URLs that end in dispform.aspx?id= followed by a number.

Hope this

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)

Hope this

That was it!  Thanks much!