Sharepoint site calendar error "Cannot complete this action. Please try again."

I have a calendar in my sharepoint site and when you click on the calendar you get the error:
"Cannot complete this action. Please try again."

The link is still on the left Nav Bar link.
I have gone into central admin and you can see the link for the calendar and that it has 4250 items in it but you can not click on it and go into it to manage the calendar.

Is there a way to force SharePoint to check all links?
How can i export the calendar and then delete/re-import it?
is there any other options im not thinking about to fix it?
knightdogsAsked:
Who is Participating?
 
Rainer JeschorConnect With a Mentor Commented:
Hi,
it seems that the previous initiated restore job "hangs". As mentioned in the last entries of your log excerpt, please review the central administration -> Operation -> Timer Jobs and delete the "orphaned" restore job.
Then restart the WIndows SharePoint Timer Service (either through Services snap-in, MMC or using an administrative cmd ->
net stop sptimerv3
net start sptimerv3

HTH
Rainer
0
 
knightdogsAuthor Commented:
I was also thinking of doing a stsadm -export of the site and then import to see if that would correct the issue.

This is on a live site.
0
 
Rainer JeschorCommented:
Hi,
which Sharepoint version and edition?
Anything in the windows event log on the server or in the Sharepoint ULS log?
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
knightdogsAuthor Commented:
RainerJ

In central Administration > Site Settings
Version: 12.0.0.6676
running on windows 2003 server
0
 
knightdogsAuthor Commented:
RainerJ

central administratoin > Operations
Windows SharePoint Services Search --- so WSS right?

32bit server
0
 
Rainer JeschorCommented:
Hi,
no - thats just the WSS search service - which is also available on the Server edition.

A good guide to identify the edition:
http://blogs.technet.com/b/sharepointcomic/archive/2008/09/06/determine-which-version-of-sharepoint-is-installed.aspx

Regardless of the edition:
anything in the SharePoint ULS log (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs)?
Or/and in the Windows Event log?

How does your URL look alike? Ending with the page
calendar.aspx
?

Can you try to manually open the same url but instead of "calendar.aspx" using the "allitems.aspx" - does this open?

Thanks and HTH
Rainer
0
 
knightdogsAuthor Commented:
Looking into the logs I see a bunch of this:

Timestamp              	Process                                 	TID   	Area                          	Category                      	EventID	Level     	Message 	Correlation
11/27/2013 09:36:00.50 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 2.	 
11/27/2013 09:38:01.18 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 4.	 
11/27/2013 09:39:02.68 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 5.	 
11/27/2013 09:41:02.39 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 6.	 
11/27/2013 09:42:02.88 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 1.	 
11/27/2013 09:45:06.14 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 28.	 
11/27/2013 09:46:04.25 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 62.	 
11/27/2013 09:47:03.31 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 9.	 
11/27/2013 09:50:04.23 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 3.	 
11/27/2013 09:51:03.34 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 12.	 
11/27/2013 09:55:03.26 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 8.	 
11/27/2013 09:56:02.89 	wsstracing.exe (0x07E4)                 	0x150C	ULS Logging                   	Unified Logging Service       	uls1	Monitorable	Tracing Service lost trace events.  Current value 23.

Open in new window

     



Trying to go directly to the url with:
https://abc.com/Lists/Shared%20Calendar/AllItems.aspx

gives the same error also.
0
 
knightdogsAuthor Commented:
Researching wsstracing.exe I saw a few posts saying to restart the
Windows SharePoint Services Tracing service.  I did this and now the logs show this:

Timestamp              	Process                                 	TID   	Area                          	Category                      	EventID	Level     	Message 	Correlation
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	 
11/27/2013 11:12:29.98 	OWSTIMER.EXE (0x07B8)                   	0x07E0	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id '{AD697E13-D59B-49F8-8542-0D1B175421D0}' for service '{8DF7E795-7082-4BA1-9694-F9A56B9AD534}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.

Open in new window

      



Looking in Central Administration > Operations > Timer Job Status
I dont see any jobs that are still running.
all jobs show 100% for the progress.  Am i looking in the right place?
0
 
knightdogsAuthor Commented:
I followed the steps here to resolve the above:

http://social.technet.microsoft.com/Forums/sharepoint/en-US/82e3b319-05b2-46a5-ac77-6cd4ed2ce27c/application-log-files-for-the-sharepoint-sever-are-growing-to-gbs

followed these steps

http://support.microsoft.com/kb/939308


and now my logs look like this:

Timestamp              	Process                                 	TID   	Area                          	Category                      	EventID	Level     	Message 	Correlation
11/27/2013 11:42:16.01 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ak	Medium  	 Processing web application id e9c6a3fd-deec-4fb6-8b8d-523192c162da	 
11/27/2013 11:42:16.01 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ag	Medium  	Processing service Microsoft.SharePoint.Administration.SPIncomingEmailService, id 1f6ab726-d59c-42ab-a69a-ed1ab3670c5b	 
11/27/2013 11:42:16.01 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ag	Medium  	Processing service Microsoft.SharePoint.Administration.SPTimerService, id 8df7e795-7082-4ba1-9694-f9a56b9ad534	 
11/27/2013 11:42:15.84 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72au	Medium  	Service Microsoft.SharePoint.Administration.SPAdministrationService, id 1d6d2fdd-2b92-4d2c-9a74-e96e431a89c7 not online, ignoring	 
11/27/2013 11:42:15.89 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ag	Medium  	Processing service Microsoft.SharePoint.Search.Administration.SPSearchService, id fed6821a-08bd-434b-a61d-97fc0cc5de4c	 
11/27/2013 11:42:15.92 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ah	Medium  	 Added job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition, id 956d874b-88dd-4ad9-8e3d-fea30ed1299b	 
11/27/2013 11:42:15.92 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ag	Medium  	Processing service Microsoft.SharePoint.Administration.SPDatabaseService, id ee5c0ff4-b182-42a3-a6e7-e12f54a4af13	 
11/27/2013 11:42:15.92 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ag	Medium  	Processing service Microsoft.SharePoint.Administration.SPWebService, id b660abd4-11b2-4bcc-a178-7566f0eccaf3	 
11/27/2013 11:42:15.92 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72aj	Medium  	Processing web service Microsoft.SharePoint.Administration.SPWebService, id b660abd4-11b2-4bcc-a178-7566f0eccaf3	 
11/27/2013 11:42:15.96 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ak	Medium  	 Processing web application id 782b9214-c7de-46cf-a1b5-74293db33c06	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPWorkflowFailOverJobDefinition, id afc88688-af4a-48b2-9094-4f220bc4ba6c	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPWorkflowJobDefinition, id 71a2a5be-5dca-4bf9-a0d0-0d1d6d25aaa1	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPChangeLogJobDefinition, id 4a9bb4ec-fb86-42df-88cd-e4b884f78223	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72am	Medium  	  Job definition Microsoft.SharePoint.Administration.SPDeadSiteDeleteJobDefinition, id c0dc792e-a759-4d4c-8191-4f372ff18cd7 not applicable, ignoring	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPImmediateAlertsJobDefinition, id 07efba87-fd74-4843-9acf-8565da3852b5	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPRecycleBinCleanupJobDefinition, id 6fb21d3c-6025-4690-97b1-aee596cb6355	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPDatabaseStatisticsJobDefinition, id 516fa1db-8fab-4e92-aed3-453e73020bca	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPSiteDeletionJobDefinition, id d9d4df85-807e-4d69-b70f-7f69cf7dec93	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPUsageAnalysisJobDefinition, id f3876c50-ecde-4976-a22b-b6e04eb185b6	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPDiskQuotaWarningJobDefinition, id ec028f6c-f6a6-4391-9685-2ce8d5542b93	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72al	Medium  	  Added job definition Microsoft.SharePoint.Administration.SPWorkflowAutoCleanJobDefinition, id 085ba249-d675-4bef-94c7-1565fb0e9320	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ag	Medium  	Processing service Microsoft.SharePoint.Administration.SPWebService, id a33ad1b7-02cb-47a9-89b9-bfba2f728da9	 
11/27/2013 11:42:15.99 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72aj	Medium  	Processing web service Microsoft.SharePoint.Administration.SPWebService, id a33ad1b7-02cb-47a9-89b9-bfba2f728da9	 
11/27/2013 11:42:16.03 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ah	Medium  	 Added job definition Microsoft.SharePoint.Administration.SPConfigurationRefreshJobDefinition, id ad697e13-d59b-49f8-8542-0d1b175421d0	 
11/27/2013 11:42:16.03 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ah	Medium  	 Added job definition Microsoft.SharePoint.Administration.SPSqmTimerJobDefinition, id 942f7bbb-f79b-473b-9536-d95911118c64	 
11/27/2013 11:42:16.03 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	72ah	Medium  	 Added job definition Microsoft.SharePoint.Administration.Backup.SPBackupRestoreJobDefinition, id 9d406713-8267-4fea-b5a7-59a440925bbc	 
11/27/2013 11:42:18.93 	OWSTIMER.EXE (0x15E8)                   	0x13CC	Windows SharePoint Services   	Topology                      	8xqz	Medium  	Updating SPPersistedObject SPBackupRestoreJobDefinition Name=Backup/Restore Parent=SPTimerService Name=SPTimerV3. Version: 254001 Ensure: 0, HashCode: 35320229, Id: 9d406713-8267-4fea-b5a7-59a440925bbc, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.Update()     at Microsoft.SharePoint.Administration.SPJobDefinition.Update()     at Microsoft.SharePoint.Administration.Backup.SPBackupRestoreJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)  	 
11/27/2013 11:42:17.57 	OWSTIMER.EXE (0x15E8)                   	0x1420	Windows SharePoint Services   	Timer                         	5utr	Medium  	Queued timer job Backup/Restore, id {9D406713-8267-4FEA-B5A7-59A440925BBC}	 
11/27/2013 11:42:19.49 	OWSTIMER.EXE (0x15E8)                   	0x13CC	Windows SharePoint Services   	Timer                         	7psa	Critical	The Execute method of job definition Microsoft.SharePoint.Administration.Backup.SPBackupRestoreJobDefinition (ID 9d406713-8267-4fea-b5a7-59a440925bbc) threw an exception. More information is included below.  The timer job for the restore operation was canceled. Before running the restore operation again, review the restore logs and delete the timer job from the timer job definition page in the Central Administration site.	 
11/27/2013 11:42:19.51 	OWSTIMER.EXE (0x15E8)                   	0x13CC	Windows SharePoint Services   	Timer                         	72ae	Unexpected	Exception stack trace:    at Microsoft.SharePoint.Administration.Backup.SPBackupRestoreJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)	 
11/27/2013 11:42:55.07 	w3wp.exe (0x11F4)                       	0x0F98	Windows SharePoint Services   	General                       	0	Medium  	Entering MRU trim routine.	 
11/27/2013 11:42:55.07 	w3wp.exe (0x11F4)                       	0x0F98	Windows SharePoint Services   	General                       	0	Medium  	Initial table size: 20050262 in 149 entries	 
11/27/2013 11:42:55.07 	w3wp.exe (0x11F4)                       	0x0F98	Windows SharePoint Services   	General                       	0	Medium  	Final table size: 20050262 in 149 entries	 
11/27/2013 11:42:55.07 	w3wp.exe (0x11F4)                       	0x0F98	Windows SharePoint Services   	General                       	0	Medium  	Exiting MRU trim routine.

Open in new window

0
 
knightdogsAuthor Commented:
Ahhh,
Thanks and sorry for that.
Still learning....
0
 
knightdogsAuthor Commented:
In event viewer I see a lot of these errors in Application:

SQL Database 'STS_Config_13841' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below.

Cannot open database "STS_Config_13841" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

Open in new window

0
 
knightdogsAuthor Commented:
The progress of the job is 100%.

I don't see anything about it in the logs now.
I still can not get into the calendar.
0
 
knightdogsAuthor Commented:
It ended up being a corrupt table.  I suspect from the updates applied the day before.
Had to engage MS to get it fixed.

Thanks for trying.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.