[Hannah814]

Are you picking a users name when running the IEMStest? Ie run it and when you select a user run it for yourself to test the permissions.

I had a similar problem with a bes that migrated users from exchange 2003 to exchange 2010! When I ran the IEMstest it was picking up the wrong exchange still. Very strange.

If you create a test user that was created on the exchange 2010 (Don't use a user from the old exchange) can you add them and provision a blackberry up for them on the new BES?

Have you checked the besadmin permission such as Administer information store also?

[Hannah814]

Should have said they way I combated it in the end after days and days of trouble shooting was to create a brand new BESadmin account straight on the exchange 2010 with fresh permissions etc. Then reinstalled the BES onto the new BESadmin user account. I never really got to the bottom of what was wrong. However it fixed it!

[DSHThomsons]

Thanks Hannah, Just re-ran it, created a new profile with my username and no joy, brings back the same error. Will try a new test user created on 2010 and come back to you.

Thanks for the help so far

[fadmin]

Originally Posted by DSHThomsons

Thanks Freakinvibe.

We set a new user up on 2010 and then tried them on bes 5 and that didnt work, will sett up a new user on 2003 and then try them on BES 5 and come back to you.

Before I do though, I am going to run with Hannah814 suggestion as the problem seems to lie in connecting to the MSGStores.

So have you tried what freakinvibe suggested to you?

[DSHThomsons]

OK tried a new user from 2010, put them onto bes 5 - not working.

I have working BB users on 2003, tried moving one of them over, transporter reports that migration is complete, but the device does not work.

Shall I still create a new user on 2003 and set them up directly on bes5 ?!

[fadmin]

yes, and if it does not work then probably bes 5.0 is the first issue, among others. Is besadmin mailbox on 2010 or 2003 exchange?

[DSHThomsons]

Hi fadmin, this also failed in the same way as the others :(

[timmyBES]

Originally Posted by DSHThomsons

Just to update after making changes to the BES Throttling Policy I still have the same issues.

When I run the IEMSTest tool I still get

Profile:
BlackBerryServer

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\besadmin>"C:\Research In Motion\BlackBerry Enterprise Server 5.0.0\tool
s\IEMSTest.exe"
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Vers
ion 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
OpenMsgStore() for this profile failed (8004011d)
C:\Users\besadmin>

Profile:
BlackBerryServer_MailStoreProfile

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\besadmin>"C:\Research In Motion\BlackBerry Enterprise Server 5.0.0\tool
s\IEMSTest.exe"
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Vers
ion 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
OpenMsgStore() for this profile failed (8004011d)
C:\Users\besadmin>

If anyone has ideas on how to troubleshoot this that would be appreciated !!

Thanks
Dom

You will receive this error if you are not running the IEMStest as the beasadmin account.

[DSHThomsons]

Hi,
I am running the IEMtest as the besadmin account and getting the error.

[DSHThomsons]

Originally Posted by fadmin

yes, and if it does not work then probably bes 5.0 is the first issue, among others. Is besadmin mailbox on 2010 or 2003 exchange?

The BESAdmin account was on 2003 but is now on 2010 exchange.

The uses on bes 4 are all still working (I actually thought when I migrated the BESAdmin account it would cause the bes 4 guys to fail, but it didint).

[fadmin]

So you have installed new bes using the same service account and different configuration database,right?

[timmyBES]

Did you run handheldcleanup after migrating mailboxes?
KB00140-How to use the handheldcleanup.exe tool when moving mailboxes in Microsoft Exchange 0 1150613326

[DSHThomsons]

Originally Posted by fadmin

So you have installed new bes using the same service account and different configuration database,right?

Yep, installed the new BES, using same service account (BESAdmin) and created a new DB on the new BES server using Transporter to migrate a few users over.

[DSHThomsons]

Originally Posted by timmyBES

Did you run handheldcleanup after migrating mailboxes?
KB00140-How to use the handheldcleanup.exe tool when moving mailboxes in Microsoft Exchange 0 1150613326

Hi Timmy, no I've not run that, will take a look now, cheers

[DSHThomsons]

Hi Guys,

Just to update you all where we are at the moment - the SRP has been disabled again (this is the second time) so our carrier is getting me a new one as we speak.

Whilst a new one is being generated, our carrier support guy logged on and took a look, found in the logs the error messages below:

BlackBerry Messaging Agent (SERVER NAME) Agent 1 failed to start. Error code 5305

BlackBerry Messaging Agent (SERVER NAME) Agent 2 failed to start. Error code 5305.

We are now waiting on a new SRP to come through.

[DSHThomsons]

Whilst waiting for the SRP to come through, I thought I'd look at the IEMSTest tool again.

Last night we ran a couple of commands on Exchange 2010 that bascially checked and applied the permissions to the BESAdmin account.

Now when I run the IEMSTest I get something different back, when I select the profile to use, I go for BESAdmin it then asks me to select a mailbox, I select the BESAdmin mailbox and it returns the below:

C:\Users\besadmin>"C:\Research In Motion\BlackBerry Enterprise Server 5.0.0\tool
s\IEMSTest.exe"
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Vers
ion 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
Opening Default Message Store Mailbox - BES Admin

BES Admin: Opening message store using
/o=T-BX/ou=first administrative group/cn=Recipients/cn=BESAdmin
/o=T-BX/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configurat
ion/cn=Servers/cn=THOMSONS-MAIL01/cn=Microsoft Private MDB
BES Admin: Mailbox opened successfully
BES Admin: Root Folder opened successfully
BES Admin: Folder created successfully
BES Admin: Test folder deleted successfully
BES Admin: MAPI test completed successfully
BES Admin: CDO Server Name: THOMSONS-MAIL01
BES Admin: CDO Mailbox DN: /o=T-BX/ou=first administrative group/cn=Recipients/c
n=BESAdmin
BES Admin: CDO logon successful
BES Admin: Get default calendar folder successful
BES Admin: Get calendar folder name successful: 'Calendar'
BES Admin: CDO test completed successfully
BES Admin: No Send As permission for the {T-BX\besadmin} account operator.

C:\Users\besadmin>

When I run it using my profile, using my mailbox I get:

C:\Users\besadmin>"C:\Research In Motion\BlackBerry Enterprise Server 5.0.0\tool
s\IEMSTest.exe"
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Vers
ion 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
Opening Default Message Store Mailbox - BES Admin

MY USER NAME: Opening message store using
/o=T-BX/ou=first administrative group/cn=Recipients/cn=Dominic.Hibbert
/o=T-BX/ou=first administrative group/cn=Configuration/cn=Servers/cn=TBX
-EXCH01/cn=Microsoft Private MDB
MY USER NAME: Mailbox opened successfully
MY USER NAME: Root Folder opened successfully
MY USER NAME: Folder created successfully
MY USER NAME: Test folder deleted successfully
MY USER NAME: MAPI test completed successfully
MY USER NAME: CDO Server Name: TBX-EXCH01
MY USER NAME: CDO Mailbox DN: /o=T-BX/ou=first administrative group/cn=Recipi
ents/cn=Dominic.Hibbert
MY USER NAME: CDO logon successful
MY USER NAME: Get default calendar folder successful
MY USER NAME: Get calendar folder name successful: 'Calendar'
MY USER NAME: CDO test completed successfully
MY USER NAME: No Send As permission for the {T-BX\besadmin} account operator.


C:\Users\besadmin>

[Hannah814]

All my BES's come back with Send as permission failed on exchange 2010 as well. It has got the send as permission though! So figured if it aint broke don't fix it!

Is this the 3rd SRP key you have had? I would be more concerned that something is disconnecting it. for instance: KB18566-SRP connection is disconnected after upgrading to BlackBerry Enterprise Server version 5.0

[fadmin]

It sounded like something is not right with SRP and that's why I asked you if you used the same SRP as in BES 4.1.

If I was I I would have removed bes 5.o completally.
-Wait for new srp etc. from carrier and while waiting do following:
-Check permissions on new windows server (local server admin. logon as service,logon locally etc)
-If windows 2008 R1 or R2 disable IPv6 and firewall.
-check permissions of BESAdmin service account on exchange.
-Make sure your exchange 2010 hase latest rollup etc.
-Make sure you install latest cdo and mapi software.
-Read install guides

Once you receive SRPs etc do following:

-start install from scratch.
-Once done activate one test user from exchage 2003 on new BES5.0.2.
-If it works remove that user and do the same but activate (not migrate yet) one user whose mailbox is on 2010 on BES 5.0.
-If both works try migrating user from BES 4.1 (with mailbox still on 2003 exchange) to a new BES 5.0. Make sure it works.
-Then move mailbox of that user to a new exchange 2010 and see if that works too.

Good luck.

[DSHThomsons]

Damn, getting this now....

[PS] C:\Windows\system32>Add-ADPermission -InheritedObjectType User -InheritanceType Descendents -ExtendedRights Send-As
-User "BESAdmin" -Identity "CN=BES Admin,CN=Users,DC=T-BX,DC=COM"
Active Directory operation failed on tbx-dc1.T-BX.COM. This error is not retriable. Additional information: Access is d
enied.
Active directory response: 00000005: SecErr: DSID-03151E07, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : WriteError: (0:Int32) [Add-ADPermission], ADOperationException
+ FullyQualifiedErrorId : 39B13CB0,Microsoft.Exchange.Management.RecipientTa sks.AddADPermission

[DSHThomsons]

Hi All, just to update this is now working. I believe it was the BES Admin permissions on the databases when we migrated over to 2010 (even though the same BES Admin account was servicing BES 4 accounts fine from 2010, and for Exchange 2010 users).

I am going to speak to a techie from our carrier later, and see if we can spot what it was, if so I will post to let you know.

Thanks everyone for the help, in particular Hannah814 and fadmin!

Cheers
Dom