04-16-2013 10:26 AM - edited 04-17-2013 04:01 AM
we migrate our Exchange 2010 to Exchange 2013.
Now we have a second BES Server. this Server connects directly to the Exchange 2013 CAS with a second besadmin account with a ex2013 mailbox over EWS (KB33406). If i transport a user from Exchange 2010 to Exchange 2013 the 2013 BES cant find the right Server DN in GAL. Handheldcleanup.exe fix this issue but only 10 minutes. After this time the Server DN switch back to the old Exchange 2010 Server CAS Array DN.
Is there a fix for this Problem?
MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d)
ServerDN=/o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=OLDCASARRAY/cn=Microsoft Private MDB
Current ServerDN /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=GUID@DOMAIN/cn=Microsoft Private MDB (Right)
Previous ServerDN /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=OLDCASARRAY/cn=Microsoft Private MDB (Wrong)
Thnaks for help
Solved! Go to Solution.
04-25-2013 12:26 PM
Welcome to the BlackBerry® Support Community Forums.
There’s no supported solution as this is not a known issue and further in-depth investigation would be required. We would suggest contacting BlackBerry Technical Support: http://ca.blackberry.com/customer-service/contact-
Let us know if you have any questions.
04-29-2013 04:26 AM
we fixed the Problem!
1. disable LDAPSearch (Registry)
2. Create a thorttling policy with unlimited not $null
New-ThrottlingPolicy BESPolicy2013 -RCAMaxConcurrency unlimited –EWSMaxConcurrency unlimited –EWSMaxSubscriptions unlimited -CPAMaxConcurrency unlimited
04-29-2013 10:38 AM
thanks for sharing your solution with us
05-01-2013 06:49 AM
We are experiencing the same issue with the wrong server being reverted back after 10 minutes. Running the handheldcleanup tool puts it back to the correct messaging server, only for it to revert shortly afterwards.
Can you elaborate on your fix and also let us know whether you have experienced any further issues associated with the fix? Disabling the LDAPSearch, will that effect lookups or population of newly added users?