[kariger]

Hi all

Let me try to explain my issue :

I have 2 BB Server - BB1 and BB2
I have 1 Exchange Server Clustered - CN1 and CN2.

My issue is :

When my exchange server is on CN1 , everything is OK - people receive mails, etc .. and the IEMSTEST is OK with BB1 and BB2 !
Now , if i move my exchange server on the CN2 :

BB1 can resolve the information store with IEMSTEST , and people receive mails.
But BB2 can not resolve the information store with IEMSTEST and people can not receive mail !

The error is : OpenMsgStore failed (8004011d) blackberry

I looked on the internet for a solution and i already check this :

Dll version of CDO.DLL and MAPI32.DLL , they re all in 6.5.7654.12 version.
BESADMIN right on the information store seems OK ! because BB1 can browse it!
I re-created the MAPI profile on BB2, but no change appears.
Of course , i already rebooted all server !

If you have any idea what happen during the migration between CN1 to CN2 , please help me !

If you need any log , or anything else , do no hesitate to contact me !

regards

Kariger

[bl0rb]

Hello from germany,

if you have moved the store/user try "handheldcleanup.exe -u".

Greetzz

bl0rb

[kariger]

Hello from Luxembourg !!

I did like that : ( Besname = BB server name ? )

BlackBerry Enterprise Server Utility - HandheldCleanup.exe, Version 2.0
Copyright (c) Research In Motion, Ltd. 2000-2001. All rights reserved.
Attempting MAPILogon....
MAPILogon Success.
Opening Default Message Store Mailbox - BESADMIN.
Please Enter BESName: -> be201msad
Scanning handhelds....this may take a while...
Update Handhelds Complete
HandheldCleanup.exe finished

And i tried again iemstest - same error !

It's very frustrating !!!

[freakinvibe]

Your BES Mapi Profile should point to the cluster resource name and not to the physical server names. So it should not point to CN1 or CN2. Check this by going to the "Blackberry Server Configuration" Applet. On the "Blackberry Server" tab, click on "Edit MAPI Profile".

[kariger]

Hi

I verified my BB1 and BB2, and it seems pointing to the EVS Name and not to my cluster node name(physical name) !

regards

[kariger]

Hi

I solved the problem ,

i re-create an new local profile and re-configured everything step by step with success !!

Many thanks for your help !

Kariger