SharePoint - Logs filling up entire disk

Asked By TravisBeazle
08-May-07 11:50 PM
Hi There

I am having an issue on my web server. The system disk is becoming
completely full, in about 3 hours time. The folder: C:\Program Files\Common
Files\Microsoft Shared\web server extensions\12\LOGS  is filling up with log
files. Opening one of the logs reveals a lot of entries showing owstimer.exe
which is related to MOSS 2007. Can anyone shed any light on what would be
causing these mass amounts of log files? Here is a snippet from one of them:

05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.98 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:45.01 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.
05/09/2007 12:47:44.99 	OWSTIMER.EXE (0x081C)
0x0834	Windows SharePoint Services   	Timer
5uuf	Monitorable	The previous instance of the timer job 'Config Refresh', id
'{70B603BA-FE8E-4179-B644-6E3CAA3B95AC}' for service
'{17382B2C-E083-490A-BE2D-9782C64F20D1}' is still running, so the current
instance will be skipped.  Consider increasing the interval between jobs.

Help would be much appreciated.

Regards
Travis
SharePoint Discussions
 
SharePoint
(1)
IIS
(1)
  rote replied...
09-May-07 01:45 AM
Travis but you should be able to trim down you log from
the Sharepoint Central Admin site look for something pertaining to logs
there
Patrick
  Daniel Bugday replied...
09-May-07 06:45 AM
There is something called usage and analysis in sharepoin central
administration!

Check the settings there!

/Daniel Bugday
  Daniel Bugday replied...
09-May-07 06:45 AM
There is something called usage and analysis in sharepoin central
administration!

Check the settings there!

/Daniel Bugday
  Daniel Bugday replied...
09-May-07 06:45 AM
There is something called usage and analysis in sharepoin central
administration!

Check the settings there!

/Daniel Bugday
  StevenTappin replied...
09-May-07 07:20 PM
Hi Travis,

I posted a blog article about how to trim down log size... this might be of
help for you:
http://blogs.vertigo.com/personal/steventap/Blog/Lists/Posts/Post.aspx?ID=2

For my prod servers, I put the logs on a seperate drive to prevent them from
taking up all of the drive space.

Steven.
  Mike Gilbert replied...
21-Jul-08 06:32 PM
Argh - if your sharepoint server is writing hundreds of error messages to a log, then the solution is NOT to figure out how to handle or suppress the log messages!!



I had the same problem - found the solution in this blog: http://blogs.msdn.com/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx



I'm also having problems with IIS not being available, this knowlege base article (with hotfix) may also be relevant but I'm trying the above fix first.



http://support.microsoft.com/kb/946517/en-us
  Rich Woods replied to Mike Gilbert
11-Feb-11 10:46 AM
Steven is absolutely correct in saying you shouldn't just suppress the log messages.



The fix he points to worked for me.
Previous Discussion:  WSS 3.0 License issue
Create New Account
help
SharePoint WSS FAQ additions and changes - 11th - 17th June 2007 Note: All of the addresses of scid = kb;en-us;939015 Support WebCast: Microsoft Office Outlook 2007 integration with Microsoft Windows SharePoint Services (WSS) version 3 Contact Lists and Document Libraries 15th June 2007 http: / / support.microsoft.com / default.aspx?scid = kb;en-us;937208 Description of the SharePoint Server 2007 hotfix package: May 15, 2007 14th June 2007 http: / / support.microsoft.com / default aspx?scid = kb;en-us;937203 Description of the Windows SharePoint Services 3.0 hotfix package: May 15, 2007 14th June 2007 http: / / support.microsoft.com in the search results when you use an SQL query to sort search results in SharePoint Server 2007 14th June 2007 http: / / support.microsoft.com / default.aspx?scid = kb;en-us;937904 Description of the SharePoint Server 2007 hotfix package: May 25, 2007 (2nd one from May 25) 13th June 2007 http: / / support.microsoft.com / default.aspx?scid = kb;en-us;937949 You cannot upgrade SharePoint Portal Server 2003 to SharePoint Server 2007, and you receive an error message when you run the Prescan.exe tool
SharePoint Data Format on SharePoint pages - how to set I'm relatively new to SharePoint. We are planning on deploying Microsoft Office SharePoint 2007. I've installed a Proof of Concept "farm". On all of the servers and are either XP SP3 or Vista SP1. The Regional and Language Options were set BEFORE SharePoint was installed. However, all date fields on the SharePoint pages show as mm-dd-yyyy, which is ambiguous with respect to the day and this format. . ." dialog to set the Short Date Format to dd-mmm-yy. On the SharePoint site, in Site Actions, Site Settings, Site Administration, Regional Settings, I've set the "Locale that I can find to specifically set the Date Format. The date format on the SharePoint page is now dd-mm-yyyy, not dd-mmm-yy - the format set in Control
SharePoint Problem with BDC "View Profile" link [Sorry - this is a repost from another newsgroup - I Services and re-importing it, but that doesn't help either. (I've also rebooted, IIS reset, etc.) So what can I look at on my production server to see why production server, after clicking the BDC value in the list view: - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - w3wp.exe (0x1E74) 0x1894 SharePoint Portal Server Business Data 71qj High Acquired Read lock on LobSystemInstance cache w3wp.exe (0x1E74) 0x1894 SharePoint Portal Server Business Data 71qk High Released Read lock on LobSystemInstance cache w3wp.exe (0x1E74 0x1894 SharePoint Portal Server Business Data 71qj High Acquired Read lock on LobSystem cache w3wp.exe (0x1E74) 0x1894 SharePoint Portal Server Business Data 71qk High Released Read lock on LobSystem cache w3wp.exe (0x1E74) 0x1894 SharePoint Portal Server Business Data 71qj High Acquired Read lock on Entity cache w3wp.exe (0x1E74 0x1894 SharePoint Portal Server Business Data 71qk High Released Read lock on Entity cache w3wp.exe (0x1E74
SharePoint Subject: access denied to images (again) (it seems my first post of this question did properly under my technet account. posting again. Sorry.) I have several site collections on a sharepoint 2007 farm. One of the sites has a problem loading images from / _layouts / images / . Specifically have the permission to access Images folder. At this point, I suggest we open the IIS console, find the problematic web application (hosting the site) and check the identify, please log B5DC-83D062F75957} X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049 Newsgroups: microsoft.public.sharepoint.portalserver X-Tomcat-NG: microsoft.public.sharepoint.portalserver (it seems my first post of this question did not work properly under my technet account. posting again. Sorry.) I have several site collections on a sharepoint 2007 farm. One of the sites has a problem loading images from / _layouts / images / . Specifically permission to access Images folder. \ par \ par At this point, I suggest we open the IIS console, find the problematic web application (hosting the site) and check the identify, please log par X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049 \ par Newsgroups: microsoft.public.sharepoint.portalserver \ par X-Tomcat-NG: microsoft.public.sharepoint.portalserver \ par \ par (it seems my first
SharePoint Why authentication before opening a document in document library Hi, I want to be able I suggest we perform the following steps to resolve this issue. Step 1: Add the SharePoint site to the trusted site = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 1. Open Internet Explorer > Tools > Internet Options 2. On the Security tab, click Trusted and click Sites 3. Add the URL of the SharePoint site to the trusted sites list. 4. Click the "Custom Level" button under Trusted security be resolved. If the issue doesn't disappear, please check the Authentication type of the IIS virtual server. Step 2: Check Authentication type = = = = = = = = = = = = = = = = = = = = = = It is a known issue that the user will be prompted with login credentials when accessing the SharePoint Explorer View or opening documents stored in the SharePoint libraries. Therefore, please check the authentication type of this web application. 1. Open the IIS Manager, and right click the IIS website on which the SharePoint web application is hosted. 2. Point to Properties. 3. Click