[Mikeyy]

Hi, having trouble getting this Blackberry Enterprise version 4.1 working.

quick run down of what i've got,

Small business server 2k3 running as the exchange server /w service pack 1.
server 2k3 standard running with BES installed /w exchange systems manager /w service pack 1 installed.
on the BES machine, logon setup as BESAdmin as a user on the domain, and administrator on the local machine.

on the exchange server i have enabled the send as permission on the BESAdmin account and followed the user documents to install the software.

I had no problems through the install with any errors.

1 weird thing happened though, was looking through the event viewer and noticed some errors about the MAPI profile, when i went to the Edit MAPI profile icon, my exchange server and username wasn't in the fields anymore, which i had entered during the initial install. i've re-entered these details and it finds the exchange server/user account fine.

when i go into the blackberry server configuration and go to the Blackberry server tab, when i click on edit MAPI profile, an error message appears that says - the MAPI subsystem cannot be correctly initialized and used. Please make sure MAPI is installed and correctly configured. Where can i look/change settings to resolve this issue, as the event viewer is also showing another error about a service not starting which is below -

Event Type: Error
Event Source: BlackBerry Messaging Agent BESMACHINE Agent 1
Event Category: None
Event ID: 10277
Date: 24/05/2007
Time: 11:01:57 AM
User: N/A
Computer: BESMACHINE
Description:
BlackBerry Messaging Agent BESMACHINE Agent 1 failed to start. Error code 5302

Any help is greatly appreciated, as i keep going around in circles trying to find the problem!!

Thanks, Michael.

[ians]

Has anyone resolved this problem?

[ians]

... and i dont have any other problem than this one with agent1 ... dunno what to do with this .. all seems fine, everything works ... excluding agent1

[Oderus]

Have you verified that your mapi.dll's are the same version on Exchange as they are on the BES?

[ians]

Originally Posted by Oderus

Have you verified that your mapi.dll's are the same version on Exchange as they are on the BES?

Thx for help,
I know this possibly stupid question, but how can i comare them?

[jymkata]

Right-click -> Properties -> Version tab

[ians]

btw, im newbie in bes .. so possibly there also some other errors :

While im starting BES Manager as Administrator it shows me warning message "Failed to open the default message store using the MAPI Profile 'BlackBerryManager'. Please review the log for details ...."
If i logged as BESAdmin no such message appears, and all seems fine excluding this error with agent1.

More strange thing, in BB Server configuration pressing MAPI profile :
As BESAdmin : warning message "The MAPI subsystem cannot be correctly initialized and used. Please make sure MAPI is installed and configured properly."
In events i've got this :
Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1009
Date: 5/30/2007
Time: 6:03:41 PM
User: N/A
Computer: **********
Description:
Failed to access the metabase, error code is 80040154 (Class not registered).

For more information, click http://www.microsoft.com/contentredirect.asp.

If i logged as Administrator : all ok.

What all this means and how can a slove this problem?
Thx a lot.

[ians]

Originally Posted by jymkata

Right-click -> Properties -> Version tab

i dont have any mapi.dll on my exchange system, bes are on the same.

i've alredy :
* re-install ( all is fine, no errors )
* removed mail profiles
* tested exch storage
* pass all checklist

a lil help please, do i miss something?

[hitty]

Originally Posted by Mikeyy

Event Type: Error
Event Source: BlackBerry Messaging Agent BESMACHINE Agent 1
Event Category: None
Event ID: 10277
Date: 24/05/2007
Time: 11:01:57 AM
User: N/A
Computer: BESMACHINE
Description:
BlackBerry Messaging Agent BESMACHINE Agent 1 failed to start. Error code 5302

Any help is greatly appreciated, as i keep going around in circles trying to find the problem!!

Thanks, Michael.

Managed to sort this with the BlackBerry KB00075