none
OWA login screen opening, but never getting past that point (after transition to 2010 from 2003)

    Question

  • I'm in the process of transitioning from 2003 to 2010.  I've got the 2010 server to the point that mail is coming in and going out of it, and co-existing with 2003 properly (as far as I can see so far). I've moved my own mailbox over to 2010 and that seemed to go well. 

    Prior to moving my mailbox, when I navigate to the OWA url I get the 2010 log in screen... but when I logged in I was (properly) taken to the 2003 OWA screen where my mail was.  Now that my mailbox is on 2010, I enter my name and password and then it just spins and spins.  That is, it never comes back saying that it can't connect, or anything else.  It just tries and tries forever.  And I'm not finding any events at all during this process in the 2010 server.

    I believe it is unrelated, but I'm also unable to download the offline address book once my mailbox was transitioned.  I'd rather keep this thread focused on the OWA issue, unless they are somehow related.

    I've tried a number of things... mostly permissions based.  I loaded the server entirely using the domain\Administrator account, so with the thought that perhaps setup just does a poor job of delagating permissions (my user is a full admin on the 2003 machine), I added myself as a member of just about every AD group that was added during prerequisite steps.  But nothing is doing the job.  I don't know where else to look but this must be something simple, and likely permissions based somewhere I would think.

     

    Thanks for any direction you can offer!

    Tim

     

    Friday, May 06, 2011 5:16 PM

Answers

  • Hi Tim,

    It sounds like you are running into the same thing I recently worked through.  Fortunately, I documented the experience.  Check out this forum post to see if that matches your scenario:  http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/cc32c08b-4584-44e7-ac5d-5da4ca85d202

    In addtion, I posted a more comprehensive write-up and have a link to a powershell script to perform the correct configuration here: http://ehloworld.net/?p=136

    The short of it is that when you remove the redirection on all the IIS virtual directires it adds the config to the web.config file in the physical OWA directory.  This causes problems because the configuration needs to be in the application.host file.  Please review the log post and let me know if this helps.

    Your approach to name resolution looks good.  Sounds like you want to test internally before affecting external access.  Good approach there.

    Regards,


    Robert Durkin

    Check out my blog for more Microsoft Exchange and PowerShell topics. Follow me on Twitter.

    • Marked as answer by tmiller112 Saturday, May 07, 2011 12:44 PM
    Friday, May 06, 2011 8:13 PM

All replies

  • Hi Tim,

    I noticed that you are still in co-existance with 2003 and you have redirection to the 2003 OWA experience setup and working properly.  Do you also have HTTP redirection setup on the CAS server(s) for the default website?  I have seen this cause issues in the past.

    Regards,


    Robert Durkin

    Check out my blog for more Microsoft Exchange and PowerShell topics. Follow me on Twitter.

    Friday, May 06, 2011 7:41 PM
  • Robert, thank you for the reply. 

    I do have HTTP Redirect setup on the CAS server in 2010, to https://servername.domain.com/owa.  I followed these instructions here:  http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/.  At first this did seem to work well.  It's only for internal so far.  I haven't yet changed my external DNS.  Once I do I intended to change my redirect to https://mail.domain.com/owa.  Internal DNS is changed for mail (to new server) and legacymail to old server.  But internally this was working well so that any form of http(with or without S)://mail (or server name).domain.com  took me to the new OWA page, which in turn routed back to old OWA when my mailbox was there.

    However now I'm not having that same experience.  If I type http://mail.domain.com/exchange internally, I get a forbidden access page.  But I can still get to the 2010 owa login screen by navigating all the way to https://svrexc.deppmann.com/owa (however I have to have the S or it fails with forbidden access).  I noticed this after I posted above.  I was going to run back through the instructions at that link again.  I assumed this part wasn't working now because of all the tweak attempts I've been making.  I tried rebuilding the owa and ecp virtual directories somewhere along the way. 

    Are you saying that this redirect I have may be causing the problem somehow? 

    Friday, May 06, 2011 7:57 PM
  • Hi Tim,

    It sounds like you are running into the same thing I recently worked through.  Fortunately, I documented the experience.  Check out this forum post to see if that matches your scenario:  http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/cc32c08b-4584-44e7-ac5d-5da4ca85d202

    In addtion, I posted a more comprehensive write-up and have a link to a powershell script to perform the correct configuration here: http://ehloworld.net/?p=136

    The short of it is that when you remove the redirection on all the IIS virtual directires it adds the config to the web.config file in the physical OWA directory.  This causes problems because the configuration needs to be in the application.host file.  Please review the log post and let me know if this helps.

    Your approach to name resolution looks good.  Sounds like you want to test internally before affecting external access.  Good approach there.

    Regards,


    Robert Durkin

    Check out my blog for more Microsoft Exchange and PowerShell topics. Follow me on Twitter.

    • Marked as answer by tmiller112 Saturday, May 07, 2011 12:44 PM
    Friday, May 06, 2011 8:13 PM
  • Robert, Thanks very much.  This represented nearly two days of tinkering in an effort to get it right.  Removing the redirect via the method on your blog solved the problem so I can now log in to my 2010 OWA for the first time.  In retrospect I probably should have considered the redirect, but it had worked nicely when I didn't have any 2010 mailboxes, so I didn't think of it.  Good stuff!  You are my hero today :)
    Saturday, May 07, 2011 12:44 PM
  • Robert, Thanks very much.  This represented nearly two days of tinkering in an effort to get it right.  Removing the redirect via the method on your blog solved the problem so I can now log in to my 2010 OWA for the first time.  In retrospect I probably should have considered the redirect, but it had worked nicely when I didn't have any 2010 mailboxes, so I didn't think of it.  Good stuff!  You are my hero today :)


    Glad I could help.  That one took me a while to figure out as well.  Hopefully MS updates the technet article to avoid this for others.

    Cheers,


    Robert Durkin

    Check out my blog for more Microsoft Exchange and PowerShell topics. Follow me on Twitter.

    Monday, May 09, 2011 1:08 PM