[MCSEDanny]

I bought a Pearl the day they came out from T-Mobile and everything worked fine. I returned it within the 14 days and since then we had one user buy a pearl and everything connected fine. Now we have had 3 new users purchase pearls and they all have the same issue. They can compose a new email; lookup an address in the GAL but after typing the message there is no send option only save draft. I have T-Support with RIM and have probably spent over 20 hours of the phone with them this week with no solution. Is anyone else having this issue?

Sorry if you think this should be under BES Admin

[krad]

what version of bes are you running?

[MCSEDanny]

Originally Posted by krad

what version of bes are you running?

I believe its 4.1.3 I know it was SP3 that came out just before DST. Exchange 2003 SP2

[acnst]

Did you try resending the service books through BlackBerry Manager on the BES? What happens if you do a new enterprise activation?

[MCSEDanny]

Originally Posted by acnst

Did you try resending the service books through BlackBerry Manager on the BES? What happens if you do a new enterprise activation?

Yes we completely deleted the user, redid enterprise activation, resent service books. I even setup the Pearl under another user that does not have a BB and they had the same issue. So its a Pearl configuration on the BES or something on the Pearl.

[jhoetzl]

Do you have an enterprise policy? (Not IT Policy)
.Even if you think you've got all the PIN's listed and makes and models...try disabling it temporarily if you have it, and see how it goes.

[MCSEDanny]

I have 2 IT policies Default and IT. I moved the 3 none working users from Default to IT and now everything is working. What I need to do is go back and compare so I can find out what setting is not allowing under default for the Pearl because every other user I have is in the default policy.

[Pistol_Pete]

Remove the user from the BES.
Reload the OS.
Re-add the user to the BES.
Initiate Enterprise Activation.

[jhoetzl]

Originally Posted by jhoetzl

Do you have an enterprise policy? (Not IT Policy)

Hmmm, thought the not IT Policy was clear - guess not.

What I mean - there are the policies you mentioned, and then there is a thing called an "Enterprise policy".
In there, you can define which PIN's and makes/models can connect to your BES. I've had some troubles with THOSE policies and getting a server to connect to "localhost" (where localhost = srp = RIM/BB Land), not the typical "localhost" as in 127.0.0.1 (Bad, Bad error messages there!).


As for "Best Practices" - best to leave the default policy as is, and then create new ones, even if the new one is just a copy of "Default" called "Typical".

And I am all for setting all those entries in there to a value, even if it is the default value. It makes it much clearer to read later when you come back to it.

[whaut]

FWIW, I have the same issue with one particular user's Pearl on our BES server (exchange).

Two or three times a week I have to redo the enterprise activation - two other users with Pearls don't have any problems.

I am just now delving into this deeply, and have tried all the suggestions above to no avail...I will be watching this thread to see if anyone comes up with a solution.

W