OWA Front End issues - a few of them

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I am posting this problem to a few groups, so if you have seen this
elsewhere......

I have searched and searched to no avail for solutions to these
problems, but none seem to be right for my situation:

I have a FE/BE Exchange 2003 SP2 installation. FE is running Standard
on a Win2K3 SP1 box, BE is running Enterprise on a Win2K3 SP1 box.
These are completely fresh installations in a brand new Exchange
environment (no upgrades from anything).

When logging into OWA (through the FE server using "https://";) using
the Premium client, I get the eternal "Loading..." and the icons are
not functional. I know there have been numerous postings about
compression and to install the IIS 6.0 compression corruption, but
since I'm on SP2 the hot fix complains that the files installed are
newer than the files in the hot fix, so it fails. Plus I don't have
compression turned on anywhere.

When I log into the Basic client I can view my messages and I can click
on anything that is a hyperlink (i.e. Reply) but if I click on any
icons I get the following two errors:

Line: 38
Char: 1
Error: Object expected
Code: 0
URL:
https://mail.company.com/exchange/username/Drafts/RE:%20subject-3.EML...

Line: 1
Char: 1
Error: 'cmdSend' is undefined
Code: 0
URL:
https://mail.company.com/exchange/username/Drafts/RE:%20subject-3.EML...

I have checked all the permissions that I can find (adding
Authenticated Users permissions to the system folders and allowing Read
& Execute, Read and List permissions); I have deleted the Virtual
directories and had Exchange recreate them. I have verified anonymous
authentication (the anonymous account is a local computer account not a
domain account). I have even blown away IIS & Exchange and reinstalled
them (being a front end server - not a big deal).

Now here is the kicker, if I login to the BE server using OWA (using
"http://"; NOT "https://";) I get into the Premium account just fine with
no problems, I can't login to the basic client - I'm never given an
option. Obviously I don't want to open the BE server to the internet
(defeats the purpose of having a FE/BE configuration).

I have SSL configured on the FE server, and I have tried both with and
without Forms Based Authentication (with no compression). I have not
installed Trend Micro OfficeScan on the servers (though it is on the
workstations - but not all). And URLScan has never been installed.
There are absolutely no errors reported in Event Viewer.

BTW, one last config note: I have RPC over HTTP installed using the
FE/BE configuration with absolutly no problems what-so-ever.

I welcome any comments/thoughts/suggestions/questions you may offer up.

.

Relevant Pages

  • Re: Install of SMS not detecting Active Directory
    ... service account until the site is installed and the services start. ... Running setup as local administrator will not work very well, ... > installation fails immediately after answering the options with an error ... > stating SQL server is not available. ...
    (microsoft.public.sms.setup)
  • Re: Administrator account disabled in SBS 2008 but password is now kn
    ... demonstrating to a very high value customer. ... passwords for both my user account and the Administrator account. ... The Server service is disabled. ... extension of a trial installation which expired due to non-use when there ...
    (microsoft.public.windows.server.sbs)
  • RE: Administrator account disabled in SBS 2008 but password is now kn
    ... demonstrating to a very high value customer. ... passwords for both my user account and the Administrator account. ... log back in and finish up the server installation and to install Exchange, ... The Server service is disabled. ...
    (microsoft.public.windows.server.sbs)
  • Re: Advanced client install!
    ... Your Push installation account must be a member of ... Now have brought up a new installation and things are working fine ... > ccm.log from the site server giving information of the status of the ... > Getting a new request from queue "Retry" after 100 millisecond delay. ...
    (microsoft.public.sms.admin)
  • RE: Sharepoint Single Sign-On Issue Account Issue
    ... > anyway I found a solution, to enforce the SSO configuration; ... > to change 'C:\Program Files\' according to your server default program files ... >> on the Single Sign-On Admin Account creation. ...
    (microsoft.public.sharepoint.portalserver)