[CO_BBTechie]

Hey guys. I'm trying to re-activate an 8100 on our BES. User complained of intermittent issues with email sync between Notes client with respect to marking read and filing. My initial thought was to bring the hand held current with the OS release. So a backup was taken, then the OS was upgraded.

After initial attempt to re-activate yesterday, the hand held hung during activation and the BES showed an odd error. At that point I canceled the activation from the hand held re-booted the BES until this morning when I can look at it more. It didn't seem to matter if I restored the user's backup file before the activation attempt. The result was still a failed activation when I didn't restore the data first.

Stats:
BES is at 4.0.3.5 (yes I realize we're behind but that's changing soon)
Hand held; ATT 8100 @ OS 4.2.1.109

Actions taken;
Wipe hand held save for two 3rd party apps; Beyond411 & Zagat to go.
Delete user from BES
Re-create user on BES
Change memo sync to false (seems to hang activation at this BES release)
Perform OTA activation from 8100



Results;
Hand held hangs at 93% during activation, with "Email filters" & "Email Settings" remaining on "initializing."

BES errors out with "e:\lotus\domino\nBES.exe... has terminated abnormally"

BES discontinues forwarding mail for everyone at this point, and a re-boot is necessary to restore message delivery.

I've got a tech support contract but I thought I'd see if I can get a quick road map here first.

Thanks

[CO_BBTechie]

Lots of Lookey-Loos but no contributors... guess I'll take it to RIM.

[jsconyers]

Have you noticed if any of the BlackBerry Services stop?

[CO_BBTechie]

After further testing... viewing the console window on the BES, it's actually the address book sync that is failing and crashing the server. Beyond that I haven't checked if any services in particular are failing because the whole server fails.

I was able to get the hand held activated by setting address book sync to false. However, when the activation completes, and I turn the address sync back up, it fails again.

Our Notes admin had a similar problem with his own 8100 and believes if we remove the roaming capability from this user's setup, we will have better luck.

[DiscGolfer]

Have you tried leaving the Sycn address book set to false and resend the service books? Do you have a test environment? if so test the device there.

[CO_BBTechie]

I have successfully activated the device with address sync off. However, our Notes admin removed her roaming functionality and had me point to a new .nsf file. This had the same result. We do not have a test environment, only a live one.

[Ugg]

"nbes.exe" is the BES task that runs under Domino - if that crashes and burns the BES won't be able to talk to Domino any more.

A few thoughts - does the Domino log have any information about why it has quit? Do you have the option of restarting the BES task via "load BES" without doing a full reboot? What does the Windows task manager say about memory used by the various processes on the box?

[hdeters]

Hi CO_BBTechie,
I had the same on my side and it was due to an update of our Notes Admin Server from Domino7 to Domino 8 this changed the pernames.ntf (Template for personal adress book) and this crashed the blackberry server with ran on 4.1.0
Domino 8 needs Bes 4.1.5
So I had two options:
1. Update Bes to 4.1.5
2. Replace the design of the names.nsf in roaming directory to a domino 7 pernames.ntf.

Since I had not time until now to update to bes 4.1.5 I chose option 2 and was sucessfull.
Regards Hermann