[manmtn99]

Hi,
We had some network infrastructure issues caused by one of our AD controllers failing, affecting DNS. This has been resolved and all systems are now working fine once we updated their DNS settings and flushed services etc. Unfrotunately, our BES server seems to have a problem connecting to the Exchange 2003 environment. During startup, I see the following message in the log: "Agent 1 failed to initialize within 30 seconds" same for agent 2. After ten attempts, it stops and issues a message saying it won't try again for 24 hours.

When I go into the Blackberry Server Configuration and click on the Edit MAPI Profile button, I get the following "The MAPI subsystem cannot be correctly initialized and used. Please make sure MAPI is installed and configured properly".

I have checked the MAPI and it all seems fine, even so far as sending a test email from the BES manager to a test user. However, we can't seem to get any communication out to the devices. Have checked comms and can get to the Blackberry router all ok.

Anybody got any thoughts or hints? Running BES 4.1.0.40 with Exchange tools installaed.

[gziz]

switch service account will fix that.

[manmtn99]

Thanks. I gave it a whirl but still the same.

[Dobbin]

Can you open Exchange System manager on the BES and can you manage the Org?

When you say you managed to send a mail from BES Manager to a test user where did you do this from and how? outlook cannot be installed on the BES so did you open its mailbox from somewhere else? in which case this just shows that its mailbox is alive.

Check the GC the BES is using - is it the DC that died? :

BlackBerry Search Results

[manmtn99]

Thanks Dobbin.

I sent an email Blackberry Manager-Security Administrator Authority/Users/Send Message. See attached. THis was delivered successfully to the Outlook inbox of the user. Also, If you initiate Enterprise Activation from the BB, the RIM_bca28a80-e9c0-11d1-87fe-00600811c6a2 message appears in the Outlook inbox too. THis means to me that the BES is talking to Exchange ok and that the BES is receiving requests from the BB.

I'll check out the GC situation shortly.

[Dobbin]

I would tend to agree. If you can send a message from the console then I would think its connection to at least its own mbx is up and working. That enterprise activation mail arrives in a mbx means only that the mailbox exists and has an external address - I take it the ent act mail doesnt get removed from the mbx?

I would expect not if the BES cant talk to it. What does MAGT say? Up the log level to 4 and give the controller a restart...

[manmtn99]

All fixed. I ended up going into the Exhcange System Manager and for each server "resetting" the read/write access for the BESADMIN account. All started working after a restart of the BES.