Veritas Enterprise Vault™ Setting up the Enterprise Vault Office Mail App
- Setting up the Enterprise Vault Office Mail App
- About the Enterprise Vault Office Mail App
- Deploying the Enterprise Vault Office Mail App
- Troubleshooting the Enterprise Vault Office Mail App
The Enterprise Vault Office Mail App manifest file is not created
If invalid parameter values are supplied for the OfficeMailAppManifest.aspx
page for use with the PowerShell cmdlet New-App, no manifest file is created. The cmdlet fails and returns an error message of the following type:
The app couldn't be downloaded. Error message: The remote server returned an error: (500) Internal Server Error.
The typical causes of this error are as follows:
The user is not enabled for Enterprise Vault.
The LegacyExchangeDN value in the -Url parameter includes reserved characters, but the value is not encoded.
The BaseURL value is not valid.
The following example returns a more detailed error message when the manifest file is not created for a specified individual user. This script also shows how you can download the application manifest to a file, then specify the file in the New-App cmdlet instead of the URL.
Add-Type -AssemblyName System.Web $Mbx = get-mailbox "mailbox" $uri = new-object system.uri( "http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + [System.Web.HttpUtility]::UrlEncode($Mbx.LegacyExchangeDN)) $webclient = New-Object Net.Webclient $webClient.UseDefaultCredentials = $true try { $bytes = $webclient.DownloadData($uri) New-App -mailbox $Mbx.LegacyExchangeDN -FileData $bytes } catch [Net.WebException] { [Net.HttpWebResponse] $webResponse = [Net.HttpWebResponse]$_.Exception.Response; Write-Warning $webResponse.StatusDescription } |
Where:
mailbox is the name of the mailbox you are trying to enable for the Office Mail App.
EV_server is the name of the Enterprise Vault server.