Hi ...
I've got some problems on our blackberry system.
We use BlackBerry Enterprise Server 4.1.4 (upgraded from version 4.1.1) on Windows Server 2003 with SQL 2005. The Server specs: are Pentium 4 CPU 2.8 GHz, RAM 1GB, HD 40 GB (15 GB Space Left).

Last time, when we were using version 4.1.1, the blackberry devices can receive and can send emails. But, sometime, we can't REPLY back to the sender. At that time, I delete the service book and did the Enterprise Activation. I got that problems a lot and redo Activation a lot also.

After upgraded to version 4.1.4, still got the same problems.
And one more, I make the Enterprise Activation this time, it takes too long.
I think, it takes at least 6 hours.

I don't want to do Enterprise Activation a lot and want to fix Activation too long error.

Could somebody please help me on those matters?

Regards,
KZHtun

well you could always activate by tethering the devices. This may be more labor intensive but would not take nearly as long.

Hi Sith_Apprentice,

Is there any way to solve my problems?

I checked one blackberry device, which can not reply email, in BlackBerry Manager and found that "IT Policy Status:" is "Error".
I tried to fix that error using "Resend IT Policy", "Assign IT Policy" and "Resend Service Book", but can not.

Please help me on this.

Regards,
KZ

I think the your post/question would be better fitted for BES admin corner, but i've seen EA's take upwards of 4-5 hours in a Domino enviroment, I'm not sure what your enviroment is, but in Domino, when you do an EA, I think that it has to scan your entire mail file before it completes the activation. If I am wrong there correct me, but that is just what i've seen in the various activations that I have done.

When you aren't able to send emails from the blackberry and you open one that has a red X, what is the error that it feeds you back? you'd have to scroll to the very top of the email to get it.

I agree, the Admin area is best for these questions

** Moved to the BES Admin area **

I have ran into some devices that the "reply" option is missing. The only way to correct this for me was to remove the user from the BES, re-add them and then reactivate the device.

I am not sure what is causing the extended activation times

EAs taking that long are (I believe) more linked to a misconfiguration somewhere in Domino. My USA users have mailfiles of up to 8GB, and my BES is in the UK. Doing an EA (with BES in London talking to server in USA over VPN) has still never taken more than 30 mins.

Jadey,

That is true, I have experienced something similar. A similar issue is that when doing an EA / EA to finally kick off, I have to clear the pending messages. As soon as you do that, the ea starts off and goes through quickly.

What generally takes the longest besides the inbox is the pnab for 3000+ contacts.

In Domino if you have a very large mail file and the BES is across the WAN then for prepopulation purposes it must scan the whole mailfile. You can try to set the prepopulation settings to 0 for that server and see if that resolves the issue, if your users can tolerate getting an empty device.

Also, keep in mind:

"We use BlackBerry Enterprise Server 4.1.4 (upgraded from version 4.1.1) on Windows Server 2003 with SQL 2005. The Server specs: are Pentium 4 CPU 2.8 GHz, RAM 1GB, HD 40 GB (15 GB Space Left)."

BES and SQL on the same box with only 1GB of RAM, either way upgrade the to 2 GB. BES documentation states a minimum 1.5 when the BES is a standalone machine. SQL is known to be a resource hog. How many users are you supporting? Is the Exchange/Domino/GroupWise on the same box as well? You didn't clarify what mail platform you are using.

When they can't reply what does the Using field of the message show? Desktop Secure? Unknown?

If it shows Unknown then the service book is corrupt and re-sending it should correct it but if it's a reoccurring issue then something else is going on.

For users that show an IT Policy status of Error you will more than likely have to reactivate because the BB is rejecting the Policy and will not accept a new one until you perform a security wipe.