OWA issue on exchange 2007 - 404 page

[Sarah_Seftel1]

Hi,

I have a weird situation of OWA & ev in exchange 2007.

OWA install performed, owauser.wsf was running without any alerts.

evanon is created in EV server, TXT file of exchange server is in the right place.

when opening OWA - you can see the archived icon but not the EV toolber.

when opening an archived mail you get :

the archived item is not available at the moment... press here to open the original item (traslating from hebrew - more or less)

when pressing the link - you get 404 page.

I enables the web.config logging, but there is nothing at all that is written in the logs that looks like it has been doing anything from the OWA side.

I have the same issue (ev 9 + server 2008 + owa on exchange 2007) on 3 other places.

I think it has something to do with IIS 7 on 2008 server, but - as always - I might be wrong...

any ideas?

Sarah.

[JesusWept3]

Can't really tell much from the log file as I'm on an iPhone, however it does show that the mailbox it's tryig against has not been enabled for archiving or it can't read the hidden message (maybe because the EWS URL is incorrect or should be using HTTPS instead of regular HTTP) Also the EWS URL is purely set to localhost so you may want to try changing this Can I ask whether this is an external URL that can be accessed from the Internet or is an internal URL? The reason you are getting the 404 is due to the fact that it can't radthe hidden message and ultimately doesn't know the EV URL

[Sarah_Seftel1]

sorry for the poor knowledge - but, EWS URL? where do I change it?

Exchange Web Service?

I need to change it to the EV server?

[Sarah_Seftel1]

this is what I see in the web.config:

<add key="EnterpriseVault_ResourceVersion" value="v9.0.1.1073"/>
<add key="EnterpriseVault_WebDAVRequestHost" value="localhost"/>
<add key="EnterpriseVault_LogEnabled" value="false"/>

where do I change the EWS URL please?

[TonySterling]

You would add it to the web.config. 

The URL to use when calling the Exchange Web Services on the CAS, (default "<https://localhost/ews/exchange.asmx>"):
  <add key="EnterpriseVault_ExchangeWebServicesUrl" value="https://localhost/ews/exchange.asmx"/>

Article URL http://www.symantec.com/docs/TECH141519

[Sarah_Seftel1]

getting the same messege, and the same 404 page.

the weird thing is that even if i'll enable logging, I don't see this user in any of the log files...

in the log, I do see a different user with the following:

05/07/2011 19:18:23 [5960,8] [WebDAVRequest::Send] Exception sending WebDAV request: System.Net.WebException: The remote name could not be resolved: 'http'
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at Symantec.EnterpriseVault.Owa.ExchangeStoreAccess.WebDAVRequest.Send()

but the web config set to "<add key="EnterpriseVault_ResourceVersion" value="v9.0.1.1073"/>
        <add key="EnterpriseVault_WebDAVRequestHost" value="https://192.168.1.42/ews/exchange.asmx"/>
        <add key="EnterpriseVault_LogEnabled" value="false"/>
        </appSettings>

so is the The remote name could not be resolved: 'http' got something to do with that?

[TonySterling]

Do you know if Client Certificate Authenticatication is enabled?

It could be this: Article URL http://www.symantec.com/docs/TECH155485

[Sarah_Seftel1]

is not fully written...

where exactly do I check it?

Sarah.

[TonySterling]

Yeah, there are some missing bits, huh?  :)

Here, this might help.  http://blogs.technet.com/b/exchange/archive/2008/10/07/3406361.aspx

[ghlee]

Does anyone have any idea?

Basically we just applied a windows patch and now EV buttons are missing and unable to open archived items.

I've already uninstalled and reinstalled. In addition, i've compared the web.config file between the problem CAS server and the other CAS server that has not yet been patched. It looks identical.

I've enabled logging and this is what i see:

Exception sending WebDAV request: System.Net.WebException: The remote name could not be resolved: 'http'

[TonySterling]

Can you share what patch you installed?  Was it Windows OS or Exchange?

[Sarah_Seftel1]

<add key="EnterpriseVault_ResourceVersion" value="v9.0.1.1073"/>
<add key="EnterpriseVault_WebDAVRequestHost" value="localhost"/>
<add key="EnterpriseVault_LogEnabled" value="false"/>
<add key="EnterpriseVault_ExternalWebAppUrl" value="/enterprisevault"/>    
<add key="EnterpriseVault_UseExternalWebAppUrl" value="true"/>    
<add key="EnterpriseVault_ExternalHostNames" value="ExternalHostName"/>

We still have to define the ISA since in our case what I have is internal domain that is different than the external domain name.

But after doing those changes at the moment - when contacting internal address I don't get 404 anymore.