Basic Troubleshooting and Isolation for Online Archive issues:
Ref. articles:
1. User is unable to access Archive folder:
Isolation:
-Check if Online archive is enabled.
-Check the license assigned to the users.
-Check the behavior in OWA and OLK.
-Ensure issue is not machine specific.
Troubleshooting:
Collect output:
Get-Mailbox –Identity “testuser@abc.com” | Select *archive*
2. Emails are not moving to Online Archive:
Isolation:
-Check the archive mailbox status.
-Check the Retention Policy assigned.
-Check the retention Tags in the retention Policy.
-Ensure customer is looking in to correct Archive folder.
Troubleshooting:
Collect Output:
Get-Mailbox –Identity “testuser@abc.com” | Select *archive*
Get-MialboxFolderStatistics – identity “usermailbox”
Get-Mailbox –Identity “” | select RetentionPolicy
Start-ManagedFolderAssistant – Identity “usermailbox”
3. Archive size is reaching quota and is not auto-expanding:
Isolation:
-Check for the assigned license to the user.
-Ensure auto-expanding is enabled.
-Auto-expanding may take upto 30 days for expansion.
Troubleshooting:
Collect Output:
Get-Mailbox – Identity | select Autoexpandingarchiveenabled.
Get-Mailbox “user mailbox” | select *Archive*
Get-MailboxFolderStatistics
Basic Troubleshooting and Isolation for Online Archive issues in Hybrid environment:
https://docs.microsoft.com/en-us/microsoft-365/compliance/unlimited-archiving
https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges
1. On-premise users cannot access online archive.
Isolation:
-Ensure O365 IP addresses are permitted in the firewall (If any firewall is in place between O365 and onpremise server)
-Ensure archive is enabled.
-Ensure user has concerned license assigned.
-Check the behavior in OWA and OLK.
Troubleshooting:
Collect output:
Get-RemoteMailbox “” | Fl *archive*
Test-MapiConnectivity –archive
Test-ArchiveConnectivity -UserSmtp””
Test-OAuthConnectivity -Service EWS -TargetUri “”Mailbox “” | fl
2. The value "08073974-1902-4542-88ea37ba310f0c5c" of property "ArchiveGuid" is used by another recipient object. Please specify a unique value
Isolation:
-Check for the conflicting object.
-Check for deleted items as well.
-Collect GUID from the validation error
Troubleshooting:
Collect Output:
Get-MsolUser -UserPrincipalName affecteduser@domain.com).errors.errordetail.objecterrors.errorrecord| fl
Get-Recipient -IncludeSoftDeletedRecipients 'ExchangeGUID value'|ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted
Remove-MailUser ‘ExchangeGUID value' – PermanentlyDelete
3. User cannot open Online Archive in OWA. Get error “Your archive appears to be unavailable”
Isolation:
- Ensure O365 IP addresses are permitted in the firewall (If any firewall is in place between O365 and onpremise server)
-Ensure issue is not specific to machine.
Troubleshooting:
Collect Output:
Test-OAuthConnectivity -Service EWS -TargetUri “”Mailbox “” | fl
Test-ArchiveConnectivity -UserSmtp””
Get-RemoteMailbox “” | Fl *archive*
Test-MapiConnectivity –archive
Basic Troubleshooting for MRM, Retention Policy & Retention tag Issues:
Ref. articles:
https://docs.microsoft.com/en-us/powershell/module/exchange/policy-and-complianceretention/getretentionpolicy?view=exchange-ps
https://docs.microsoft.com/enus/powershell/module/exchange/mailboxes/getmailbox?view=exchange-ps
https://docs.microsoft.com/enus/powershell/module/exchange/mailboxes/getmailbox?view=exchange-ps
1. MRM working validation.
Isolation:
-Ensure Online Archive with MRM validates connectivity to a user’s archive mailbox
-Ensure Online Archive with MRM validates Oauth Connectivity
Troubleshooting:
Test-ArchiveConnectivity -Usersmtp “smtpaddress”
Test-OAuthConnectivity -Service EWS -TargetUri https://outlook.office365.com/ews/exchange.asmx -Mailbox “onpremise mailbox smtpaddress” -Verbose | fl
Test-OAuthConnectivity -Service EWS -TargetUri “https://server.contoso.com/ews/exchange.asmx” -Mailbox “o365mailbox smtpaddress” -Verbose | fl
2. Retention Policy and retention tags issues.
Isolation:
- Get list all Retention Policies
- Check Organization configuration
-Check User mailbox attributes
-Collect List of Retention Policy Tag
- Mailbox Diagnostics Information
Troubleshooting:
Get-RetentionPolicy |Export-Clixml "MRM Retention Policies -All.xml"
Get-Organizationconfig | IsDehydrated , *ELC*
Get-mailbox “smtpaddress” | export-clixml getmailbox_details.xml
Get-RetentionPolicyTag | Export-Clixml "MRM Retention Policy Tags - All.xml"
Important Properties: RetentionPolicyTagLinks , RetentionId
Export-MailboxDiagnosticLogs -ComponentName mrm “smtpaddress”
Important properties:
ELCLastRunSuccess
ELCLastRun
Basic Troubleshooting for Litigation Hold Issues:
Ref. articles:
https://docs.microsoft.com/en-us/exchange/policy-and-compliance/holds/litigation-holds?view=exchserver-2019
1. Basic Troubleshooting for Litigation Hold Issues:
Isolation:
-Check mailbox is under litigation hold.
-Check mailbox folder statistics
Troubleshooting:
Get-MailboxFolderStatistics -IncludeAnalysis | ? {$_.name –like “Deletions” -or $_.name –like “Purges” – or $_.name –like “Versions” -or $_.name -like "Recoverable Items"} | FL Name,ItemsInFolder,FolderSize
Start-ManagedFolderAssistant -HoldCleanup
Basic Troubleshooting for eDiscovery Issues:
Ref. articles:
https://docs.microsoft.com/en-us/microsoft-365/compliance/ediscovery
https://docs.microsoft.com/en-us/microsoft365/compliance/office-365-advanced-ediscovery
https://docs.microsoft.com/en-us/microsoft-365/compliance/ediscoverytroubleshooting-common-issue
1. The compliance search contains the following invalid location(s):useralias@contoso.com. The location "useralias@contoso.com" is ambiguous.
Isolation:
-Check for the conflicting object.
-Remove the duplicate value.
Troubleshooting:
Get-Recipient <username>
2. Search fails on specific locations
Isolation:
-Check compliance search status.
-From the output collect the failed location.
-Retry the search for the failed location.
Troubleshooting:
Get-ComplianceSearch <searchname> | FL
3. Exporting search results is slow
Isolation:
-Check for any network issue.
-Analyze Compliance search output and look for SearchResults & SearchStatistics
Troubleshooting:
Get-ComplianceSearch <searchname> | FL
Get-ComplianceSearchAction | FL
4. Internal server error (500) occurred"
Isolation:
Break the search into smaller searches and run the search again.
Try using a smaller date range or limit the number of locations being searched.
Troubleshooting:
Get-ComplianceSearch <searchname> | FL
Examine the trace.log file. It's located in the same folder that you exported the search results to.
Comments
0 comments
Please sign in to leave a comment.