[rasobey]

Hi all

I was hoping that my recent upgrade to SP6 (BES 4.0, ExchSvr 2003 SP2) would solve this intermittent problem but it seems not. I have had a user contact me and say his BB has suddenly stopped receiving messages. The first time I can see any errors on my BES server event log relating to this user is:

CalICSAgent:: - LoadSyncInfo Open Root Folder(0x80070005) failed for user.

Where user is the email address of the user having problems.

Following that are loads of event errors:

CalICSAgent::Synch: Could not reload synchronization state for user.
{user} DoICS() failed: ERR_FAIL
{user} CalSyncState::GetSyncStateTable - GetContentsTable(0x80040115) failed.
{user} CalSyncState::QueryByRefId - GetSyncStateTable failed.
{user} CalSyncState::BuildStateRecordMap - GetContentsTable(0x80040115) failed.
{user} CDOCalendar::ConsistencyCheck - ConsistencyCheck failed.
{user} Unable to save configuration settings or statistics.
{user} RescanPIMItems - Failed getting contents table (type=Memos) (0x80040115).
{user} ReloadPagerStats() failed

etc.

I've tried going through reactivation procedures with him and he gets an error "No response from server" (this isn't verbatim). Other BlackBerry devices are not affected, and nothing has changed on the Exchange Server.

My last trick, before bouncing the BES server (which is known to fix this in my experience) was to remove him from BES overnight and readd him this morhing. I am waiting to see if this has resolved the issue.

In the meantime, can anyone decipher what may have happened?

Thanks

Richard

[wusmani]

"Open Root Folder(0x80070005) failed for user"


This error indicates a permission problem. Make sure the BESAdmin should have "create named properties" permissions applied to it. Or you may have to give full Exchange Administrator permissions (from the delegate control option).

[rasobey]

Thanks Wusmani, I appreciate your reply. I'd like to say that I "know" this isn't related to permissions. However, I can't be 100%. Let me elaborate:

I've done some more testing on this now. This issue occurs when a milbox is moved to a specific storage group/mailbox store on our Exchange servers. The BB just stops working, and stays that way until one of the following is true:

1) The BES is restarted.
2) The mailbox is moved to a different mailbox store.

All the properties for the mailbox store in question are inherited from the Storage Group, and the other mailbox stores are working as normal.

IEMSTEST output is as follows:

<blah's> Mailbox opened successfully.
Root Folder opened successfully.
Folder created successfully.
Test folder deleted successfully.
Test completed successfully for <blah>.

I'm pretty stuck now.

[|||||||]

Yeah it's not permissions, have you run the handheldcleanup utility? Also if you move a user from one storage group on one Exchange server to another storage group on the same Exchange server it will not move untill you restart the BES.

[rasobey]

I haven't run handheldcleanup without being on the phone to my SPs tech support, so not sure of the correct syntax and any reprocutions of getting it wrong.

[rasobey]

Originally Posted by |||||||

Yeah it's not permissions, have you run the handheldcleanup utility? Also if you move a user from one storage group on one Exchange server to another storage group on the same Exchange server it will not move untill you restart the BES.

I've just realised what's going on, I think. Yes, the mailboxes are being moved to a different mailbox store on the same server. I assume it's irrelevant whether it's in the same storage group, so long as the mailbox is not leaving the server?

[wusmani]

My bad. ||||||| is right, the handheldcleanup.exe tool should do the trick in this case.

[jrbes]

Same server different store, you will need to restart the controller\Synchronization services on the BES for the changes to be noticed.