[Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 268
  • Last Modified:

BESx on server exchange 2013. Getting this error message

HI all,

for 4 weeks now this has been doing my head in...struggling with this but was wondering if anyone could shed some light or lead me into the right direction...

i followed a very good tutorial online of how to install besx on exchange 2013 and it was going well but for some reason this is the error i get when i use the besx tool to test the configuration...

Upon adding a user in the console, it all goes through, the user gets an automated activation code but when i try to activate it via their bb, nothing happens...i wasn't even getting as far as the automated email with an activation code...i found out that i had to create a public folder in exchange ecp to get this to work.

please help :(

this is the error code:

C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\Utility>
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Ver
ion 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
Opening Default Message Store Mailbox - BESx Admin

Manjinder Singh: Opening message store using
        /o=JBrom/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Rec
pients/cn=c4f8435f1bbd439599ae7d96811a57ac-Manjinder Sin
        /o=JBrom/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Con
iguration/cn=Servers/cn=JBEX/cn=Microsoft Private MDB
Manjinder Singh: Mailbox opened successfully
Manjinder Singh: Root Folder opened successfully
Manjinder Singh: Folder created successfully
Manjinder Singh: Test folder deleted successfully
Manjinder Singh: MAPI test completed successfully
Manjinder Singh: CDO Server Name: JBEX
Manjinder Singh: CDO Mailbox DN: /o=JBrom/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)/cn=Recipients/cn=c4f8435f1bbd439599ae7d96811a57ac-Manjinder S
Manjinder Singh: CDO logon successful
Manjinder Singh: CDO COM exception: Code = 80040705, WCode = 0505, Code meaning
= IDispatch error #1285
    Description = The Microsoft Exchange Server computer is not available.  Eit
er there are network problems or the Microsoft Exchange Server computer is down
for maintenance. [Microsoft Exchange Server Information Store - [MAPI_E_FAILONE
Manjinder Singh: CDO test failed
Manjinder Singh: No Send As permission for the {JBROM\besxadmin} account o
Manjinder Singh: Initializing EWS Proxy... successful
Manjinder Singh: Configuring User... successful
Manjinder Singh: EWS calendar find request... successful

C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\Utility>
1 Solution
David Paris VicenteCommented:
Hi mfmsupport ,

I know that you mention Exchange 2013, but in the past same issues , were reported since Exchange 2000 and above.
So if you can give it a try follow this:
Take note of every configuration change that you made, backup is always good.

Lets check if you are using the exact DN for JBROM\besxadmin.

Here's how to determine the exact Distinguished Name...

1. On your Exchange Server launch Active Directory Users & Computers
2. Right-click on the very top node (it says "Active Directory Users and Computers") and select View | Advanced Features
3. Next, drill down in the tree, until you locate your user (besxadmin)
4. Right-Click on your besxadmin user and select "Properties"
5. Click on the "Attribute Editor" (You won't be editing anything in this tab ... you're just looking)
6. Scroll down in this list of attributes, until you find "distinguishedName"
7. Copy the entire Value

As a example this could be something like this "CN=besxadmin,OU=Special Purpose,OU=My Company,DC=mycompany,DC=com"

8. Now go back to the Exchange Management Shell and re-enter the entire "Add-ADPermission" command, this time using the Distinguished Name you found in ADUC.

Example: "Add-ADPermission -InheritedObjectType User -InheritanceType Descendents -ExtendedRights Send-As -User "besxadmin" -Identity "CN=BES Admin,OU=Special Purpose,OU=My Company,DC=mycompany,DC=com"

And try again the tests, if this doesn´t work let´s try other way

Let´s issue this cmdlet in exchange:get-CASMailbox <username> | FL

Check the value of the parameter on MAPIBlockOutlookNonCachedMode this should be False.

Also check if Microsoft Exchange Server has a registry key configured that blocks versions of MAPI:

Key Disable MAPI Clients

If nothing exists lets move on-

Configure the BlackBerry Enterprise Server to connect to the Microsoft Exchange Server 2013 without requiring public folders.
 Open the Registry Editor.
 Locate the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Messaging Subsystem\CDO.
 Within the registry key, create a Dword called Ignore No PF and assign it a decimal value of 1.
 Save the changes and then close the Registry Editor.
 Restart the BlackBerry Enterprise Server services.
 Restart BlackBerry Manager and check.

If this doesn´t work remove the key that you created.

Let us know if this help or leaded you on the good way.

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now