[MarkJS]

Hi All,
OK after spending 2 days troubleshooting this and reading tons of threads I have run out of ideas. In brief I have the following setup:
• BES 4.1 connected to Exchange 2003
– Working OK I used the transporter to migrate 5 users to BES5 without issue.
• BES 5.0.3 on Windows 2008 R2 using SQL2008 connected to same Exchange 2003
– Working OK

Note these are independent BES and different service accounts/mailboxes.

We had around 5 test users on the BES 5.0.3 server before I followed the standard procedure to migrate the BESADMIN service mailbox to Exchange 2010. All went swimmingly there until the BES5 users no longer sync’d and no Exchange 2003 user can be activated (i.e. add new user).

So to confirm prior to the 2010 BESADMIN migration, these users Exchange 2003 worked without issue. What is more curious is that if I provision a 2010 mailbox on the newly migrated BES5 on 2010 they work! Just 2003 users that now fail.

The logs are not helpful and show the standard (MAGT Log) :

************************************************** ****
MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed, MailboxDN=/o=IBJ/ou=GBR1/cn=Recipients/cn=AlamKe, ServerDN=/o=IBJ/ou=GBR1/cn=Configuration/cn=Servers/cn=exch2003/cn=Microsoft Private MDB
[40720] (02/17 13:42:48.452):{0x17A0} MAPI call failed. Error 'The information store could not be opened.', LowLevelError 0, Component 'MAPI 1.0', Context 649
************************************************** ****

I have been back through the setup docs a number of times, but what still confuses me is that 2003 originally worked now fails, and 2010 works! The same serviceaccount/mailbox was used.

If I delete the 2003 user from the BES5 and recreate I get the *.ETP in my 2003 mailbox but it never moves. I checked the permissions on the service account and all good. I even logged into my mailbox using BESADMIN account (outlook) and could send and receive mails).

Any ideas would be a big help. Cheers all.

Cheers Mark

*MAGT LOG*

[knottyrope]

0x8004011d is usually permission related or a throtle policy not set.

there can also be a DNS limit imposed as well on your DC if on 2008.

[MarkJS]

Hi KR,

Yep read countless threads on the throttling policy, removed, re-added etc. I am on Exchange 2010 SP2 so applied the other changes I saw for SP1. As part of testing pretty much NULL'd everything.

I dont see any events on the exchange server re complaints and the 2010 mailboxes are fine on BES5 just 2003.

Re permissions I have been back through, prior to the migration I had a working 2003 user base and BES5, only when the BESADMIN was moved to 2010 it went belly up.

I am rebooting my 2003 server this weekend to see if this does anything.

I will look into the DC DNS idea, we have an empty root domain (schema) that is 2008 R2 and these are GC's.

[ctpuk]

Are the Ex 2010 and Ex 2003 servers in the same Exchange orgs - or are you moving to a new org?

[ctpuk]

Assuming it's the same org...

In Outlook - how is delegate functionality between a 2010 and 2003 mailbox? Is it behaving ok?

Did you run setup /PrepareLegacyExchangePermissions before installing Ex 2010?