Link to home
Start Free TrialLog in
Avatar of it-afdelingen
it-afdelingen

asked on

FE OWA fails reaching BE cluster - HTTP Error 404 - File or directory not found.

Scenario:
3 FE Win 2003 with Ex 2003 SP2 + 2 x 2 active/passive BE Win 2003 with Ex 2003 SP1

After updatering FE servers and one BE cluster, OWA can't reach mailboxes on the updated BE.

Tried to update the one BE cluster to SP2, so FE and BE was the same, but no result.

The one BE cluster not updated, and still running SP1, is running smoothly through FE OWA.

Also trouble sending mails from one BE to the other.
Avatar of amaheshwari
amaheshwari
Flag of India image

Please check this:


"HTTP Error 404 - File or Directory not found" error message when you request dynamic content with IIS 6.0
http://support.microsoft.com/?id=315122

Ashish
Check this as well:

Common reasons IIS Server returns "HTTP 404 - File not found" error
http://support.microsoft.com/kb/248033/en-us
Avatar of it-afdelingen
it-afdelingen

ASKER

If i call the BE http://exchangeserver2/exchange it works fine.
It's only when i try to reach at mailbox on the updated BE through my FE servers I get the error.
Users are split, all users on the updated server, cant access their mail through OWA, and there is no errors in eventlog, alle blue and fine. But úsers placed on the not updated server, can access fine through the same FE server, that gives 404 to users on the updated server.
Have you tried reapplying SP2 on the updated server, Also please compare all the Security fixes on all the servers, Make sure that all are up to date ( Apart from Sp2). In most cases if one security fix is applied on the FE and the same is not applied on the BE it might break OWA. Also check the IIS log files for any errors.
Yes, ive tried to reapply SP2. Both the FE and the SP2 BE is fulle updated.
Also no mail is travelling between SP2 BE and SP1 BE.
ASKER CERTIFIED SOLUTION
Avatar of questionforraja
questionforraja

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Same hotfix on both servers.
Q_21879140 Solves the problem.

Not an OWA problem, but a security settings.