Office Mail App Add-In Error: Something went wrong and we could not start this Add-In.
Article ID: 100044459
Updated On:
Description
Error Message
"Add-In Error: Something went wrong and we could not start this Add-In. Please try again later or contact your system Administrator."
"Add-In Error: This Add-In may not load properly but you can still try to start it."
Cause
The BaseURL must be used for External OMA access
In the New-App command, you must specify the Active Directory attribute LegacyExchangeDN with the OfficeMailAppManifest.aspx page. You can also specify other parameters, if required. The OfficeMailAppManifest.aspx page supports the following query string parameters:
|
LegacyMbxDN |
Mandatory. The Active Directory attribute LegacyExchangeDN for the user. If the LegacyExchangeDN value includes any URI reserved characters, then the LegacyExchangeDN value in the -Url parameter must be encoded. The following are examples of URI reserved characters: : / ? # [ ] @ $ & ' / + , ; = |
|
OfficeAppName |
Optional. The name of the Office Mail App in the Office Mail App Bar. The name defaults to Enterprise Vault. |
|
BaseURL |
Optional. The URL of the |
The manifest file is not generated if invalid values are supplied. The typical causes are as follows:
-
The mailbox is not enabled for archiving.
-
The LegacyExchangeDN value in the -Url parameter includes reserved characters, but the value is not encoded.
- The BaseURL value is not valid.
Resolution
Use the BaseURL in the Add-Type script
Add-Type -AssemblyName System.Web$Mbx = get-mailbox "mailbox"New-App -OrganizationApp -DefaultStateForUser:enabled -Url ' ("http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + [System.Web.HttpUtility]::UrlEncode($Mbx.LegacyExchangeDN) + "&BaseURL=https://external_access_server/EnterpriseVault")
Issue/Introduction
