When attempting to load the Enterprise Vault Office Mail App in OWA 2013, a call is made to load JavaScript files from the Enterprise Vault Server.   Under certain circumstances, one or more of these files may be missing or have been moved to another location.  The failure to reach some or all of the required JavaScript files will cause the Office Mail App to display unexpected results.

1. It is necessary to determine what JavaScript files may be missing, or are unable to be read.  To discover this, utilize the “Network Capture” feature built into Internet Explorer’s Development Tools. 
   • For more information on how to run a Network Capture, please review:  https://msdn.microsoft.com/en-us/library/gg130952(v=vs.85).aspx
2. Replicate the issue while running the Network Capture and review the log.  Multiple entries referencing the Enterprise Vault Virtual Directory may be returning a “404” result.  "404" equates to File not Found.
3. Attempt to discover these files manually.  The Enterprise Vault Virtual Directory reads to the “WebApp” folder located under the Enterprise Vault Installation Directory.  This folder and its contents can be reviewed by utilizing Windows Explorer.  Ensure that any file/folder specified in the Network Capture as a 404 is actually missing.

Note: If the JavaScript files returning the 404 are found in their respective locations under the “WebApp” directory, then further troubleshooting may be required to determine if the requests are being routed elsewhere.  Please contact Enterprise Vault Technical Support.

If the required files shown, as possibly missing in the Network Capture, are not able to be located in the “WebApp” directory then the Enterprise Vault Binary files will need to reinstalled. 

Please review the Enterprise Vault Documentation on reinstalling binaries if necessary. 

When attempting to load the Enterprise Vault Office Mail App (OMA), random characters or an empty text field is displayed.