The BES is running on windows server 2000.

BES version 4.1.6.9

Exchange 2003 is running on windows server 2003.

At the weekend I did an off-line defrag on our exchange database, I also defraged the hard drive on the BES.

When I came back into work today, I saw a lot of mapi errors in the app logs on the BES server, users also complained about not being able to send and receive emails.
I restarted the server, as I have seen this before whilst taking the exchange server off-line. After restarting still no success, and received these in the app logs.

Type: Warning
Source: Blackberry Messaging
Event ID: 20134
MailboxManager::SubsystemInitialize - MAPILogonEx (0x80040111)

Type: Error
Source: BlackBerry Messaging
Event ID: 10277
BlackBerry Messaging Agent server-name Agent 1 failed to start: Error code 5302


Then these pop-up every 1 minutes.


Type: Warning
Source: Blackberry Controller
Event ID: 20406
'server-name' agent 1: will not restart - reached the maximum of 10 restarts per 24 hours

Up to now I have deleted the mapi user from the registry and then tried to recreate it again with the Blackberry Server Config tool, but I then get these errors when trying to add the mapi profile.

The name could not be resolved. Network problems are preventing connection to the Microsoft Exchange Server computer. Contact your system administrator if this condition persists.
and then this

The name could not be resolved. The action could not be completed.

I have also reinstalled ESM, and then patched the server so the CDO.dll and MAPI32.dll files are the same version as the exchange server.

But I still can't add the mapi profile. This all is done whilst logged on as the BES admin account.

OMG, why did you do an offline defrag of your Exchange database? Please tell me Microsoft told you to, or you moved a whole slew of mailboxes out of the database.

1) Restart the BES
2) zip up the logs from today and email them to me at and I'll post back anything relevant (include a link to this thread too please).

I'd say just give this a read: KB00075 - Service failed to start, generating error 5302 ... but that is a whole different ball of wax / amount of work to do that you may not need to do.

I did an offline defrag because I archived off a load of mailboxes.

I will email you the logs later.

Is the global catalog dc working properly? The one that exchange points to?

Yes it is working fine.

Give this a read and try it now if you can: KB00075 - Service failed to start, generating error 5302 (this error is showing up in the MAGT log)

I have gone through that, and I have also tried creating a new BlackBerry Enterprise Server service account. But I still am getting the same errors when trying to add the new mapi profile, to the bes.

Error when adding new mapi profile:

The name could not be resolved. Network problems are preventing connection to the Microsoft Exchange Server computer. Contact your system administrator if this condition persists.

and then this

The name could not be resolved. The action could not be completed.

try this:

login to a PC with Outlook as the BESAdmin account ... can you create a MAPI profile as that user?

Yes, can do that.

... so did that work on the PC? Sorry, I'm not clear if you tried it with success or if you just indicated it was something you could try.

It was successful.

I installed the BES on one of our existing win 2003 servers whilst I tried to fix the problem with adding the mapi profile. It has been running fine on that server ever since.

I have just installed Windows 2000 server on a spare server we have, and then installed BES on it. Guess what happened, when asked to add the mapi profile I am getting the exact same error.

Could it be a problem with a service pack? I did fully patch the server before installing BES.

Has anyone any more thoughts.

Also when I try to access the "logons" folder under "Mailbox Store" in esm on the problematic windows 2000 server I receive the error below.

An error occurred while retrieving the requested information. The Microsoft Exchange Information Store service is not running or the Microsoft Exchange server computer is unavailable.

ID no: c103074d
Exchange System Manager


I also receive the same error when trying to access any Public Folders in esm on the win2k server.

And when installing the BES on a win2k server I receive this warning.

Mismatched Microsoft Data Access Component(MDAC) versions recorded in the registry.

We do have https configured for owa. Could that be causing a problem?

I would like to add as well this is only happening on win2k servers. When installing BES on a win 2003 servers, I can create the mapi profile fine, and I do not get any errors in esm.