Another Enterprise Activation issue

[j1akey]

I have a newly installed BES Express at a customer site. There is only a single blackberry currently that I need to connect but of course something that should be easy has turned into something difficult or something obvious that I'm just not seeing.

Anyway I can't get this single device connected. When I try to connect wirelessly I get the following message.

The Blackberry Enterprise Server has not responded to your
activation request. An error may have accurred.

I also get a similar message when I try to accociate the device to a user with it plugged into the server with a USB cable. I was not the one to install the server but from what I can tell from looking at it, it seems to be installed correctly.

Steps Taken:

1. Wireless activation. Didn't work.
2. Verified BES connection with Exchange. All services running as well.
3. Removed and re-added user to BES. Tried again. Nope
4. Verified with Verizon that the correct plan is on the phone. It is.
5. Tried to associate the phone with the user with a wired connection. Still doesn't work. Much swearing ensues.
6. Wiped handheld. Again tried a wireless and wired activation. Still doesn't work.

[dpeters11]

Originally Posted by j1akey

I have a newly installed BES Express at a customer site. There is only a single blackberry currently that I need to connect but of course something that should be easy has turned into something difficult or something obvious that I'm just not seeing.

Anyway I can't get this single device connected. When I try to connect wirelessly I get the following message.



I also get a similar message when I try to accociate the device to a user with it plugged into the server with a USB cable. I was not the one to install the server but from what I can tell from looking at it, it seems to be installed correctly.

Steps Taken:

1. Wireless activation. Didn't work.
2. Verified BES connection with Exchange. All services running as well.
3. Removed and re-added user to BES. Tried again. Nope
4. Verified with Verizon that the correct plan is on the phone. It is.
5. Tried to associate the phone with the user with a wired connection. Still doesn't work. Much swearing ensues.
6. Wiped handheld. Again tried a wireless and wired activation. Still doesn't work.

I haven't played with BESX, but everything I've seen, wireless activation is not available. Is this on an SBS server? Maybe this thread will help:
BESX Can't activate a device - BlackBerry Support Community Forums

[j1akey]

Found it! After many hours of investigation it appears there is a problem with the installer for BB Enterprise SP1 and Express SP1 when installed on to specific types of environments.


BB KB article KB19074

Products
BlackBerry® Enterprise Server for Microsoft® Exchange



--------------------------------------------------------------------------------

Environment
BlackBerry® Enterprise Server version 5.0 to 5.0 SP1
BlackBerry® Enterprise Server Express version 5.0 SP1
Issue Number 561893



--------------------------------------------------------------------------------

Overview
To validate this issue, gather the Install log ( Install_log.txt ) from the default directory "C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\Logs\Installer" and search for Local machine Internet Protocol (IP) Address as shown below with the similar log lines to the following:

Installer log snip :

[30000] (03/09 12:24:51.157):{0x1D28} [ENV] Local machine IP Address = 192.168.0.1 [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 debug log (MAGT), you should see lines similar to the following:

[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 5.0.0.110
[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

Additionally, you can also validate this issue from the Windows Event Viewer > Application Log, the following warning should be logged :

Event Type: Warning
Event Source: BlackBerry Controller
Event Category: None
Event ID: 20406
Description:
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.




--------------------------------------------------------------------------------

Cause
When installing the BlackBerry Enterprise Server version locally on the Microsoft Exchange Server, the EnableLegacyProfileConfig trait is not being set to true during the install if the IP addresses contained a zero within them (e.g. 192.168.0.1 became 192.168). This is preventing the installer from detecting that BlackBerry Enterprise Server and Microsoft Exchange Server are on the same server. As a result of this "EnableLegacyProfileConfig" trait is not being set during install due to truncation of certain IP addresses. Hence causing the BlackBerry Messaging Agent failed to start with Error code 5305 and the Messaging Application Programming Interface (MAPI) profile referencing the Global Catalog Server in the registry is either missing or incorrect.




--------------------------------------------------------------------------------

Resolution
This is a previously reported issue that has been escalated internally to our development team. No resolution time frame is currently available.




--------------------------------------------------------------------------------

Workaround
A Structured Query Language (SQL) script has been created by our development team to set the EnableLegacyProfileConfig trait to true in the database. To request this script, please contact our Technical Support at 1-877-255-2377 and refer to "ESRQ00002132".

Please ensure that the Instructions for running the script is followed in detail before running the script.

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




--------------------------------------------------------------------------------

Additional Information
Note: Under no circumstances should manual manipulation of the database occur due to this issue.

[trd2turbo]

It's a timeout. I ran into that when the email that BES sends to the user mailbox was getting caught up either in the email firewall or other. I forced it through a few times and once the email hit the mailbox, it activated OTA just fine.

Looks like your may be different but fyi..