05-23-2012 03:16 PM
Hi all :)
I have a weird problem.
Last week I setup/enabled Enterprise Vault / vault access through rpc/http for our mobile users.
Since then OWA does not work properly goping through Internet Explorer. It works fine with Google Chrome however.
What happens with IE is that you get the logon window, OWA logs in but then hangs while trying to load.
Has anyone had this experience or know what might have changed to cause this weird behaviour?
We are running EV8 (I will be upgrading shortly) on windows server 2003, exchange 2003.
thanks
Tracy
05-23-2012 03:23 PM
Your best bet is to enable logging and seeing where its hanging.
I'm guessing this is affecting both enabled and non enabled users connecting to OWA, correct?
You can edit the frontend and backend INI files located in the Enterprise Vault install directory on the Exchange servers and then review the logs from there.
Also does it only fail for external OWA usage or is it both internal and external usage?
what happens if you browse directly to a Backend exchange server , does it work then also?
Reason i ask is because if the backend works and the front end doesn't, it helps narrow things down a bit, and typically if the backend does not work then the frontend won't work, so it helps you concentrate on one particular server.
Another option you may have is to revert to just OWA EV only and not worry about RPC over HTTP access and publish the /EnterpriseVault/ directory from the EV Server in the same manner you would with Exchange 2007 or Exchange 2010
05-23-2012 07:21 PM
You mean loggin on the exchange server or on the EV server?
05-23-2012 07:34 PM
On the Exchange server, in the \Program Files\Enterprise Vault\ directory is an INI file where you can enable logging for OWA 2003
Just make sure that you go directly to that server when doing the OWA logon.
So for instance if you have something like
mail.myCompany.com -> owaServer1.myCompany.com
mail.myCompany.com -> owaServer2.myCompany.com
mail.myCompany.com -> owaServer3.myCompany.com
go directly to https://owaServer1.myCompany.com and enable the logging there
otherwise if you enable logging on one server and it goes to another server, you won't see the request logged etc
Also try a non EV enabled user vs an EV enabled user, and then you can see if its something specific to enabled users or all enabled users.
05-23-2012 08:09 PM
No ini file in any of the sub directories.
Tested non-ev user. same result
I am going straight to our single exchange server.
I'm thinking that running the rpc enable process has changed something, maybe in IIS on the exchange server?????
Tracy
08-02-2012 04:28 PM
(bump)