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:
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-e1bce707fe01&ex=UE:Microsoft.Exchange.Data.Storage.TooManyObjectsOpenedException 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=34c38d3c155f45f4a10f4c5e091aa240-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.