Outlook Web Access

[Matt Fulks]

I am trying to install OWA on an NT Exchange Server 5.5 and receive an HTTP 500 Internal Server Error. I removed the NT Authentification but that did not fix the problem. Any suggestions?

[Mike McKinlay · Accepted solution]

Depending on your installation, you may need to deinstall IIS, install v2, then upgrade to v3 and v4. Also, there is an upgrade document at

http://www.microsoft.com/TechNet/exchange/technote/upgrade.asp

What version of NT and Service Packs are you running? Version/patch info for IIS? Exchange/OWA?

[Matt Fulks]

I'm running NT 4.0 SP 6a, Exchange 5.5, and IIS 4.0

[Mike McKinlay]

As I recall, the Exchange 5.5 SP1 fixed some problems with OWA. Are you patched to SP1 or SP2?

[Matt Fulks]

I don't believe there are any SP's on Exchange. Should I install SP3, or start with SP1 and then add SP3?

[John Whitehead_1]

Matt, you can go straight for SP3. It might also be worth having a look around in IIS administrator to check that the virtual directory /exchange is set up correctly. Does OWA work locally when you go to http://127.0.0.1/exchange ?

[Matt Fulks]

No, when I try the loopback address/exchange I still get the "http 500 internal server error" message.
How should the virtual directory/exchange be setup?

[Jamie Hughes]

Hi Matt,

OWA has a few "gotchas" and there are definitely some things you need to do to get it installed and working properly. I highly recommend that you spend a few minutes reviewing the OWA Troubleshooting document that Microsoft has put together. There is info on installation, server configuration, etc. It will save you a lot of headaches now and down the road if you follow their recommendations, paying special attention to the Server Configuration Checklist section.

http://support.microsoft.com/support/exchange/content/whitepapers/owa_tshoot.asp?PR=ECH&T1=7d&FR=0&A=T&T=Q&S=F&

Best regards,
Jamie Hughes

[Matt Fulks]

I tried to follow the Server Configuration Checklist, but when I try to grant LOG ON LOCALLY to the local computers database, by typing usrmgr \ from a DOS prompt I receive a message stating that the is a member of the domain and focus will be set to the domain. Everything else on the Server Configuration Checklist is setup correctly. How do I get the Log on locally configured?

[Jamie Hughes]

Hi Matt,

You have to set that via User Manager for Domains. Start that up and go into Policies, User Rights, then toggle the pulldown until you see the Log On Locally right. Then just add what you need.

I hope that helps,
Jamie Hughes

[Matt Fulks]

I've done that but through the domain. I'm having problems getting to the local computer's accounts database which Microsoft says is a requirement.

[Jamie Hughes]

Hi Matt,

Is the IIS machine a member server or a domain controller? Also, how are you logging on when you do this (locally or into the domain) and also who are you logging on as, either locally or domain (local admin, domain admin, etc). If this is a member server, do you have admin rights on it?

Thanks,
Jamie Hughes

[Jamie Hughes]

Hey Matt,

It sounds like the IIS machine is a member server. If that's the case, log onto the IIS computer using the LOCAL administrator account. Start User Manager for Domains and then choose User / Select Domain and type the local computers name as \localcomputer.

If that isn't working for you, something else isn't set up right and we'll have to do some more digging.

Best regards,
Jamie Hughes

[Jatt Dill]

Hi Matt,

I had same problem internal server error 500. I walked through all the configuration for exchange server 5.5, IIS 4.0. Nothing happend. I re-installed three four times on different machines does't work either. I search every single page on the internet no info was available. Finally i put stress on my brain and figured out. why i am getting this error message.

Solution : Its the access right in the IIS default web site properties web page.

Follow these instructions:

1. Open the default web site properties.
2. Click on Directory security tab.
3. Edit the Anonymous access and Athentication control.
4. Just check the basic Athentication (Clear Text). Uncheck all the others.
5. Then it will ask you select the child node. Just select exchange.
6. Make sure you configured the same type of access in the exchange server LDAP protocol property page.
7. Then try to log in http://servername/exchange

I Tried it works for me. I have Exchange and IIS installed on the same server.
Give a shot I hope it will work for you too.

Your Friend,
Jatinder Mann