- .NET (4)
- Administration (12)
- Allgemein (6)
- C# (4)
- MOSS 2007 (31)
- Office (2)
- Programming (5)
- SharePoint (38)
- SharePoint 2010 (3)
- Uncategorized (1)
- VB.NET (2)
- Web (7)
- WIN 2008 (1)
- Workflow (8)
- 27.4.2010: Access denied while joining an existing MOSS 2007 farm
- 27.4.2010: SQL-Server Logfiles kürzen / Shrink SQL-Server DB Logfiles
- 14.4.2010: Timerjobs für Policies laufen nicht
- 10.12.2009: CAML query nested too deep
- 28.11.2009: SharePoint 2010, Listen und Bibliotheken, was ist neu?
- 27.11.2009: SharePoint 2010 Beta, erste Eindrücke
- 6.10.2009: SharePoint Fehlermeldung bei Verwendung der Suche / Search error
- 25.9.2009: MOSS große Listeneintrag Anlage wird nicht hochgeladen / MOSS large list item attachment not uploading
- 20.9.2009: stp Vorlage ungültig... / stp template invalid...
- 26.5.2009: Erste Systemvoraussetzungen für SharePoint 2010 von Microsoft veröffentlicht
Timerjobs für Policies laufen nicht
Sollte man feststellen, dass die eingestellten Policies (z.B. Löschen von Dokumenten, die älter als Zeitraum x sind) nicht abgearbeitet werden und man in der Zentraladministration unter Timer job definitions feststellt, dass diese Jobs noch nie gelaufen sind, dann hilft folgendes Vorgehen:
Record Center / Information Management Policy Jobs Not Running
Interesting enough, we noticed after installing “something” (it could have been Project Server, Service Pack 1 or even the Infrastructure Update) that none of the time jobs managed by the PolicyConfig service were running. If fact, they were all list as have never run, which I knew is a lie since they used to work at some point in time. These jobs include:
Expiration Policy
Hold Processing and Reporting
Information Management Policy
Records Center Processing
In trying to troubleshoot this issue, I was messing around with one of the stsadm commands that can be used to set the when these four polices run. However, when I tried to run the following command:
Stsadm -o setpolicyschedule -schedule “daily at 23:50:00″
I would get an error saying “The Information Management Policy feature is not active.” After a little bit more research, I found out that the “feature” that it is complaining about is the RecordsManagment feature. Granted, this feature is scope at the Farm level and thereby is automatically activate, I took the liberty and ran
stsadm -o activatefeature -name RecordsManagement -force.
After running the re-activate command, I was then able to run the setpolicyschedule command (which I didn’t need to do to resolve the issue) and volia my Information Management Policy’s timer jobs are running again!
-> Aus “Team Eli´s blog” http://vspug.com/teameli/2008/10/13/record-center-information-management-policy-jobs-not-running/