Howdy all,
Has anyone come across an issue with WSSv3 where it is filling up the logs
with:
11/23/2010 00:59:59.56 OWSTIMER.EXE (0x0430)
0x0F98 Windows SharePoint Services Timer
5uuf Monitorable The previous instance of the timer job '', id
'{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}' for service
'{00000000-0000-0000-0000-000000000000}' is still running, so the current
instance will be skipped. Consider increasing the interval between
jobs.
THe Servicve GUID is all zero'd out :( and I'm unable to find the timer job
with the ID.
Im also getting hit by Config Refresh timer job messages.....
11/23/2010 01:05:20.90 OWSTIMER.EXE (0x0430)
0x0F98 Windows SharePoint Services Timer
5uuf Monitorable The previous instance of the timer job 'Config
Refresh', id '{36585983-62A2-48C4-8104-60D7FDB1A9CE}' for service
'{3F4BC297-5757-49A7-B5AD-1CC2C90CDDC8}' is still running, so the current
instance will be skipped. Consider increasing the interval between
jobs.
Have cleared the cache and tweaked the timer job to increase its time, but
starting to hit a wall... all the info I can find says "not the service,
delete the cache and restart it... However doing this every6day is not
viable nor desirable.
No error in the Event Logs on the SQL Server (also has plenty of space on
it), nor in logs of the WFE (both Event Viewer and WSS).
Cheers,
DB
_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
