<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Records Management on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/records-management/</link>
    <description>Recent content in Records Management on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Mar 2012 19:06:19 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/records-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SharePoint 2010 &#43; Custom retention formula installation failure &#43; current user is not a farm administrator</title>
      <link>https://matt-thornton.net/tech/sharepoint/sharepoint-2010-custom-retention-formula-installation-failure-current-user-is-not-a-farm-administrator/</link>
      <pubDate>Tue, 06 Mar 2012 19:06:19 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/sharepoint-2010-custom-retention-formula-installation-failure-current-user-is-not-a-farm-administrator/</guid>
      
        <description>&lt;p&gt;You may encounter this issue when trying to deploy a Custom Expiration Formula for use as part of records management within SharePoint 2010. The error you may encounter is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The SPPersistedObject, PolicyConfigService Name=PolicyConfigService, could not be updated because the current user is not a Farm Administrator.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is a really nasty little error and it may be easy to miss as people have a tendency to use an empty try catch {} in their FeatureActivation so the feature activates but you&amp;rsquo;re not aware there is a problem. (Well, you become aware of it when for all the activation in the world, the “Use Custom Retention Formula” dropdown never changes from disabled.) It&amp;rsquo;s particularly annoying because you&amp;rsquo;re activating a feature at the Site Collection level - why would you need Farm Admin to do it? Well, it&amp;rsquo;s because it makes changes to the Content Service (or thereabouts) - and this is proven when you go to Central Admin &amp;gt; Security &amp;gt; Configure Information Policy Management &amp;gt; Retention and you&amp;rsquo;ll notice (after a successful activation) that your custom policy shows up in the “Resources” section.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>