DELETED DELETED DELETED DELETED

Question

DELETED DELETED DELETED DELETED DELETED DELETED DELETED DELETED

Answer 1

Hi @IniobongNkanga-8038 ,

Welcome to the Microsoft Q&A platform!

Based on your description, you encountered some problems when trying to enable the archive mailbox for user l.butXXXXX@XXXXX.de. Let's analyze the potential causes and solutions for the PowerShell error and the Exchange Admin Center (EAC) internal server error.

The PowerShell error message you received indicates that there may be a problem retrieving the detach date of the previous archive. You can try the following steps to resolve this issue:

1. Make sure the user does not have an existing archive mailbox. You can run the following command to verify:

Get-Mailbox -Identity "l.butXXXXX@XXXXX.de" | Select-Object ArchiveStatus

If ArchiveStatus is None, it means there is no existing archive mailbox.

2. Although you mentioned that there are no pending move requests, it might be worth double-checking:

Get-MoveRequest -Identity "l.butXXXXX@XXXXX.de"

If there are any pending move requests, you can remove them using:

Remove-MoveRequest -Identity "l.butXXXXX@XXXXX.de"

3. Try using the -Force parameter with the Enable-Mailbox cmdlet:

Enable-Mailbox -Identity "l.butXXXXX@XXXXX.de" -Archive -Force

An "Internal Server Error" in the EAC can be caused by a number of reasons, including issues with the arbitration mailbox or the admin mailbox. Here are some steps to troubleshoot this issue:

1. Make sure the arbitration mailbox is healthy:

Get-Mailbox -Arbitration

If any arbitration mailboxes are missing or not healthy, you may need to recreate them.

2. Make sure the administrator account you are using has a mailbox. If not, create one:

Enable-Mailbox -Identity "<admin ID>"

3. Check Event Viewer for any related errors that may provide more details about the problem.
4. Sometimes recreating the OWA virtual directory can resolve internal server errors:

Remove-OwaVirtualDirectory -Identity "owa (Default Web Site)"
New-OwaVirtualDirectory -InternalUrl "https://<your-server>/owa" -ExternalUrl "https://<your-server>/owa"

By following the steps above, you should be able to identify and resolve the issue that is preventing you from enabling archive mailboxes for your users.

---

Please feel free to contact me for any updates. And if this helps, don't forget to mark it as an answer.

Best,

Jake Zhang

Answer 2

Kindly Confirm if the mailbox has a disabled archive guid

• Get-Mailbox -Identity "user@domain.com" | Select-Object ArchiveGuid,DisabledArchiveGuid

Then use the below cmdlet to remove it and then enable archive again.

• Set-Mailbox -Identity "user@domain.com" -RemoveDisabledArchive