Sharepoint

[Guest Stevens]

About 4 days ago I noticed an error message in my Application Event log from

Sharepoint Services that there was not enough free space available and the

tracing service has temporarily stopped outputting trace messages to the log

file. I found the log files at C:\Program Files\Common Files\Microsoft

Shared\Web Server Extensions\12\Logs. At this location there are lots of

logs 30 - 40 meg. each. They all contain the same message,

'07/10/2007 08:18:14.98 OWSTIMER.EXE (0x0AD4)

0x0AFC Windows SharePoint Services Timer

5uuf Monitorable The previous instance of the timer job 'Config Refresh', id

'{CBECAB1F-4C74-4322-8F69-D838AA2EE6EC}' for service

'{4B8266D1-15D6-4A7E-AC9D-7B720684782A}' is still running, so the current

instance will be skipped. Consider increasing the interval between jobs.'

 

Any idea what this is and how to resolve it?

 

Thank you.

--

Mike Stevens

[Guest Jim]

RE: Sharepoint

 

Was this implementation of MOSS 2k7 from a Beta2 version?

 

In either case, take a look at:

 

http://technet2.microsoft.com/Office/en-us/library/3df597d0-bad0-4c73-9c26-a10bb80449881033.mspx?mfr=true

 

 

 

Jim

 

 

 

"Stevens" wrote:

> About 4 days ago I noticed an error message in my Application Event log from

> Sharepoint Services that there was not enough free space available and the

> tracing service has temporarily stopped outputting trace messages to the log

> file. I found the log files at C:\Program Files\Common Files\Microsoft

> Shared\Web Server Extensions\12\Logs. At this location there are lots of

> logs 30 - 40 meg. each. They all contain the same message,

> '07/10/2007 08:18:14.98 OWSTIMER.EXE (0x0AD4)

> 0x0AFC Windows SharePoint Services Timer

> 5uuf Monitorable The previous instance of the timer job 'Config Refresh', id

> '{CBECAB1F-4C74-4322-8F69-D838AA2EE6EC}' for service

> '{4B8266D1-15D6-4A7E-AC9D-7B720684782A}' is still running, so the current

> instance will be skipped. Consider increasing the interval between jobs.'

>

> Any idea what this is and how to resolve it?

>

> Thank you.

> --

> Mike Stevens

[Guest Stevens]

RE: Sharepoint

 

No, this is 2003.

--

Mike Stevens

 

 

"Jim" wrote:

> Was this implementation of MOSS 2k7 from a Beta2 version?

>

> In either case, take a look at:

>

> http://technet2.microsoft.com/Office/en-us/library/3df597d0-bad0-4c73-9c26-a10bb80449881033.mspx?mfr=true

>

>

>

> Jim

>

>

>

> "Stevens" wrote:

>

> > About 4 days ago I noticed an error message in my Application Event log from

> > Sharepoint Services that there was not enough free space available and the

> > tracing service has temporarily stopped outputting trace messages to the log

> > file. I found the log files at C:\Program Files\Common Files\Microsoft

> > Shared\Web Server Extensions\12\Logs. At this location there are lots of

> > logs 30 - 40 meg. each. They all contain the same message,

> > '07/10/2007 08:18:14.98 OWSTIMER.EXE (0x0AD4)

> > 0x0AFC Windows SharePoint Services Timer

> > 5uuf Monitorable The previous instance of the timer job 'Config Refresh', id

> > '{CBECAB1F-4C74-4322-8F69-D838AA2EE6EC}' for service

> > '{4B8266D1-15D6-4A7E-AC9D-7B720684782A}' is still running, so the current

> > instance will be skipped. Consider increasing the interval between jobs.'

> >

> > Any idea what this is and how to resolve it?

> >

> > Thank you.

> > --

> > Mike Stevens

[Guest Jim]

RE: Sharepoint

 

Sorry 'bout that...

 

"Stevens" wrote:

> No, this is 2003.

> --

> Mike Stevens

>

>

> "Jim" wrote:

>

> > Was this implementation of MOSS 2k7 from a Beta2 version?

> >

> > In either case, take a look at:

> >

> > http://technet2.microsoft.com/Office/en-us/library/3df597d0-bad0-4c73-9c26-a10bb80449881033.mspx?mfr=true

> >

> >

> >

> > Jim

> >

> >

> >

> > "Stevens" wrote:

> >

> > > About 4 days ago I noticed an error message in my Application Event log from

> > > Sharepoint Services that there was not enough free space available and the

> > > tracing service has temporarily stopped outputting trace messages to the log

> > > file. I found the log files at C:\Program Files\Common Files\Microsoft

> > > Shared\Web Server Extensions\12\Logs. At this location there are lots of

> > > logs 30 - 40 meg. each. They all contain the same message,

> > > '07/10/2007 08:18:14.98 OWSTIMER.EXE (0x0AD4)

> > > 0x0AFC Windows SharePoint Services Timer

> > > 5uuf Monitorable The previous instance of the timer job 'Config Refresh', id

> > > '{CBECAB1F-4C74-4322-8F69-D838AA2EE6EC}' for service

> > > '{4B8266D1-15D6-4A7E-AC9D-7B720684782A}' is still running, so the current

> > > instance will be skipped. Consider increasing the interval between jobs.'

> > >

> > > Any idea what this is and how to resolve it?

> > >

> > > Thank you.

> > > --

> > > Mike Stevens