Forum Discussion

Blackfoottech's avatar
13 years ago
Solved

EV 10 Archive Explorer 404 error in Outlook

Hi,

I have a Windows 2008 R2 server that has EV 10 installed on it.  Yesterday I walked through the instructions to set up Ev access through OWA.  I did not get it to work.  The EV icons do not appear internally or externally.  Today some of my users cannot open Archive Explorer or Search Vaults from within Outlook (2007 or 2010), they receive a 404 error File or Directory Not Found.

Can someone help me troubleshoot this??

Thanks.

  • OK So heres whats happening....

    1. EV Client detects that its using Outlook Anywhere (RPC over HTTP)

    28/02/2012 21:03:46.128[4804][L]: DesktopCommon::UseRPCOverHTTP: 0x0
    28/02/2012 21:03:46.129[4804][H]: RPC over HTTP is enabled (flags = 39)
    28/02/2012 21:03:46.129[4804][L]: ~DesktopCommon::UseRPCOverHTTP: 0x0


    2. EV Client reads the Hidden message and see's the Default Web App URL

    28/02/2012 21:03:46.484[4804][H]:     DEFAULTWEBAPPURL = https://e-vault.blackfoot.com/EnterpriseVault


    3. EV Client then tries to connect using the *internal* name for EV and gets no response

    28/02/2012 21:03:46.882[5368][M]: HaveConnection::ExecuteTest - Connection test to: e-vault.blackfoot.com/EnterpriseVault/clienttest.gif failed
    28/02/2012 21:03:46.883[5368][M]: HaveConnection::ExecuteTest (2589335) - Ending connection
    28/02/2012 21:03:46.890[5368][M]: Could not contact the EV web server (https://e-vault.blackfoot.com/EnterpriseVault) directly, trying the EV RPC over HTTP URL


    4. EV Client then tries to see if there is a URL specified in the policy but finds none:

    28/02/2012 21:03:46.892[5368][L]: ~DesktopCommonConfig::LoadSettingsFromHiddenMessage: 0x0
    28/02/2012 21:03:46.892[5368][M]:     Desktop Setting: RPCOVERHTTPPROXYURL
    28/02/2012 21:03:46.892[5368][M]:     No Value

    5. EV Client attempts to use the URL you use in Outlook and append /EnterpriseVaultProxy/ at the end

    28/02/2012 21:03:46.940[5368][M]: HaveConnection::ExecuteTest - Connection test to: mail.blackfoot.com/enterprisevaultproxy/clienttest.gif failed
    28/02/2012 21:03:46.941[5368][M]: HaveConnection::ExecuteTest (2589476) - Ending connection
    28/02/2012 21:03:46.942[5368][L]: ~HaveConnection::ExecuteTest
    28/02/2012 21:03:46.942[5368][M]: Could not contact the EV web server using the RPC over HTTP URL (https://mail.blackfoot.com/enterprisevaultproxy)

     

    After this the Enterprise Vault client basically gives up.
    The reason for it not getting the response it requires is simply just from trying to get the regular GIF and it coming back with some kind of error, so it could be the SSL issue that you mentioned.

    However what you could do is if you don't care about External access to EV via Outlook Anywhere is simply to change the Desktop Policy to use a Direct connection method, as opposed to anything else, this way even when the clienttest.gif fails, you will still be pointed to the correct URL, its just users will be asked to accept that the SSL has an incorrect name