OWA works for some but not others

95 pts.
Tags:
Microsoft Exchange 2003
Microsoft Outlook
Microsoft Windows Server 2003
Outlook Web Access
OWA
Hello, I am using both Microsoft Exchange and Windows Server 2003. I have 12 employees and 5 of them cannot connect to OWA and receive this error: The page cannot be found. The page you are looking for might have been removed, had its name change, or is temporatily unavailable. HTTP Error 404 - File or directory not found. Internet Information Services (IIS). IT NOT that they cannot connect. Everyone can get to the OWA site and enter their username and password. However, certain people receive the error while others can use it as they always have. This started happening a few weeks ago. The remaining 7 employees do not have any problems with OWA. I have tried to research the error and cannot find anything on why it works for some and not others or any fixes that resolve this. A new employee began here and she cannot access OWA either. And just to be sure of that I then created a fake user account with an Exchange box and that account cannot get email using OWA either. Any help or advice would be greatly appreciated. Thank you, Justine

Answer Wiki

Thanks. We'll let you know when a new response is added.

Have you checked the exchange features tab in AD for all users having the problem to make sure OWA is enabled for them?

Try possibly making a user who can’t receive email an administrator and see if you can log in to OWA as them, but remember to change them back afterwards.

Discuss This Question: 10  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Justine
    Yes I have checked that and it is enabled for all users. Any other ideas? Thank you
    95 pointsBadges:
    report
  • Technochic
    Try reading through this article and see if anything there applies.
    57,010 pointsBadges:
    report
  • Justine
    I will read through it and try. Thank you!!
    95 pointsBadges:
    report
  • Justine
    Thank you for the article. I followed it and many of the items were correct. However I did have to add some of the permissions to the indicated folders. I restarted the WWW Publishing Service and it did not work. OWA is still in the same point that I began at. Any other possibilities? I read about un-installing and re-installing IIS but I do not know if this is the fix either and do not want to just start doing unnecessary things. Thank you very much.
    95 pointsBadges:
    report
  • CosmoC
      Have you restarted the Server?
      Are ALL users able to connect locally (http://ExchangeServerName/exchange/UserName) on LAN?
      Have you tried using the OWA IP instead of DNS name?
      Is it always the same 7 users that CAN connect or is it 7 max before the 8th gets an error?
      Are you using any custom ports which might be blocked?
    
      There are a few MS updates which cause problems, but I don't think any cause 404 errors.
      Are they all using XP computers or some Vista?
      Is everyone using Internet Explorer? Same versions?
    
      I would verify where this issue actually is before un/reinstalling software.  Try to pinpoint if its a computer, user/permission, server, or network problem first.
    280 pointsBadges:
    report
  • Justine
    Have you restarted the Server? -Yes I have - restarting did not solve this. Are ALL users able to connect locally (http://ExchangeServerName/exchange/UserName) on LAN? - No - The 7 users that do not have problems can connect locally while the same 5 users with problems cannot Have you tried using the OWA IP instead of DNS name? -Internally we can only connect to our OWA by using the IP of the server. Internally I connect with https://192.168.1.xx/exchange -Externally we connect to OWA using: https://email.awnc.org/exchange Is it always the same 7 users that CAN connect or is it 7 max before the 8th gets an error? - Yes, it is always the same 7 people which can connect and the same 5 that cannot. Are you using any custom ports which might be blocked? - No, nothing on the Firewall was reconfigured, added, changed, deleted, ect. There are a few MS updates which cause problems, but I don't think any cause 404 errors. Are they all using XP computers or some Vista? -All employees are currently using XP. I am actually one of the 5 that OWA does not work for. I have ran the most recent updates from MS in hopes that perhaps it would solve this (somehow) and it did not. :-) Is everyone using Internet Explorer? Same versions? -Yes everyone using IE V7 I would verify where this issue actually is before un/reinstalling software. Try to pinpoint if its a computer, user/permission, server, or network problem first. -I don't plan on un/reinstalling until I know that is the best thing to do and/or a last resort. -I do not know how to "pinpoint" this problem. I don't believe it is related to a computer on the network b/c I can go home or even to the library and I cannot log into my OWA account but can log into one that works without any problems. -I have checked some user/permissions and cannot seem to find anything their either. I followed the MS articles: 327843 (troubleshooting OWA logon failures) and followed Technochic's article advice as well. I also read through MS articles 315122, 248033 (IIS error 404 file not found info) and still no luck. I have one other article that I have not tried: Article here Would you recommend that I follow the above article? Someone also suggested that I try the Exchange Isinteg and eseutil tools..................I do not know if that would fix this either. Thank you kindly.
    95 pointsBadges:
    report
  • Justine
    Anyone have any other suggestions or ideas on this one? Thank you in advance, Justine
    95 pointsBadges:
    report
  • Justine
    I know how frustrating it can be to have the exact same problem as one other person in this world and go through forum after forum without any fixes listed. Incase anyone else happens to have this same issue here is how I fixed it: 1. In Active Directory Users and Computers, I went into each of the accounts that OWA did not work for 2. I opened up the Email Addresses tab and checked the listed email addresses against accounts that OWA works for. 3. It appears that all the users which OWA did not work for had "update through recipient policy" checked and the users that OWA work for do not have that checked. ALSO, users that it did not work for were receiving an email account through the recipient policy such as *9945@mydomain.org or *fefed@mydomain.org 4. I unchecked the box to update w/ recipient policy and deleted the random *xxxxx@mydomain.com accounts on the users it did not work for 5. OWA now works for all employees and my next venture will be editing/correcting the recipient policy for the domain. Hope this helps!!!!
    95 pointsBadges:
    report
  • Cashley
    Hi justine, First, thank you for coming back and documenting your solution. I have been experiencing the same symptoms with a number of my users. Interestingly the solution in my case involved the same areas of AD as yours but the in the opposite direction. In my case all the users which OWA did not work for had “update through recipient policy” UNchecked and the users that OWA did work for DID have that checked. Once I checked that box for the non function OWA users, they could once again use OWA. So your comments definitely led me to the solution. Thanks again. Charlie
    10 pointsBadges:
    report
  • TauilBrazil
    First of all, thank you to Justine and Cashley for their answers that help me out to discover the solution. I had the same problem. It was working only for some, then I realized that the ones that was not accessing the e-mail had the default smtp e-mail deleted in the tab "E-mail Adresses". Ex: 9999@mydomain.com. When I insert it back, everything began to work. Thank you everybody, I hope my solution could help somebody.
    10 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following