baysysadmin
asked on
Users cant login to OWA after being migrated form Ex2007 to Ex2013
I just finished my Ex2007-Ex2013 coexistance and everything is working great except OWA.
Ex2013 CU2 is installed on Win 2012 which has all the required prerequisites.
It only seems to apply to NON Admin users.
So far only 2 users have been migrated from ex2007 and 1 new user created on ex2013.
All 3 cant login to OWA.
It seems to load fine for a moment, I can see the inbox with this message:
Then when they try again, it says:
I did have the same issue for Admin accounts but I manged to resolve that by
This didnt help with other users as they already had the inherit selected.
Looking at the IIS logs I see these errors.
Looking at the event logs I see a warning:
I checked the AppPool and it is RUNNING.
I looked up the Toomany objects error and found some registry fix for Ex2010 but nothing on Ex2013. I applied it but it didnt resolve my issue. I set it to 40 but still got this message:
Rather than just increasing it more, i need to find out why its using all those objects.
I believe this issue started after upgrading to CU2. My test user connected fine to OWA before the update.
Ex2013 CU2 is installed on Win 2012 which has all the required prerequisites.
It only seems to apply to NON Admin users.
So far only 2 users have been migrated from ex2007 and 1 new user created on ex2013.
All 3 cant login to OWA.
It seems to load fine for a moment, I can see the inbox with this message:
Your Request cant be completed right now. Please try again later.but then it kicks them out back to login screen.
Then when they try again, it says:
something went wrong
A problem occurred while you were trying to use your mailbox
I did have the same issue for Admin accounts but I manged to resolve that by
Go under the user in AD and on their Security Tab I went to Advanced and checked the box to ‘inherit’ the parent settings
This didnt help with other users as they already had the inherit selected.
Looking at the IIS logs I see these errors.
GET /owa/ &ActID=fc9efcef-5f48-448e-9c09-e1bce 707fe01&ex =UE:Micros oft.Exchan ge.Data.St orage.TooM anyObjects OpenedExce ption 444 Domain\User
There was an error setting up WacConfiguration. Wac will be disabled and we will fall back to stellent. The WacUrlHostName was invalid. Expected a valid Uri. Actual value was ''. Value read from 'OrganizationConfig'
Looking at the event logs I see a warning:
A process serving application pool 'MSExchangeSyncAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3956'. The data field contains the error number.
I checked the AppPool and it is RUNNING.
I looked up the Toomany objects error and found some registry fix for Ex2010 but nothing on Ex2013. I applied it but it didnt resolve my issue. I set it to 40 but still got this message:
Mapi session /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=3 4c38d3c155 f45f4a10f4 c5e091aa24 0-ittest3 with client type OWA exceeded the maximum of 40 objects of type Session.
Rather than just increasing it more, i need to find out why its using all those objects.
I believe this issue started after upgrading to CU2. My test user connected fine to OWA before the update.
Please check this blog to find whether you are in the same situation..
http://terenceluk.blogspot.in/2013/10/exchange-server-2013-owa-throws-error.html
http://terenceluk.blogspot.in/2013/10/exchange-server-2013-owa-throws-error.html
ASKER
Wow that is a lot of steps, none of which I did. Ill have to look at that in more detail.
I really hope I dont have to redo my exchange. I already moved 3 users, can I use the same process to move them back to 2007 database?
I really hope I dont have to redo my exchange. I already moved 3 users, can I use the same process to move them back to 2007 database?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ended up updated Exchange to CU3 and then setting up http to https redirection.
The issue went away completely.
The issue went away completely.
ASKER
When manually specifying HTTPS and then logging in, it loads fine.
I tried 3 different methods of getting the HTTP redirect workig with no luck.
http://msexchangeguru.com/2013/10/30/http-redirect-owa-ecp/
http://www.jppinto.com/2009/04/automatically-redirect-http-requests-to-https-iis-7/
And also a default redirect file with this code:
None of them redirected http to https