Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

Reply
New Contributor
Posts: 3
Registered: ‎04-10-2008
My Device: Not Specified

Calendar synchronization from device disabled. Appointment filtered

Hello all
Setup
Stand-alone Blackberry Enterprise Server
2003 server
Exchange 2003 SP2
BES ver. 4.1.4.26
Exchange Server 2003 SP2
CDO 6.5.7651.61 same on both servers.

I am receiving this in my MAGT Log when entering appointment on BB

[40700] (04/09 10:06:16.187):{0x1410} {username@Company.com} Receiving packet from device, size=110, TransactionId=-910330668, Tag=4063, content type=CICAL, cmd=0x3
[40000] (04/09 10:06:16.187):{0x1410}{username@company.com}-HandleAppointmentToSynchronize-Entering-Tag=4063
[40293] (04/09 10:06:16.187):{0x1410} { username@company.com} Calendar synchronization from device disabled. Appointment filtered, Tag=4063
[40000] (04/09 10:06:16.187):{0x1410} user@company.com }-HandleAppointmentToSynchronize-Exit-rc=Error
[40279] (04/09 10:06:16.187):{0x1410} { username@comapany.com } SubmitToRelaySendQ, Tag=4063
[40000] (04/09 10:06:16.187):{0x1090} [BIPP] Send status DATA_ACCEPTED, Tag=4063


Wireless Synchronization is turned on in the BB

Any help would be great.

Thanks
Retired
Posts: 79
Registered: ‎04-01-2008
My Device: Not Specified

Re: Calendar synchronization from device disabled. Appointment filtered

[ Edited ]

GeoMon wrote:
Hello all
Setup
Stand-alone Blackberry Enterprise Server
2003 server
Exchange 2003 SP2
BES ver. 4.1.4.26
Exchange Server 2003 SP2
CDO 6.5.7651.61 same on both servers.

I am receiving this in my MAGT Log when entering appointment on BB

[40700] (04/09 10:06:16.187):{0x1410} {username@Company.com} Receiving packet from device, size=110, TransactionId=-910330668, Tag=4063, content type=CICAL, cmd=0x3
[40000] (04/09 10:06:16.187):{0x1410}{username@company.com}-HandleAppointmentToSynchronize-Entering-Tag=4063
[40293] (04/09 10:06:16.187):{0x1410} { username@company.com} Calendar synchronization from device disabled. Appointment filtered, Tag=4063
[40000] (04/09 10:06:16.187):{0x1410} user@company.com }-HandleAppointmentToSynchronize-Exit-rc=Error
[40279] (04/09 10:06:16.187):{0x1410} { username@comapany.com } SubmitToRelaySendQ, Tag=4063
[40000] (04/09 10:06:16.187):{0x1090} [BIPP] Send status DATA_ACCEPTED, Tag=4063


Wireless Synchronization is turned on in the BB

Any help would be great.

Thanks

 

Hi GeoMon!

 

The BlackBerry Enterprise Server thinks that wireless synchronization is not enabled for the Calendar. Although you said that it is enabled, can you possibly check that once again (and/or clarify where you've checked previously)?

Message Edited by TheOracle on 04-11-2008 02:24 PM
New Contributor
Posts: 3
Registered: ‎04-10-2008
My Device: Not Specified

Re: Calendar synchronization from device disabled. Appointment filtered

HelloI almost gave up hope that no one would be able to help me.  Under the users Properties/Pim Sync/ Wireless Sync Enabled = True IT PolicyPim Sync Policy GroupDisable all Wireless Sync = FalseDisable Calendar Wireless Sync = False Anywhere else in BES settings that I maybe missing?
Retired
Posts: 79
Registered: ‎04-01-2008
My Device: Not Specified

Re: Calendar synchronization from device disabled. Appointment filtered

Is wireless synchronization for the Calendar enabled on the BlackBerry itself?
New Contributor
Posts: 3
Registered: ‎04-10-2008
My Device: Not Specified

Re: Calendar synchronization from device disabled. Appointment filtered

 Yes it is.
New Member
Posts: 1
Registered: ‎07-22-2008
My Device: Not Specified

Re: Calendar synchronization from device disabled. Appointment filtered

Try installing BES 4.1 Service Pack 5

 

http://na.blackberry.com/eng/deliverables/1433/Release_Notes.pdf

 

See specifically

SDR 126850

In BlackBerry Enterprise Server Version 4.1 SP2 and later, if a BlackBerry device received an IT policy that changed the Disable

Wireless Calendar rule setting to False, the wireless calendar on the BlackBerry device remained disabled.

In BlackBerry Enterprise Server Version 4.1 SP5, this issue is resolved.