SharePoint 2019 Retention policy transfer to not working. Does on 2013 and 2016.

waaromikniet 101 Reputation points
2021-03-30T13:51:19.907+00:00

I have a ContentType retention policy on my list. It has 2 fases. First fase declares a record. Second fase moves the declared record to a record center after a day. On 2013 this works fine. On my 2019 box only the first fase works. So a record is declared. The second fase is not working and I get this error in the ULS

File ******* is not moved because it's a record and deleteblocked

Steps to reproduce

All actions are done via Site settings and central admin

  • We have created a new site collection (Record Center English)
  • We configured the new Record Center as a send to connection
  • We have created a new site collection (team site English)
  • Enable in place record management
  • We have created a custom contenttype that inherits from the document contenttype
  • We have created a information right policy on our custom contenttype
    This information right policy has 2 fases. Fase 1 (non record): Declare item as record based on created + 0 days (0 days is for testing purpose) Fase 2 (For records): Move the item to a sendto location (newly created record center) based on declared as record + 0 days (0 days is for testing purpose)
    Retention Policy

82842-pfqur.png

  • We created a custom document library, enabled contenttypes and add our contenttype to the library.
  • We set our custom contenttype as default and remove the out of the box contenttype document
  • Drag a file in the new library.
  • Run the expiration policy SharePoint timer job. We see the item declared as record
  • Run the expiration policy SharePoint timer job again We now expect the item being moved to our sendto connection.

Wat we see is this error in the ULS 

03/30/2021 11:28:42.73    OWSTIMER.EXE (0x0A48)                       0x6F8C         Document Management Server           Content Organizer              bcoey  Medium        File /sites/retentiontest/Test/Rapportage.csv is not moved because it's a record and deleteblocked.         394ab99f-8d20-e0c8-1a6a-82c62c1a90ec  
03/30/2021 11:28:42.73    OWSTIMER.EXE (0x0A48)                       0x6F8C         Document Management Server           Information Policy Management     xorh   High             Failed to submit file Test/Rapportage.csv:  Moving file /sites/retentiontest/Test/Rapportage.csv is blocked because it's a record and deleteblocked.   394ab99f-8d20-e0c8-1a6a-82c62c1a90ec  
03/30/2021 11:28:42.73    OWSTIMER.EXE (0x0A48)                       0x6F8C         Document Management Server           Information Policy Management     aar0   Medium           SiteSubscriptionId=00000000-0000-0000-0000-000000000000; SiteId=6f6681e0-23aa-4f21-a49c-86d753f6bfab; WebId=1001e1ea-08e5-4496-8ada-a0a93f383ff2; ContentDB=Content_O: Processing retention post actions for item /sites/retentiontest/Test/Rapportage.csv:UndoCheckOutBeforeUpdate, KeepCheckedOutToSystem         394ab99f-8d20-e0c8-1a6a-82c62c1a90ec

When we do the same in our SharePoint 2013 farm the second run of the “expiration policy SharePoint timer job” moves the document to our sendto connection

When I alter the information policy and send the record to the recycle bin instead of the send to connection it will work.

SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,798 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. ChelseaWu-MSFT 6,316 Reputation points
    2021-03-31T09:48:32.36+00:00

    I can reproduce this behavior in my SharePoint Server 2019 environment. Error returns when we try to move a declared record using Send To Connection.
    It seems to be the default behavior for Record Declaration working with Information management policy, and there does not seem to be any fix or workaround for it.

    In this case, I would propose a new support ticket to be raised to have a dedicated Technical Professional to support you from there. The contact number for your region could be easily found from below website, you can simply refer to the Customer Service Representative and he/she will be glad to help you with creating a new ticket.
    Global Customer Service phone numbers
    https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    **Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. **

  2. waaromikniet 101 Reputation points
    2021-04-01T06:40:34.32+00:00

    I did some testing on SharePoint 2016. On SharePoint 2016 this still works. So there is, in my opinion, a breaking change in this behaviour in SharePoint 2019

  3. waaromikniet 101 Reputation points
    2021-04-13T07:12:17.617+00:00

    I got a response from the engineering team from Microsoft. They say it is by design in SharePoint 2019.
    I can't understand why they would break a feature that is already present since SharePoint 2010. There is also no documentation about this major change.
    They gave the advice to change to record declaration setting to "No aditional restrictions". See below image.
    Our business requirements is that when a record is declared users should not be able to edit or delete the document. So we can't use this setting in that way.

    87303-recorddeclarationsetting.png

    0 comments