[1fish]

One of our users is experiencing an intermittent problem when attempting to sync her blackberry (pearl). She, specifically, has problems when it tries to sync her calendar. Which historically has been (temporarily) solved by opening desktop manager, selecting backup and restore, clearing the calendar entries on her BB and then resync'ing it. There are 8 other users on the BES but she is the only one who has repeatedly had this problem. Anyone have any ideas?


BES 3.6.6.5
Exchange 2003
CDO version 6.5.7651.61 (on both Exchange and BES server)

[hdawg]

Upgrade to SP7. Exchange 2003 SP2 is not supported with BES 3.6 SP6 or below

[1fish]

Done. We will see if that fixes it.

[bertiebassett]

and erm 'get your upgrade boots on...' the version after the version you're running will have RIM support stopped from 31/1/08. I suggest you get onto your carrier REP or T-support cont'r'act (if you have one) and blag an upgrade to 4.1...

Do you want to be the guy that explains to 'management' in February "I'm sorry sir your shiny BB has stopped working, I don't know why and RIM won't help me fix it..."

[1fish]

Interestingly / fortunately enough, the upgrade is already in the planning stages!
(See one of my prior posts - http://www.blackberryforums.com/bes-...ade-3-6-a.html)

[1fish]

Originally Posted by 1fish

Done. We will see if that fixes it.

I just heard that the same user's sync blew up again - on the calendar.

We are (now) on BES 3.6.7.12 and CDO version 6.5.7651.61 (on both Exchange and BES server)

Any thoughts /suggestions are very welcome!

[hdawg]

Are you seeing anything in the ALRT log for this user?

[1fish]

Originally Posted by hdawg

Are you seeing anything in the ALRT log for this user?

Nothing in the ALRT logs - then again, I don't have any ALRT log files.

[hdawg]

By default all BES logs are in:

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

check other local disks too if you have them.

[1fish]

Perhaps I should have been more verbose in my last post.

Yes, I have logs. Not that I think it matters greatly, but they are in the .....\Logs directory and not ....\Logs\YYYYMMDD\.

None of my logs have 'ALRT' either in their name or in the content. The three different types of logs in that directory are:

• YYYYMMDD_BlackBerry Enterprise Server_SERVERNAME.txt
• YYYYMMDD_MDS_SERVERNAME.txt
• YYYYMMDD_BlackBerry Server_Controller.txt

[hdawg]

Oh crap, I'm sorry ... I totally forgot you were on 3.6. I've forgotten much about 3.6 logging due to a lack of usage; I'm sorry.

Is this the only Pearl on the server? Is this the only 4.2 HH OS device on the server?

I unfortunately can't think of anything off hand; I'm sorry.

[1fish]

Good news - I finally upgraded last night to 4.1
Better news - Everything went smoothly!
Bad news - One of my users is still having this problem.


This time I have an ALRT log nut there isn't anything in there about this user. In fact the only thing in there that strikes me as remotely interesting is:

[30000] (11/30 00:00:11.245):{0x1058} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Controller (Application Event Log on SERVERNAME) | 11/30/2007 00:00:11 (AFFF4E20) -> EventID:afff4e20[CFG] Controller won't generate userdump files. Userdump.exe not found.

But I really don't think that is related to this.

Thoughts?

BES 4.1.4.15
Exchange 2003
CDO version 6.5.7651.61 (on both Exchange and BES server)