After a successful install of OWA extensions, shortcut icons display in OWA interface however no EV toolbar options are displayed, or if displayed, are non-functional when accessing an archive-enabled mailbox.  In this situation, check the IIS log on the Exchange server connecting to and look for a 404 error during the OWA loading process.

Several common scenarios for the error to be displayed include the following:

Scenario 1
On an Exchange 2007 CAS (Client Access Server) and the EV Tool bar options loaded however OWA returned an error when attempting to use any of the EV toolbar options. The 404 error occurs in the IIS log when the OWA page attempted to access \Client Access\owa\EnterpriseVault\v7.5.3.2138\languages\en-us\EVStrings.js.  In this case, the "en-us" folder did not exist.  

2008-08-05 17:24:46 W3SVC1 <IP_Address> GET /owa/EnterpriseVault/v7.5.3.2138/languages/en-us/EVStrings.js - 80 <Domain\Username> <IP_Address> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+1.1.4322) 404 0 3

(From the error "404 0 3", the sub-status '3' translates via Net helpmsg to "The system cannot find the path specified.")

Note: OWA would return an error.  In the details, the error was:

"errorMessage = 'g_sEVStringSearchArchives' is undefined"
(The component 'g_sEVStringSearchArchives' could change, depending on the EV option selected)

Solution:
Confirm that the file listed is present in the requested location and accessible.
- Depending on the version of EV and Exchange, if the requested file(s) did not install, it may be required to locate the necessary file(s) in the install media or from another working environment.
- If running Exchange 2000 or Exchange 2003 and EV 2007, the files to be placed in \exchweb\Enterprise Vault\<Version> would be located in the install media under '\Server\OWA2000s'.

Scenario 2
On an Exchange 2003 Front-end Server and the 404 occurred during the load page and the EV Toolbar options did not load.  In this example, the issue was due to a version mismatch installed on the Exchange Server.  If installing from a previous version (example: Installing EV 7.0 SP1), a different folder version will be created.  

Solution:
The '7.5.3.2138' (EV 2007 SP3) folder did not exist and the folder was "\Exchweb\Enterprise Vault\7.0.1.2002\" (7.0.1.2002 is EV 7.0 SP1).  

Uninstall and reinstall on the Exchange Server in question using the correct binaries. This will generate the proper 'version' folder under \Exchweb\Enterprise Vault\.

Scenario 3
An Exchange 2003 Back-end Server and the 404 occurred during the load page and the EV Toolbar options did not load (Note: NO ERROR RETURNED IN THE OWA DIAGNOSTICS).   The error occurred when the OWA page attempted to access /exchweb/enterprise vault/7.5.3.2138/EVPremiumReplacement.js.  In this case, the "EVPremiumReplacement.js" file did not exist.  

W3SVC1 10.83.230.32 GET /exchweb/enterprise+vault/7.5.3.2138/EVPremiumReplacement.js - 80 - <IP_Address> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648) 404 0 2

(From the error "404 0 2", the sub-status '2' translates via Net helpmsg to "The system cannot find the file specified.").

The sub-status can be different depending on the situation, however the sub-status can be translated with the help of the "NET HelpMsg" command:
1. Under command prompt, type "net helpmsg 3" (Minus quotes)
2. This will return "The system cannot find the path specified"

Solution:
Confirm that the file listed is present in the requested location and accessible.
- Depending on the version of EV and Exchange, if the requested file(s) did not install, it may be required to locate the necessary file(s) in the install media or from another working environment.
- If running Exchange 2000 or Exchange 2003 and EV 2007, the files to be placed in \exchweb\Enterprise Vault\<Version> would be located in the install media under '\Server\OWA2000s'.


Scenario 4
When trying to access Archive Explorer and Search.asp through OWA 2003 generates a 404 error.

Solution:
1. Open the Enterprise Vault Admin Console.
2. Expand Policies, Exchange, Mailbox and go to the properties of the Exchange Mailbox policy.
3. On the Advanced tab, select OWA from the drop-down menu.
4. Modify the Client Connection setting to Use proxy.
5. Go to the properties of the Exchange Mailbox Archiving Task and click on the Synchronization tab and click Synchronize.
6. Confirm Archive Explorer and Search.asp can now be accessed through OWA.