Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

GPR_PROPAGATION errors filling up log

  Asked By: Brendan    Date: Mar 18    Category: MOSS    Views: 1318

I am running MOSS2007 (patched to Oct 2009 cummulative roll-up) as a small
farm on a 32-bit Win 2008 SP2 with a SQL Server 2008 on a 64-bit Win 2008 SP2.

The following errors appear regularly in my logs. Should I be alarmed? How
can I configure my system to avoid these errors?

Share: 

 

1 Answer Found

 
Answer #1    Answered By: Willard Valenzuela     Answered On: Mar 18

This appears to be normal timer job operations and can safely be ignored,
it's just writing what ever operations are being performed. If the only
concern is disk space then logging level can be reduced or logging can
completely be stopped. It basically helps only when you are troubleshooting
issues.

1. Disable/Reduce logging as follows:
a. Go to Central Administration | Operations | Under Logging and
Reporting | Diagnostic Logging.
b. In the drop down menu Select a category select All.
c. Choose Lease critical event log  as Error. (This is Windows Event
logging)
d. Choose Lease critical event log as None or Unexpected. (This is
SharePoint ULS logging in 12/logs directory)

To Disable ULS logging completely:
STSADM -o setlogginglevel -tracelevel None

To Disable Windows Event logging completely:
STSADM -o setlogginglevel -windowslogginglevel None

Later on when you logs to be generated you can turn logging on as below:

2. Enable verbose logging as follows:
a. Go to Central Administration | Operations | Under Logging and
Reporting | Diagnostic Logging.
b. In the drop down menu Select a category select All.
c. Choose Lease critical event log as Information.
d. Choose Lease critical event log as Verbose.

To Enable Verbose ULS logging completely:
STSADM -o setlogginglevel -tracelevel Verbose

To Enable Windows Event logging completely:
STSADM -o setlogginglevel -windowslogginglevel Information

To SharePoint logging level to default:
STSADM -o setlogginglevel default


(Note: Setting verbose level for ULs generates huge amount of logs and
might fill up entire disk quickly)


FYI logging can also be turned on for specific category such as alerts or
workflow while troubleshooting.

 
Didn't find what you were looking for? Find more on GPR_PROPAGATION errors filling up log Or get search suggestion and latest updates.




Tagged: