This error will be in the export warnings and errors.csv or skipped items.csv. When running an eDiscovery search that includes SharePoint Online and OneDrive for Business locations, you may receive the error File Not Found although the file is located on the site. If you continue to receive these errors, see Retry failed locations for more troubleshooting steps. Retry the eDiscovery search on the failed locations only. If you receive this error, we recommend that you verify the locations that failed in the search then rerun the search only on the failed locations.Ĭonnect to Security & Compliance Center PowerShell and then run the following command: Get-ComplianceSearch | FLįrom the PowerShell output, view the failed locations in the errors field or from the status details in the error from the search output. Would you like to retry the search on the failed locations? If multiple users are returned, locate and fix the conflicting object.Įrror/issue: Search fails on specific locationsĪn eDiscovery or content search may yield the following error: The output for would be similar to the following: Name Run the following command to retrieve all instances of the username: Get-Recipient ResolutionĬheck for duplicate users or distribution list with the same user ID.Ĭonnect to Security & Compliance Center PowerShell. The compliance search contains the following invalid location(s): The location is ambiguous. If you try to add user's mailbox location to search and there are duplicate or conflicting objects with the same userID in the Exchange Online Protection (EOP) directory, you receive this error: Information on when to contact Microsoft Support is included in the resolution steps. Resolving some of these scenarios requires help from Microsoft Support.
This article covers basic troubleshooting steps you can take to identify and resolve issues you may encounter during an eDiscovery search or elsewhere in the eDiscovery process.
0 kommentar(er)
