View Single Post
Old 08-28-2006, 01:14 AM   #2 (permalink)
Knows Where the Search Button Is
Join Date: May 2006
Location: Dubai
Model: 8700g
Carrier: Etisalat
Posts: 18
Post Thanks: 0
Thanked 0 Times in 0 Posts

The Activating... status stops responding for 10 minutes, retrying every 10 minutes with a Retrying... status. After 40 minutes, the process times out with this message:
The server is not responding. Please contact your System Administrator.

Causes for this behavior include the following:

An incorrect password was entered on the device multiple times.
The user account mailbox is full, or the messaging server is unable to send or receive messages.

Tip: To verify that you are able to send and receive messages, use your desktop email client to send and receive a standard message.

The wrong email address was entered for activation.

Tip: Validate the email address entered on the device during the activation process. If necessary, correct the address and retry the activation process.

Messages are routed to a PST folder (in Microsoft Exchange environments only). As a result, the BlackBerry Enterprise Server is unable to access the activation message.
The ETP message was deleted or modified by a anti-virus or message blocking software.

Tip: Check the messaging server to verify that it is not set to modify or block DAT files. Also, make sure that the domain is not blacklisted. For help, contact your mail server administrator.

The user account has not been added to the BlackBerry Enterprise Server, or the BlackBerry Enterprise Server administrator account does not have permissions to the user’s mailbox. As a result, ETP messages accumulate in the inbox. See KB-02276 for information on permissions.
The user’s BlackBerry message filters are configured to not redirect messages from the root Inbox folder, or the ETP message was moved to an Inbox sub-folder by message filters. Remove any filters that move these messages from the Inbox, verify that the filters in the BlackBerry Redirector settings are set to redirect messages from the Inbox, and retry the activation process.
The device failed to generate an ETP message.
Tip: Perform a hard reset of the device or install the latest BlackBerry Device Software version on the device using BlackBerry Application Loader. Then, retry the activation process.

The password set by the administrator in BlackBerry Manager or the BlackBerry Enterprise Server Management console was not applied correctly.
Tip: To verify that the password was applied correctly, close BlackBerry Manager or BlackBerry Enterprise Server Management console and reopen it. Verify the password is still listed under the user's properties. If the password is not present, verify that the SQL permissions are correct, make sure that there are no network connectivity issues to the SQL Server, and check the Microsoft Data Access Components (MDAC) version. See KB-03259 for instructions on determining the MDAC version.

The BlackBerry Enterprise Server has network issues, messaging application programming interface (MAPI) issues (in Microsoft Exchange environments only) or connectivity errors, or it has an incorrect version of MAPI32.dll. Check the application logs for related errors. Contact your service provider to determine the correct version of MAPI32.dll for your Microsoft Exchange version.
The device is not in an area with sufficient wireless coverage and is in the Activating… or Retrying… state. Test network connectivity by sending a personal information management (PIN) message.
The device is not properly provisioned.
Tip: A PIN message test can verify if the device is activated for standard wireless data; however, the device might not have been activated for enterprise traffic. Contact your wireless provider to verify that it has been activated for enterprise traffic.

The ServerConfigHistory table might have unfinished tasks for the user, preventing activation from continuing. (This occurs only if the user was previously added to the BlackBerry Enterprise Server.) Manually run the BlackBerry Configuration Database cleanup agents on the SQL Server to clear these tasks, then activate again.