Blackberry devices won't activate with BES 4.1.3 with Exchange 2007
BlackBerry Enterprise Server 4.1.3 with Exchange 2007
I’ve installed the blackberry enterprise server version 4.1.3 on a stand alone machine. Server 2003 R2 w/ SP2 and all security updates installed. I followed the prerequisites and installation instructions provided by blackberry and the installation went really smooth. Because of some questions I even had blackberry on the phone for the BES installation and they ensured it took successfully.
My issue is that blackberry device won’t activate and connect to the BES. I spent time on the phone with blackberry (2 hours) and they verified the exchange 2007 permissions and everything looks fine. We even created a second BES admin account incase there were issues with the first account.
Their final comment was that the blackberry server was configured correctly but couldn’t communicate with Exchange 2007 due to permissions issues. The final test would be to login as the BESAdmin account on a workstation, create an Outlook profile to the exchange server then try to open other users mailboxes. When that works then the devices would sync fine.
The one item I’m questioning is that this is the blackberry enterprise server that is provided when you sign up for a free user license. I asked support about this and they say it’s not an issue and is the same as the regular enterprise server.
I’m stuck and need some help here. Is anyone having the same issue. Below is some additional information:
The exchange commands used are in the following blackberry knowledge base article. They have been run and verified.
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB12483
I can check a user account in active directory users and computers and the besadmin account does have the send as permissons.
Event Log Errors:
BlackBerry Support states this error is because the bes server can’t communicate with the users mailbox.
Event Type: Warning
Event Source: BlackBerry Messaging Agent BB01 Agent 1
Event Category: None
Event ID: 20154
Date: 11/24/2007
Time: 9:22:55 AM
User: N/A
Computer: BB01
Description:
User helpdesk not started
BlackBerry Support states this error is because the bes server can’t communicate with the users mailbox.
Event Type: Warning
Event Source: BlackBerry Messaging Agent BB01 Agent 1
Event Category: None
Event ID: 20265
Date: 11/24/2007
Time: 9:22:55 AM
User: N/A
Computer: BB01
Description:
{helpdesk@intertexcompanie
Thanks for any and all suggestions.
I’ve installed the blackberry enterprise server version 4.1.3 on a stand alone machine. Server 2003 R2 w/ SP2 and all security updates installed. I followed the prerequisites and installation instructions provided by blackberry and the installation went really smooth. Because of some questions I even had blackberry on the phone for the BES installation and they ensured it took successfully.
My issue is that blackberry device won’t activate and connect to the BES. I spent time on the phone with blackberry (2 hours) and they verified the exchange 2007 permissions and everything looks fine. We even created a second BES admin account incase there were issues with the first account.
Their final comment was that the blackberry server was configured correctly but couldn’t communicate with Exchange 2007 due to permissions issues. The final test would be to login as the BESAdmin account on a workstation, create an Outlook profile to the exchange server then try to open other users mailboxes. When that works then the devices would sync fine.
The one item I’m questioning is that this is the blackberry enterprise server that is provided when you sign up for a free user license. I asked support about this and they say it’s not an issue and is the same as the regular enterprise server.
I’m stuck and need some help here. Is anyone having the same issue. Below is some additional information:
The exchange commands used are in the following blackberry knowledge base article. They have been run and verified.
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB12483
I can check a user account in active directory users and computers and the besadmin account does have the send as permissons.
Event Log Errors:
BlackBerry Support states this error is because the bes server can’t communicate with the users mailbox.
Event Type: Warning
Event Source: BlackBerry Messaging Agent BB01 Agent 1
Event Category: None
Event ID: 20154
Date: 11/24/2007
Time: 9:22:55 AM
User: N/A
Computer: BB01
Description:
User helpdesk not started
BlackBerry Support states this error is because the bes server can’t communicate with the users mailbox.
Event Type: Warning
Event Source: BlackBerry Messaging Agent BB01 Agent 1
Event Category: None
Event ID: 20265
Date: 11/24/2007
Time: 9:22:55 AM
User: N/A
Computer: BB01
Description:
{helpdesk@intertexcompanie
Thanks for any and all suggestions.
Check the cdo.dll and Mapi32.dll file and make sure the versions are the same on your Exchange server as they are on BES. Exchange should match BES.
ASKER
Thanks for the suggestion. Here's what I have. I'll have to check to see which one is being used by the exchange server and to see what the ramifications are of making some changes.
CDO.dll This is the same on blackberry and exchange
6.5.7940.0
MAPI32.dll in c:\windows\system32 on exchange
1.0.2536.0
MAPI32.dll in c:\windows\SysWOW64 on exchange
6.5.7940.0
MAPI32.dll on blackberry
6.5.7940.0
CDO.dll This is the same on blackberry and exchange
6.5.7940.0
MAPI32.dll in c:\windows\system32 on exchange
1.0.2536.0
MAPI32.dll in c:\windows\SysWOW64 on exchange
6.5.7940.0
MAPI32.dll on blackberry
6.5.7940.0
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the response. Your installation guide is nice. My issue was recently resolved believe it or not by restarting the exchange server and domain controller. I only noticed this because the servers were due for maintenance of Microsoft security updates. According to the blackberry documentation the servers shouldn't have to be restarted. Sadly I'm not sure which server restart resolved the issue.
Hi, I assume by now you have installed at least SP6 and MR5 on your BES to improve compatibility with Exchange 2007. If possible can please close this question if you no longer require assistance? Thanks you.