[Pinjo]

OK, it's my turn for some suggestions. Starting last Thursday, I had my first user who was unable to Enterprise Activate. Thinking it was a fluke and/or a cell plan issue, I had them verify with their wireless provider. A second one had the same issue later in teh day Friday. Both cases, they did not have data plans.

Thinking this was resolved by the change in plans, they now stall and hang on "Activating." Early this morning, we bounced the BES services, but still teh same issues. A third person tried activating today... again failure. I removed my own BB and account completely from the BES (deleted backups), but now mine is doing the same now.

Every single person receives the Enterprise Activation email in their Exchange Inbox if I have them removed from the BES, so no spam or Junk Mail settings involved there.

When on the BES, the email does finally disappear during Enterprise Activation, but they all hang and fail to activate.

I've checked out KB13458 from Blackberry and gone through the list. Activation would not be going to multiple accounts, my provisioning has not changed, and accounts have been completely deleted and re-added multiple times with simple passwords.

I cannot attach directly to the BES via USB due to our setup.

Any ideas? Any log files where it may show where the problem falls? THE MAGT log does not show any errors.

[Oderus]

I think the problem is between the BES and Exchange. When you perform an activation, an email is sent from the device to the inbox. The device can send the email as you confirmed it's being received so I guess it's the service account that lost permissions or you have a service that is stopped, like the router.

[ExchangeWizard]

I have seen this issue happen when you enter the wrong activation password, please make sure that you are entering the correct activation password or reset it on the server and retry it.


---------------------------------------------------
EmailActivation.com
The Best BES hosting service

[Spawneh]

This is not password related.

If the ETP message is sitting in the users inbox and doesn't go anywhere typically it is due to permissions between BES/Exchange

If it were password related you would receive an error and or activation progression

[ExchangeWizard]

Yes you will eventualy get an error telling you to contact your admin however I have seen this message take about 20 minutes to show up, how long have you left it on activating before canceling ?


---------------------------------------------------
EmailActivation.com
The Best BES hosting service

[penguin3107]

Originally Posted by ExchangeWizard

Yes you will eventualy get an error telling you to contact your admin however I have seen this message take about 20 minutes to show up, how long have you left it on activating before canceling ?


---------------------------------------------------
EmailActivation.com
The Best BES hosting service

It's clear that you don't understand the problem here.
The ETP.DAT activation message is reaching the user's mailbox, which means the EA password was accepted.

This isn't a password issue.

Pinjo, have a look through this:
BlackBerry Search Results

[Spawneh]

Originally Posted by penguin3107

It's clear that you don't understand the problem here.
The ETP.DAT activation message is reaching the user's mailbox, which means the EA password was accepted.

This isn't a password issue.

Penguin, The ETP message is generated at the Relay and is sent to the address specified in the activation. once the message arrives in the mailbox then the message password is compared via a hashing algorithm to confirm that the passwords are infact the same.

So the message will always get to the mailbox, and should be taken/destroyed/eaten by the BES in the process of confirming the password match.

[Malkier]

Originally Posted by Pinjo

When on the BES, the email does finally disappear during Enterprise Activation, but they all hang and fail to activate.

If the email is getting grabbed by the BES then two things come to mind that can cause this.

1) BlackBerry Policy Service has stopped, check your services to see what is running and as what.

2) Carrier has placed BIS codes on the SIM's, the BES will receive the activation email but will not do anything with it. I have seen carriers change existing SIM cards when new SIM's are purchased/changed to BES.

[penguin3107]

Wirelessly posted (Breaking Ball)

Originally Posted by Spawneh

Penguin, The ETP message is generated at the Relay and is sent to the address specified in the activation. once the message arrives in the mailbox then the message password is compared via a hashing algorithm to confirm that the passwords are infact the same.

So the message will always get to the mailbox, and should be taken/destroyed/eaten by the BES in the process of confirming the password match.

Thanks, I appreciate the clarification.

I still don't don't think it's a password issue, sine this is affecting all users. I doubt every one of them is entering an incorrect EA password.

[ExchangeWizard]

Originally Posted by penguin3107

Wirelessly posted (Breaking Ball)



Thanks, I appreciate the clarification.

I still don't don't think it's a password issue, sine this is affecting all users. I doubt every one of them is entering an incorrect EA password.

It's possible that the users are not using the password provided by their BES, insted they are prob trying to active-using their own passwords. I'm aware that there is several variables that can cause this, and maybe is not a password issue... however from experience I have seen this to be a password issue in the past. I wounder how long is the user waiting before stoping the activation... no matter what he should receive an error message

[Spawneh]

Originally Posted by ExchangeWizard

It's possible that the users are not using the password provided by their BES, insted they are prob trying to active-using their own passwords. I'm aware that there is several variables that can cause this, and maybe is not a password issue... however from experience I have seen this to be a password issue in the past. I wounder how long is the user waiting before stoping the activation... no matter what he should receive an error message

When this issue is password related the response would be much more swift (typically within 30-45secs) this case the ETP is sitting in the mailbox and doesnt look to be getting read by the server at all.

[ExchangeWizard]

Originally Posted by Pinjo

OK, it's my turn for some suggestions. Starting last Thursday, I had my first user who was unable to Enterprise Activate. Thinking it was a fluke and/or a cell plan issue, I had them verify with their wireless provider. A second one had the same issue later in teh day Friday. Both cases, they did not have data plans.

Thinking this was resolved by the change in plans, they now stall and hang on "Activating." Early this morning, we bounced the BES services, but still teh same issues. A third person tried activating today... again failure. I removed my own BB and account completely from the BES (deleted backups), but now mine is doing the same now.

Every single person receives the Enterprise Activation email in their Exchange Inbox if I have them removed from the BES, so no spam or Junk Mail settings involved there.

When on the BES, the email does finally disappear during Enterprise Activation, but they all hang and fail to activate.

I've checked out KB13458 from Blackberry and gone through the list. Activation would not be going to multiple accounts, my provisioning has not changed, and accounts have been completely deleted and re-added multiple times with simple passwords.

I cannot attach directly to the BES via USB due to our setup.

Any ideas? Any log files where it may show where the problem falls? THE MAGT log does not show any errors.

Did you figure out what the issue was ? I'm intrested to know if you did, Thanks.



--------------------------------------------
Home Emailactivation.com Exchange Hosting Services

[knottyrope]

I have seen the password come out with same characters in a row and Pearls change it to the next character with its multi-tap input

example pass: jjtm
user enters ktm as a result from its multi-tap input.

This needs a lil fixing on RIM's part.

[Jadey]

Originally Posted by knottyrope

I have seen the password come out with same characters in a row and Pearls change it to the next character with its multi-tap input

example pass: jjtm
user enters ktm as a result from its multi-tap input.

This needs a lil fixing on RIM's part.

This needs fixing on the users' part!
If a user has a multi-tap keyboard, and doesn't know how to use it - train them! What can RIM do about that, exactly?! On a half-size keyboard device, the user HAS to tap twice to get a K if indeed they need one - I fail to see what RIM can do about it (except stop making half-size devices)

[knottyrope]

Maybe generate passwords that dont have the same key being used twice in a row.
Seems simple enough.

Train them, LOL, they won't even RTFM before turning it on.

[penguin3107]

Originally Posted by knottyrope

Maybe generate passwords that dont have the same key being used twice in a row.
Seems simple enough.

This functionality is already built into BES.
You can have the BES generate "7100 Friendly" passwords to make it easier for Suretype users to type it.

[knottyrope]

Originally Posted by penguin3107

This functionality is already built into BES.
You can have the BES generate "7100 Friendly" passwords to make it easier for Suretype users to type it.

Yep done that, but it still pops up now and then.

[Jadey]

lol, set your own passwords then!