• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 285
  • Last Modified:

Exchange 2003 and OWA not working

Hello all

I am currently testing Exchange 2003 in a Virtual PC environment where I have a DC and the Exchange box being only a member server and Im not being able to get the local OWA to work.

When I type http://servername/exchange it pops up the logon screen and after entering credentials it says Page Cannot be displayed.

Installation went well did the whole Forestprep and the domainprep, I went into one user account and did the exchange task were you add the email account so all that should be fine

Im not interested at the moment to get the whole SSL working all I want is to be able to get the basic HTTP working.

After you install exchange are you supposed to get any services running manually?
Do you have to enable any kind of permissions in IIS?

My experience with Exchange has been only on  SBS2003 at it always worked, This is my the 1st stand alone Exchange box.

Any suggestions
1 Solution
Try the following.  Sembee helped me with an issue I had a while back.  After being pointed in the right direction I found for OWA to work that you have to have the same version of paches for your Exchangeweb diectory.  Here is how you find out and what to do.

Go to both your Exchange server and you OWA server.  Go to c:\program files\exchsrvr\exchangeweb and make sure that ALL servers have the same version numbers.  If not copy and paste the missing version to the directory missing that version or versions number.  The version number will look similar to this:

IF you think it may be a permissions issue you may want to look into resetting your IIS directories.  It is pretty simple.  But I will warn you it will erase special permissions that you may have set up as well as https configs I belive.  Do your homework before doing this one:

Please post again if you have need for more help!

Is anything else displayed, other than 'Page cannot be displayed'?  Any error messages?  If not, go into your IE Advanced Options, and make sure that 'Friendly HTTP Errors' are not enabled, and try again.  The 'Friendly' error messages tend to hide most of the useful information.

You are not usually required to do anything special in IIS - it normally just works.
IT_ResourceAuthor Commented:
My Exchange and my OWA are in the same box.
I restarted the server without doing anything and launched http://servername/exchange put in credentials and now I get a page that says

                                      " HTTP 1.1 / 503 Service in no longer available "
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

IT_ResourceAuthor Commented:
actually it's http 1.1 503 Service Unavailable
IT_ResourceAuthor Commented:
I've read this:


and everything is as it should be
Hm.  Not always an easy error to fix.  Have a look at your Exchange VDir in IIS Manager, and try changing the Application Pool setting.  If it makes no difference, change it back again.
IT_ResourceAuthor Commented:
after researching in google and finding so many avenues as to what the problem might be
and since I'm doing this in a Test environment I've decided to start again from scratch
I will leave the question open just in case I have the same problem.
IT_ResourceAuthor Commented:
After reinstalling everything and actually having it running on the current environment this is no longer and issue
PAQed with points refunded (500)

EE Admin
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.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now