SharePoint 2019 eDiscovery getting failed when Place On Hold.

Rahim Molvani 1 Reputation point
2024-06-27T09:48:27.4666667+00:00

I am adding around 20 sites in combination with OneDrive sites. I am also adding 15 users for whom I want to place a hold. Sometimes the hold is applied successfully, but other times it shows "Failed" directly, or it goes into processing and then shows "Failed." I have checked the permissions and everything seems to be fine, as it is sometimes successful.

getting bellow error in logs. "Preservation failed for source. Case ID: eca1c7af-b4ae-44fc-ae4c-a5f3f516db03 SourceGroupId: 0 ActionType: In-Place Hold 747936a1-c414-2031-fc11-ee3ab56107f5 06/26/2024 09:39:20.76 w3wp.exe (0x1EE0) 0x8860 Document Management Server Discovery ap5mm Medium Updating Preservation History for Hold Id c15edf86-bb2a-42a4-b7b3-3ceb88730ae5 - 6/26/2024 9:39:20 AM Failed to put source on hold for In-Place Hold policy 'Test-hold'."User's image

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,892 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Yanli Jiang - MSFT 23,811 Reputation points Microsoft Vendor
    2024-06-28T06:05:34.53+00:00

    Hi @Rahim Molvani ,

    The error message you are receiving indicates that the preservation hold failed for the In-Place Hold policy 'Test-hold'. This can occur for a variety of reasons, including issues with permissions or site accessibility. It's possible that the hold is successfully applied for some sites and users, but not for others due to these issues.

    To troubleshoot this issue, you can try the following steps:

    • Check the permissions for the sites and users that are failing to be placed on hold. Ensure that they have the necessary permissions to be placed on hold.
    • Verify that the SharePoint locations associated with the hold requests are accessible and not read-only. If they are read-only, contact your SharePoint site administrator to configure the site as writable and retry the hold.
    • Check the URLs for the SharePoint sites associated with the hold requests to confirm that they exist. If they do exist, edit the custodial/non-custodial data source for the site and retry the hold action.
    • Verify that the email addresses associated with the hold requests are valid Exchange Online mailboxes. If they are valid, edit the custodial/non-custodial data source for the mailbox and retry the hold action.
    • If the distribution group associated with the hold request has more than 1,000 email addresses, it can't be expanded to be placed on hold. In this case, add the individual email addresses as custodial or noncustodial data sources or split the distribution group into groups with less than 1,000 email addresses and retry the hold action.

    It's also worth noting that the Hold Processing and Reporting timer job generates reports about items on hold and removed item from hold libraries that are pending release. The timer job runs daily and processes eDiscovery in SharePoint Server.

    For your references:

    Manage holds in eDiscovery (Premium)

    Add content to a case and place sources on hold in the eDiscovery Center

    eDiscovery and in-place holds in SharePoint Server


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    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.