unable to create calendar appoint. on BB
 

Howdy,
I have 1 end user (out of 200) who is unable to create calendar appointments w/ invites on their BB. They receive a "system error in sending" message.

I created a test appointment and invited the EU. It was successful on my end, and also appeared in the EU's outlook calendar, but did not hit her BB. However, when she accepted the invite in her outlook, then it appeared on her BB.

Email is not affected, nor are phone calls.

I'm having her do a hard reboot, but figure I'd try and research it out before trying things like resending the service book, or deleting/undeleting the Desktop [CICAL] entry in service books.

Our BES is 4.1.3.18, and we're on Exchange 2003. The device is a T-Mobile 8320 on 4.2.2.180 OS.

Thanks!

- jim

There are a few things that can affect the Calendar. The first thing I thought of is the possibility she has her DM set up to control the synchronization of the calendar. It is possible to have the PC only send the updates. Check the options using the DM control panel. Beyond that it may be a BES setting but doubtful. It just seems like a wireless sync setting.

Good Luck

A belated "thanks" for your reply/info.

I don't believe that it's due to a DM setting/issue. Since my orig. post I've had 3 diff. EU report calendar synching issues - and none of the 3 have done anything w/in DM. In fact, the orig. issue (my first post), the EU didn't even have her laptop with her when the issue occurred. 2 have T-Mobile devices, 1 has a Verizon device (and all 3 have diff. OS (4.2, 4.5 & 4.6)).

All 3 issues differ slightly - still trying to get more detailed info on the other 2.

We recently upgraded our BES from 4.1.3 to 4.1.7, so I'm wondering if that might be where this is coming from.

Has anyone gone through this upgrade and experienced similar issue(s)?

Thanks,

Jim

In case anyone is interested....

Turns out it's been a bit more involved than just an isolated device/sync issue. We ended up w/ about 10 people reporting the same issue, and a check of a log buried on the BES server indicated that many more were affected, they just didn't know it.

A bunch of troubleshooting was done, but it appears the root of the issue was that when the BES was upgraded, it was done so w/ the domadmin account instead of the BBAdmin account, so all the BB services were running under domadmin account. That apparently caused some orphaned registry entries to collect here:

HKEY_Current_User\Software\Microsoft|Windows NT\Current Version\Windows Messaging Subsystem

So we needed to first delete that profile and recreate the MAPI profile per this article: KB10285 (View Document)

We also had to switch the service account per this article: KB04293 (View Document) and then export some registry entries.

Fun.

Thanks for the followup! This could be very valuable to others trying to diagnose similar or related errors. (y)

Thanks. I should clarify one part of that, as I was getting interrupted about a bazillion times whilst trying to type it out...

The BES services running under the domadmin account did not necessarily cause the orphaned registry entries. BB/RIM support wasn't able (at least the techs I spoke to) say for sure if the one led to the other.

It may have been 2 separate issues that we stumbled onto.