"Failed to read 001e6602 reg value from the BlackBerry MAPI profile" appears in the BlackBerry Messaging Agent log file or "One or more errors occurred, BlackBerry enabled users were not created" error message is received when attempting to add users

Article ID: KB19074

Type: Support Content

Last Modified: 06-19-2012


Product(s) Affected:

  • BlackBerry Enterprise Server for Microsoft Exchange
  • BlackBerry® Enterprise Server 5.0 to 5.0 SP1
  • BlackBerry® Enterprise Server Express
  • DT 561893

To validate this issue, gather the installation log (install_log.txt) from the default directory C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer and search for the local computer Internet Protocol (IP) Address, as shown in the following example:

Installer log snip:

[30000] (03/09 12:24:51.157):{0x1D28} [ENV] Local machine IP Address =
[30000] (03/09 12:48:10.606):{0x1F28} <5>Mar 09 12:48:10 BESSERVER {0x1F90} 0347: (#30000) [PIPTOOL]: ConvertNameToIPAddress found IP of [192.168] for [BESSERVER ], code [0]
[30000] (03/09 12:48:10.606):{0x1F28} <5>Mar 09 12:48:10 BESSERVER {0x1F90} 0348: (#30000) [PIPTOOL]: Edit MAPI profile could not determine Exch server IP and local IP match result was 0
[30000] (03/09 12:48:18.005):{0x1F28} <5>Mar 09 12:48:17 BESSERVER {0x1F90} 0349: (#30000) [PIPTOOL]: Edit MAPI profile sets ENABLE_EXCHANGE_LEGACY_PROFILE_CONFIG_TRAIT of 0

In the BlackBerry Messaging Agent (MAGT) debug log, lines similar to the following should appear:

[50076] (07/14 18:05:16.725):{0x1F2C} Starting BlackBerry Mailbox Agent 1 for Server mail - Version 5.0.0
[30054] (07/14 18:05:16.908):{0x1F2C} Starting Message System
[30055] (07/14 18:05:16.909):{0x1F2C} Using MAPI profile BlackBerryServer
[40206] (07/14 18:05:16.911):{0x1F2C} MailboxManager::SubsystemInitialize - Using MAPI profile 'BlackBerryServer'
[20137] (07/14 18:05:16.922):{0x1F2C} MailboxManager::SubsystemInitialize - OpenMsgStore (0x80040111)
[30000] (07/14 18:05:16.923):{0x1F2C} [ENV] MAPI32.DLL: C:\Windows\system32\MAPI32.dll, Version: 1.0.2536.0
[30000] (07/14 18:05:16.923):{0x1F2C} [ENV] CDO.DLL: C:\Program Files (x86)\ExchangeMapi\cdo.dll, Version: 6.5.8069.0
[30000] (07/14 18:05:16.924):{0x1F2C} [ENV] Failed to read 001e6602 reg value from the BlackBerry MAPI profile.
[30000] (07/14 18:05:16.924):{0x1F2C} [ENV] BlackBerry Mailbox Agent 1 - BESX Version
[30000] (07/14 18:05:16.924):{0x1F2C} [ENV] BES Service Name: BlackBerry Mailbox Agent
[10277] (07/14 18:05:16.932):{0x1F2C} BlackBerry Messaging Agent mail Agent 1 failed to start. Error code 5305
[50106] (07/14 18:05:16.932):{0x1F2C} Stopping BlackBerry Mailbox Agent 1 for Server mail

This issue can also be verified by the following warning in the Windows Event Log:

Event Type: Warning
Event Source: BlackBerry Controller
Event Category: None
Event ID: 20406
The description for Event ID ( 20406 ) in Source ( BlackBerry Controller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 'BESSERVER' agent #: will not restart - reached the maximum of 10 restarts per 24 hours.


When the BlackBerry Enterprise Server is installed locally on the Microsoft® Exchange Server, the EnableLegacyProfileConfig trait is not set to True during the installation if the IP addresses contain a zero (for example, becomes 192.168). The installer is prevented from detecting that the BlackBerry Enterprise Server and Microsoft Exchange Server are on the same server. The EnableLegacyProfileConfig trait is not set during the installation because of the truncated IP addresses. The BlackBerry Messaging Agent fails to start and error code 5305 is displayed. Also, the Messaging Application Programming Interface (MAPI) profile referencing the Global Catalog Server in the registry is either missing or incorrect.

This is caused by a Kerberos™ authentication failure and may also occur when the BlackBerry Enterprise Server is installed on its own server if there are underlying issues related to Kerberos. The same resolution can be applied.


Upgrade to BlackBerry Enterprise Server 5.0 SP2.

If you are using BlackBerry Enterprise Express (Bundle 5) and are affected by this issue, complete the following steps as this issue has been addressed in BlackBerry Enterprise Server Express (Bundle 12).

  1. Uninstall BlackBerry Enterprise Server Express (Bundle 5).
  2. Download and install BlackBerry Enterprise Server Express (Bundle 12).

If BlackBerry Enterprise Server Express 5.0 SP1 (Bundle 5) has been installed and is affected by this issue, follow the steps from the preceding resolution section or request a Structured Query Language (SQL) script that has been created by our development team to set the EnableLegacyProfileConfig trait to True in the database. To request the SQL script, contact BlackBerry Technical Support.

Note: The SQL script is only intended for use with BlackBerry Enterprise Server Express 5.0 SP1. It is highly recommended to review the instructions before running the script.

If this issue occurs with the BlackBerry Enterprise Server 5.0 SP1, run the Traittool.exe file that is available in the Tools folder of the installation folder for BlackBerry Enterprise Server 5.0 SP1. For BlackBerry Enterprise Server 5.0, an update to SP1 is required because there is no Trait available for EnableLegacyProfileConfig.

To run the Trait Tool to set EnableLegacyProfileConfig trait to True, complete the following steps:

  1. Stop the BlackBerry Enterprise Server services.
  2. Open a command prompt and navigate to the Tools folder where the trait tool is located.
  3. Type traittool –trait enablelegacyprofileconfig -server <server_name> -set true

    Note: Replace <server_name> with the machine name of the BlackBerry Enterprise Server.

  4. Restart the BlackBerry Enterprise Server services.

Important: Restarting the BlackBerry Enterprise Server delays email message delivery to BlackBerry smartphones. For more information, see KB04789.

Note: You can also enable enablelegacyprofileconfig at the global level by following the steps below:

traittool -global -trait enablelegacyprofileconfig -set true

CollapseAdditional Information
Note: Under no circumstances should manual manipulation of the database be used to resolve this issue.
This article contains information previously documented in KB21974.


By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.

Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.