Exchange 2007 - OWA

Good morning all.

I've recently been put in charge of Exchage 2007, inheriting anothers environment, and am having an issue with OWA that I can't seem to track or isolate.

When an attempt is made to access OWA internally or externally, the IIS7 screen appears. I've restarted the web site without it making a difference. I have found the following errors in event viewer indicating a problem but it's unclear to me. I'm also uncertain where else to look for problem identification.

Warning - event id 5026 - MS Exchange Transport
Warning - event id 9871 - MSExchangeIS Mailbox Store
Error - event id 1020 - MSExchange Store Driver

I'm also finding some VSS and SCHANNEL errors and question the possible relation with Exchange.

What where should I be looking for and where should I be looking ? Will the Exchange Management tools offer some help? I am new to Exchange 2007 and am a little lost.
Eddie_1Asked:
Who is Participating?
 
James HIT DirectorCommented:
If there is no redirection, then you need to type the server address with the OWA address:

http://servername/owa

Try this first to confirm OWA is available and then we can work on setting up redirection.
0
 
Bruno PACIIT ConsultantCommented:
Hi,

When you say "IIS7 Screen" I presume you talk about the sort of default web page that is configured by default on the root site in IIS !?

In that case, can you confirm that your OWA URL finished with "/owa" !??

By default, the OWA URL is https://yourserver.yourdomain.com/owa !
If you forgot the "/owa" suffix then you reach the root web page, not the OWA page.


Have a good day.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
AmitIT ArchitectCommented:
What is the FQDN used for accessing OWA. You can use ExRCA tool to test the OWA.
0
 
Eddie_1Author Commented:
Hi Spartan.

Unfortunately, that doesn't want to work. The OWA address is owari.companydomain.com. So, I reied https://servername/owari.companydomain.com
0
 
AmitIT ArchitectCommented:
0
 
David CarrCommented:
OWA relies on the URL being configured correctly on the Client Access Server and the IIS service being bound to the correct certificate with the same name/URL.
0
 
Eddie_1Author Commented:
Cool tool !  It tested successfully.
0
 
AmitIT ArchitectCommented:
can you run ipconfig /flushdns in one the machine and try again.
0
 
Eddie_1Author Commented:
Tried from a client computer (Windows 7) and no change.
0
 
Eddie_1Author Commented:
So, owa is named as "Default Web Site" in IIS&. Is it as simple as renaming that to anything?
0
 
AmitIT ArchitectCommented:
Check the URL in CAS OWA URL Setting. No need to change anything in IIS for now.
0
 
Eddie_1Author Commented:
I'm not finding Server Config -> CAS -> Owa (Default Web Site)   Outlook anywhere is visible in the right action pane.
0
 
Eddie_1Author Commented:
Nver mind. Just found it and am feeling like an idiot. I wasn't using the complete url.
0
 
Eddie_1Author Commented:
I think this is a clear display of a learning curve. I'll follow-up with a couple of internal folks to make certain they're using the right and complete url.
0
 
AmitIT ArchitectCommented:
Change it and reset the IIS and test again.
0
 
Eddie_1Author Commented:
Change the url and restart IIS for owa?
0
 
Eddie_1Author Commented:
I did resulting in file or directory not found.
0
 
Eddie_1Author Commented:
Were you expecting different results when changing the url? Also, are there better log files to review when working to isolate and diagnose an Exchange prblem? Thanks for your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.