Retry a Content Search to resolve a content location mistake

  • Article
  • 2 minutes to read

Annotation

Microsoft 365 compliance is at present called Microsoft Purview and the solutions inside the compliance area have been rebranded. For more data about Microsoft Purview, see the blog annunciation.

When you apply Content Search in the security and compliance center to search a big number of mailboxes, you may get search errors that are similar to the fault:

              Mistake   The search on the following locations failed:  User1@contoso.com: Problem in processing the request. Delight endeavour once more later. If you keep getting this error, contact your admin. (CS008-009)  User2@contoso.com: Application fault occurred. Delight try once again later. (CS012-002)

These errors (with fault codes of CS001-002, CS003-002, CS008-009, CS012-002, and other errors of the grade CS0XX-0XX) indicate that Content Search failed to search specific content locations; in this example, two mailboxes weren't searched. These errors are displayed on the condition details flyout page of the Content Search.

Cause of content location errors

When searching a big number of mailboxes, the search is distributed across thousands of servers in a Microsoft datacenter. At whatever one time, specific servers could exist in reboot state or in the process of failing over to redundant copies. In either of these cases, the Content Search's request to retrieve data volition time out. In the previous example, the errors for the mailboxes that failed were the effect of the search timing out.

Resolving content location errors

Restarting the search will often consequence in like errors on different servers. Instead of restarting the search, click the Retry push that is displayed at the acme of the search results page.

Click the Retry button to resolve content location errors.

This will result in the retrying the search but for the mailboxes that failed. When you retry the search, the other results that were successfully returned are retained.

Tips to avoid content location errors

Here are some boosted causes of content location errors and some tips to help y'all avert them when searching large numbers of mailboxes.

  • The mailbox being searched might exist decorated due to user activity. In this instance, the search service might throttle itself to preclude the mailbox from becoming unavailable. To avert this, try running searches during non-business hours.

  • The search query might exist retrieving besides much content from the mailbox. If possible, effort to narrow the telescopic of the search past using keywords, date ranges, and search conditions.

  • Too many keywords or keyword phrases when you create a search query using the keywords listing. When y'all run a search query that uses the keywords list, the service substantially runs a split search for each row in the keyword list so that statistics can be generated. If you're using the keywords listing in search queries, minimize the number of rows in the keyword list or divide the number keywords into smaller lists and create a different search for each keyword list.

    Note

    To help reduce issues caused by large keyword lists, you're now limited to a maximum of 20 rows in the keyword list of a search query.

  • Also many searches are being performed on the same mailbox at the same time. If possible, endeavour to run one search at a time on whatever one mailbox.

  • Searching besides many mailboxes in a single search. The probability of content location errors increases when searching a large number of mailboxes. If possible, effort to run multiple searches then that each search includes a subset of mailboxes in your organization.

  • Required maintenance is being performed on the mailbox. Though this cause probably occurs infrequently, wait a picayune while afterward receiving the content location error and and so retry the search.