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

Suddenly not able to connecto to OWA

Just overnight I cannot connect to the OWA login screen. My IP resolves successfully, the HTTP redirect is working but I get a "cannot display the webpage". The last thing I did was apply and new SAN certificate. I have done this before and everything installed fine. Even locally on the server I cannot bring up the page. When I open IIS I can click on browse the website for OWA but when I attempt to login I get the same "cannot display webpage" message.

0
GMSMRM
Asked:
GMSMRM
  • 4
  • 2
  • 2
2 Solutions
 
NpatangCommented:
have you enabled the certificate for IIS..

check the below link for furtehr understanding
http://technet.microsoft.com/en-us/library/aa997231.aspx
0
 
GMSMRMAuthor Commented:
Yes, it is enabled.
0
 
NpatangCommented:
Take the backup of IIS and try rcreating the OWA virtual directory

http://technet.microsoft.com/en-us/library/aa998237.aspx
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LeeDerbyshireCommented:
Can you find the IIS log entries?
0
 
GMSMRMAuthor Commented:
Yes but they are jibberish to me.
I attached the latest log file if it helps.

FYI. My exchange and POP accounts work fine.
u-ex090713.log
0
 
LeeDerbyshireCommented:
It looks like you are being redirected somewhere else after logging in, but it's hard to tell where.  After you type https://servername/owa in you browser address bar, you will be redirected to the login page, so the address in the address bar will change slightly (to the .aspx page that is the logon page), but after you have logged in, the address should revert to https://servername/owa .  In your case, something may have changed.  Has the protocol (https) or the servername part changed?  Maybe it no longer has /owa on the end?
0
 
GMSMRMAuthor Commented:
Ok, I think I found where I missed a step. I did not link the HTTPS binding to the SSL certificate. I now can get to the OWA login.

BUT I had already followed your instruction to remove and re-add the owa virtual directory. Now when I open up the exchange console and go to Server Config->Client Access->OWA->properties an error comes up that it could not find the "owa (default web site)"

I did create the OWA virtual directory and it is listed after the get- cmdlet.
0
 
GMSMRMAuthor Commented:
I ran the "set-owavirtualdirectory" cmdlet and rebooted the server. Everything works once again. I just had to make some minor changes to the OWA settings back the way I had them.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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