Purview - eDiscovery Content Search failing with CS019-001 on 03/26/2025 both through Powershell and UI.. If worked

Question

Purview - eDiscovery Content Search failing with CS019-001 on 03/26/2025 both through Powershell and UI.. If worked

Keith Bower 25

I run Content Searches daily on email and have had success until 3/25 when searches began to consistently fail. We are hybrid Exchange and Office356. My PowerShell script returns this error:

Write-ErrorMessage : |Microsoft.Exchange.Configuration.Tasks.ThrowTerminatingErrorException|Unable to execute the task. Reason: Compliance search initialization for "DeleteSpecificMail_20250326_173617" failed with exception: An error occurred while sending the request..

When I use the eDiscovery > Cases > Content Search the new interface fails to load correctly, sometimes telling me to refresh the page to reload. reloading doesn't resolve. Cases are empty, but standard cases list correctly.

User's image

Classic eDiscovery > Content Search will load. And I can create a search but these fail with this message

Error The search job has failed. Internal server error occurred. Please try again later. (CS019-001)

I think permissions are set correctly. Any advice?

Scott Beck 5 Reputation points

2025-03-27T00:32:18.8033333+00:00

I have the same problem. Started happening yesterday
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-03-27T05:41:23.0633333+00:00
@Keith Bower

The error code CS019-001 indicates that there is an internal server error occurring during your content search attempts. This can happen for several reasons, including transient issues or problems with the search query that returns too many results for the system to process.

Here are some steps you can take to troubleshoot the issue:

Retry the Search - Sometimes, transient issues can cause temporary failures. Simply retrying the search after a short period may resolve the issue.

Check for Search Query Complexity - If your search query is complex or returns a large number of results, consider simplifying it. You can do this by using date ranges or limiting the number of search locations.

PowerShell Command - Use the following PowerShell command to get more details about the search and check for any additional error messages:

Get-ComplianceSearch -Identity <search name> | FL ResultDetails

Permission - Ensure that your permissions are correctly set for the eDiscovery operations. Sometimes, issues can arise if the necessary permissions are not granted.

Classic eDiscovery - Since the classic eDiscovery experience is still functional for you, you might want to continue using it temporarily while troubleshooting the new interface.

For more details refer:

Resolve search errors in eDiscovery (Standard)

Overview of Content search

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Joe Stine 0 Reputation points

2025-03-27T14:43:39.4066667+00:00

I also have the same problem since 3/26/25.
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-03-28T04:28:18.55+00:00

@Keith Bower

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Janus Palacio 85 Reputation points

2025-05-23T02:17:07.1566667+00:00

Anyone else experiencing the same issue right now?

I am unable to start a compliance search, this was working for me just last week.
Josh Weigner 1 Reputation point

2025-05-23T20:43:32.76+00:00

Yes, getting the same error today, along with Object reference not set to an instance of an object...

I can create jobs successfully in the new Content Search and results are returned. My issue is I am trying to run a purge operation on the search, and its stating that the search is still running or returned 0 results. If I run "Start-ComplianceSearch" i get Object reference not set to an instance of an object error. If I view the Search under Classic Content Search, I am seeing the CS019-001 error. If I try to create a new search through Powershell or Classic Content Search, I also get Object reference not set to an instance of an object, however the search is created but shows the CS019-001 error.
Keith Bower 25 Reputation points

2025-05-24T01:09:01.08+00:00

I have the same issue. It says the object being passed is null. It is broken again in a different way than before.

2 answers

Your answer

Scott Beck 5 Reputation points

2025-03-27T00:32:18.8033333+00:00

I have the same problem. Started happening yesterday
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-03-27T05:41:23.0633333+00:00

@Keith Bower

The error code CS019-001 indicates that there is an internal server error occurring during your content search attempts. This can happen for several reasons, including transient issues or problems with the search query that returns too many results for the system to process.

Here are some steps you can take to troubleshoot the issue:

Retry the Search - Sometimes, transient issues can cause temporary failures. Simply retrying the search after a short period may resolve the issue.

Check for Search Query Complexity - If your search query is complex or returns a large number of results, consider simplifying it. You can do this by using date ranges or limiting the number of search locations.

PowerShell Command - Use the following PowerShell command to get more details about the search and check for any additional error messages:

Get-ComplianceSearch -Identity <search name> | FL ResultDetails

Permission - Ensure that your permissions are correctly set for the eDiscovery operations. Sometimes, issues can arise if the necessary permissions are not granted.

Classic eDiscovery - Since the classic eDiscovery experience is still functional for you, you might want to continue using it temporarily while troubleshooting the new interface.

For more details refer:

Resolve search errors in eDiscovery (Standard)

Overview of Content search

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Joe Stine 0 Reputation points

2025-03-27T14:43:39.4066667+00:00

I also have the same problem since 3/26/25.
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-03-28T04:28:18.55+00:00

@Keith Bower

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Janus Palacio 85 Reputation points

2025-05-23T02:17:07.1566667+00:00

Anyone else experiencing the same issue right now?

I am unable to start a compliance search, this was working for me just last week.
Josh Weigner 1 Reputation point

2025-05-23T20:43:32.76+00:00

Yes, getting the same error today, along with Object reference not set to an instance of an object...

I can create jobs successfully in the new Content Search and results are returned. My issue is I am trying to run a purge operation on the search, and its stating that the search is still running or returned 0 results. If I run "Start-ComplianceSearch" i get Object reference not set to an instance of an object error. If I view the Search under Classic Content Search, I am seeing the CS019-001 error. If I try to create a new search through Powershell or Classic Content Search, I also get Object reference not set to an instance of an object, however the search is created but shows the CS019-001 error.
Keith Bower 25 Reputation points

2025-05-24T01:09:01.08+00:00

I have the same issue. It says the object being passed is null. It is broken again in a different way than before.

Answer 1

Microsoft reported Service Health incident with

"Issue ID: MO1041132

Affected services: Microsoft 365 suite, Microsoft Purview Status: Service degradation Issue type: Incident Start time: Mar 25, 2025, 12:45 PM MDT

User impact Users are unable to use eDiscovery services and features in Purview eDiscovery.

More info Users may be unable to export search results, or items from a review from eDiscovery.

Scope of impact Any user or admin attempting to perform actions via eDiscovery are affected.

Mar 28, 2025, 4:28 AM MDT

We're continuing our testing and analysis of the code. Our current ETA to have the mitigation deployed is Friday, March 28, 2025 at 11:00 PM UTC. However, due to the significant complexities involved with these mitigation actions, this estimate may change and we'll update this communication."

For me, the primary search function has been restored. I have not "exported content" that was reported to still be offline 3/26/2025.

Catherine Kyalo 1,935 Reputation points Microsoft Employee

2025-05-26T19:02:23.8+00:00

Hi Keith Bower

I’m following up to confirm whether this issue has been fully resolved and has not reoccurred, as I’ve seen similar reports from several customers.

Answer 2

Josh Weigner 1

In my case, it seems the issue was related to the account running the content search not being licensed.

Share via

Purview - eDiscovery Content Search failing with CS019-001 on 03/26/2025 both through Powershell and UI.. If worked

2 answers

Your answer