| M | D | M | D | F | S | S |
|---|---|---|---|---|---|---|
| « Dez | Nov » | |||||
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | ||
- .NET (4)
- Administration (14)
- Allgemein (7)
- C# (4)
- CRM (1)
- MOSS 2007 (33)
- Office (2)
- Programming (5)
- Project-Server (3)
- Projektmanagement (5)
- SharePoint (46)
- SharePoint 2010 (11)
- Uncategorized (1)
- VB.NET (2)
- Web (8)
- WIN 2008 (3)
- Workflow (9)
- 23.1.2012: Datenimport-Überlegungen (MS-CRM)
- 20.12.2011: Vorhandene Projekte in Project Server hochladen
- 18.12.2011: Project-Server Pro und Contra
- 17.12.2011: Project-Server 2010 Project Web Application (PWA)
- 25.9.2011: Migration MOSS 2007 nach Sharepoint 2010 Schrittweise (Step by Step)
- 16.9.2011: Backup-Script (Powershell) für Sp2010 aller SiteCollections und Websites einer Web-Application
- 31.3.2011: Ändern der Sprache in der SharePoint Zentraladministration (2010/2007)
- 28.1.2011: Was ist neu in SharePoint 2010 Foundation (Serie) - Teil 3
- 25.1.2011: Was ist neu in SharePoint 2010 Foundation (Serie) - Teil 2
- 25.1.2011: Was ist neu in SharePoint 2010 Foundation (Serie) - Teil 1
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/