Quantcast
Channel: Security and Compliance Management forum
Viewing all articles
Browse latest Browse all 481

Unable to Export S&C Content Search Results

$
0
0

Hi folks, wondering if anyone else has seen this / has a fix.

I can run new content searches via New-ComplianceSearch cmdlet, or through the GUI, and the search show results. However I receive errors when trying to process and export of the results found, getting the below error;

"Client Error. Unable to execute the task. Reason: Compliance search initialization for "<SearchName>" failed with exception: Unable to execute the task. Reason: ComplianceSearch object "<SearchName>" defines no locations.

Request: /api/ComplianceSearchAction?retry=false
Status code: 500
Exception: Microsoft.Exchange.PswsClient.PswsException
Diagnostic information: {Version:17.00.4234.007,Environment:SEAPROD,DeploymentId:757b444cc3f54ab8b1ff93b3b9aa9728,InstanceId:WebRole_IN_0,SID:f3be34cc-a7b7-49d4-a799-2c561df40192,CID:17cc1f24-462c-4322-9952-ade17a94fb75} Time: 2020-02-24T21:27:03.4885971Z

In Internet Explorer & Microsoft Edge, the error is always present. In Google Chrome I have had SOME luck in swapping export options after the initial error, eg; Selecting "One PST file containing all messages" first, get the error, change to "One PST file for each mailbox" and re-process the Export request, now with no error (Doesn't seem to matter what the initial selection is).

I have tried adding https://protection.office.com to trusted sites, turning off popup blocking etc, nothing. Got a legal discovery ongoing and this bug is causing me a lot of trouble in getting the info out prior to the court deadline!

FTR: I have an ongoing MS support Ticket (#18782588) going regarding this, but having a lot of trouble getting the support tech to understand this is occuring on EXPORT attempt only, they keep circling back to getting me to try to re-attempt the search.

Viewing all articles
Browse latest Browse all 481

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>