[Neil Grantham]

Hi,

Is there a default password used when you use 'Generate and Email Activation Password' in BES?

I have been following the BES 4.1 install guide, and logged in to our SBS 2003 server as BESAdmin and started the Manager.
I added the user, then went to Service Access, and then used 'Generate....'

Two emails arrived in the guys Outlook Inbox, but on his Blackberry, when I try to use Enterprise Activation, it sits there for a while and then says it can't find the server (or similar wording)
I am using his email address and his login password.

If I try to set a password in the Manager, and try 'Generate...' again it bombs out saying the old one is still in use, so I seem to be in some sort of loop.

Any help greatly appreciated.

I tried attaching the Blackberry to assign the device and got a 'User is not yet known' error, but I've seen this on the forum and will try some of the suggestions.

This has been quite a painful experience trying to implement BES for this company!!

Neil

[x14]

There's not default password. The "Generate and Email Activation Password" generates a random password.

You can set your own by using "Set Activation Password".

[Neil Grantham]

Originally Posted by x14

There's not default password. The "Generate and Email Activation Password" generates a random password.

You can set your own by using "Set Activation Password".

OK, so if it's randomly generated, how am I supposed to know it when I go to the Device to activate it?
I used the 'Create Password' option, but of course BES is now waiting for the previous attempt to register, but the device just keeps failing to find the server.

[goresci]

do these devices definately have upper case GPRS signal

if you go to your home screen and hold down ALT whilst typing LGLG
the handheld log will display, is there any infor here, in bold text or otherwise

[Neil Grantham]

I'll have a look when I go there later, but it doesn't help if I don't know what password I am supposed to put in.
The BES install guide just said to generate and send, then go to the device and put in the users email and the password, so I put in his email address and the password he told me he uses.
Now I am told it's a random password.
Confusing!

[hdawg]

I would recommend setting an activation password, rather than randomly generating one and then walking the user through the installation.

You could also create a password and email him / her the activation password. The generated passwords while secure are often too much for people that have _just_ gotten a BB.

[jibi]

Also, to clear the previous password, just go to set it and change the time to 0 and save.

Lastly, assuming you have email access to the user's account, you can just login and view the email it generated to them for the password.

[x14]

Originally Posted by Neil Grantham

OK, so if it's randomly generated, how am I supposed to know it when I go to the Device to activate it?
I used the 'Create Password' option, but of course BES is now waiting for the previous attempt to register, but the device just keeps failing to find the server.

The password is randomly generated and emailed to the user. You would have to get the password from the user's mailbox as Jibi suggest.

If you do not have access to the user's mail account I suggest you use the "Set Activation Password" method.

[Neil Grantham]

Originally Posted by x14

The password is randomly generated and emailed to the user. You would have to get the password from the user's mailbox as Jibi suggest.

If you do not have access to the user's mail account I suggest you use the "Set Activation Password" method.

I presume you mean his Exchange Inbox.
All that arrived are 3 emails from with some code in it::
This message is used to carry data between the BlackBerry handheld and an associated server. Please do not delete, move or respond to this message - it will be processed by the server
BEGINETP
<Code>
ENDETP
and an attached file called ETP.DAT

There's nothing with a password in it.

[hdawg]

that's not the password; but rather the etp messages

What is the exact error you're receiving?

this is a decent page ... Identifying and troubleshooting enterprise activation problems

[Neil Grantham]

Originally Posted by hdawg

that's not the password; but rather the etp messages

What is the exact error you're receiving?

this is a decent page ... Identifying and troubleshooting enterprise activation problems

Thanks, the error occurs as documented in this thread. I used BES Manager to 'Generate and Email...' but from what I can gather the password is random (the doc doesn't tell you that!) and I've been trying to find where I get the password - seems there should be an email - (is it to his Exchange account?) which we can't find.
On the BB I tried using the Activation screen and it couldn't find the server (probably because I used an incorrect password)
I then tried to generate a password and use 'Generate and Email...' again, to be told the first one is still active.

[x14]

If the user is not getting the message, your BES may have a mail routing issue.

You can clear the previous activation password by following Jibi's intruction in post #7 of this thread.

[Neil Grantham]

Thanks. The ETP messages got through though! (Assuming you mean the password mail has to go to his Exchange mailbox?)

Just a thought, the BES installation guide tells you how to send the password etc, but when I go to the BB, how does it know where the server is!
Is there some config I am missing on the BB that wasn't in the guide?
Logic tells me I should tell the BB somewhere what server it is looking for, maybe an IP address/name etc????

[jibi]

When you 'Generate and Email' the password, an email is actually generated AND emailed to the user in question. The password is contained in this email. It is sent from the BES service account. An easy shortcut to find these would be to look in the Sent Items of the BES service account, or as mentioned, in the Inbox of the user in question.

[hdawg]

Originally Posted by Neil Grantham

... but when I go to the BB, how does it know where the server is!

mail routing / rules ... SMTP! Yay for MX records.

[Neil Grantham]

OK, I have had another unsuccessful session with this BB user, and it's getting a bit desparate to resolve this.
We found the password emails (even if I set a password it still seems to generate a random pwd)

Problems are twofold

a) On the BB, when I try to activate it, it just seems to try then give up (something like server cannot be reached)

b) If I plug in the BB to the BES server via USB then try to assign it to the user, I get this error:
An error occured while assigning the device to the user.
The user is not yet known to the Blackberry agent.
It can take several minutes for a newly added user to be fully initialized by the server before they can be provisioned. (16)

Server is SBS 2003 with Exchange 2003 SP2
I read about problem 2) that said SBS needed a registry addition, but it didn't resolve the issue
Any thoughts?
TIA

PS - where are the BES logs?

[hdawg]

Can you check in the Messaging Agent (MAGT) logs for anything about this user? Copy and paste in what if anything you see. ... also anything you might see in the Alerter logs (ALRT)

Default location for logs:

C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs

[jeffc68]

I would delete the account on BES, delete all emails in the users mailbox that have to do with Blackberry. Recreate the account and set a activation password to something simple like j . Do not generate and email password.

I think you just need to start from scratch.

[rasobey]

Originally Posted by Neil Grantham

OK, I have had another unsuccessful session with this BB user, and it's getting a bit desparate to resolve this.
We found the password emails (even if I set a password it still seems to generate a random pwd)

Problems are twofold

a) On the BB, when I try to activate it, it just seems to try then give up (something like server cannot be reached)

b) If I plug in the BB to the BES server via USB then try to assign it to the user, I get this error:
An error occured while assigning the device to the user.
The user is not yet known to the Blackberry agent.
It can take several minutes for a newly added user to be fully initialized by the server before they can be provisioned. (16)

A) In your very first email to this thread you said you were activating using the user's login password. Get the activation password from the BES console user properties, or in the email that was sent. You may have resolved this issue already.

B) When I got this error it took a reboot of BES to sort it out. No amount of removing the user, waiting overnight and adding them back resolved the situation. I have discovered that, in the world of BES, only a reboot can fix some problems. Simply stopping and starting the BES service should suffice and will (should) delay message delivery by 5 minutes or so.

[Neil Grantham]

Originally Posted by hdawg

Can you check in the Messaging Agent (MAGT) logs for anything about this user? Copy and paste in what if anything you see. ... also anything you might see in the Alerter logs (ALRT)

Default location for logs:

C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs

In the logs directory I see lots of sub folders with (presumably) date codes such as 20070717
If I go in there, I find txt files with names such as 'BRAND-SERVER_ALRT_<lots of numbers>.txt
If I open the latest, I see entries such as:
[30000] (07/17 16:07:57.733):{0x920} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Controller (Application Event Log on BRAND-SERVER) | 07/17/2007 16:07:57 (AFFF4FB6) -> EventID:afff4fb6'BRAND-SERVER' agent 1: will not restart - reached the maximum of 10 restarts per 24 hours
[30000] (07/17 16:07:57.733):{0x25C} Alarm::ThreadProc: Received an alarm message

Last few lines of MAGT are:
[41120] (07/17 10:32:36.797):{0x1424} [CFG] Address Lookup is enabled
[41122] (07/17 10:32:36.797):{0x1424} [CFG] LDAP search is disabled, LDAP PIM search is disabled, LDAP ALP search is disabled
[41123] (07/17 10:32:36.797):{0x1424} [CFG] Using up to 10 external CDO Helpers in keep-alive mode
[41124] (07/17 10:32:36.797):{0x1424} [CFG] AddOwnerApptID is disabled
[41125] (07/17 10:32:36.797):{0x1424} [CFG] SetLocaleIDs is disabled
[40532] (07/17 10:32:36.797):{0x1424} [CFG] vCard conversion support has been enabled
[40892] (07/17 10:32:36.797):{0x1424} [CFG] GlobalRescan config: messaging:O, calendar:O, pim:O
[30221] (07/17 10:32:36.859):{0x1424} BES Cryptographic Kernel module is initialized and working properly
[40344] (07/17 10:32:36.859):{0x1424} Service is ready to accept SNMP Requests
[45009] (07/17 10:32:36.859):{0x1424} More cache hit rate: 0.0%, requests: 0, adds: 0, size: 0.0/10.0 Mb
[45014] (07/17 10:32:36.859):{0x1424} ExtMore cache hit rate: 0.0%, requests: 0, adds: 0, size: 0/20000
[30054] (07/17 10:32:36.859):{0x1424} Starting Message System
[30055] (07/17 10:32:36.859):{0x1424} Using MAPI profile BlackBerryServer
[40206] (07/17 10:32:36.859):{0x1424} MailboxManager::SubsystemInitialize - Using MAPI profile 'BlackBerryServer'
[20137] (07/17 10:32:36.891):{0x1424} MailboxManager::SubsystemInitialize - g_pSession->OpenMsgStore (0x8004011d)
[10277] (07/17 10:32:36.891):{0x1424} BlackBerry Messaging Agent BRAND-SERVER Agent 1 failed to start. Error code 5305
[50106] (07/17 10:32:36.891):{0x1424} Stopping BlackBerry Mailbox Agent 1 for Server BRAND-SERVER
[50000] (07/17 10:32:36.922):{0x127C} Controller: This BES Agent is under control of BlackBerry Agent Controller
[40507] (07/17 10:32:36.922):{0x127C} ExtUDPLogThread: Code on closing = 0
[30000] (07/17 10:32:36.922):{0x127C} [DIAG] EVENT=Unregister_thread, THREADID=0x127C, THREADNAME="ExtUDPLogThread"
[30065] (07/17 10:32:36.922):{0x1424} BlackBerry Mailbox Agent 1 for Server BRAND-SERVER shutdown complete