Still having CDOCalendar issues in log while CDO is bypassed and EWS is used (exchang
Please Login to Remove!
Hi,
Can anyone please help me with this mindbreaking issue:
This is the current setup:
Microsoft Active Directory mixed 2003/2008 (NSPI connection limit has been set to 2000), Domain Controller / Global Catalog server used by BES is a Windows 2008 server
Microsoft Exchange server 2007 SP2 (Version 8.2 (Build 176.2)), two mailbox servers (Server04 and Server05)
The BESMgmt database is running on a separate (mirrored) database server running SQL Server 2005 SP3
Two BlackBerry server clusters (4 servers in High Availability mode) running BES v5.0.2 Bundle 36
Total of 512 users sometimes running on one cluster during testing (for SP2 for example) running, sometimes evenly spread across both servers.
The BlackBerry servers are running:
Windows 2008 SP2
Exchange MAPI CDO package 6.5.8131.0
Exchange Web Services is being used for synchronization of the calendar. The CAS Exchange server is a separate server (Exchange 2007 SP2 also) running Exchange Web Services only for these BES Servers, the CAS server is not used for OWA, OMA, or any other client access role. Before when we had been running BES v5.00 and v5.01 we used MAPI/CDO and encountered the same issues.
The issue:
During the day on the active node of a cluster we will see messages popping up in the Alert log file stating:
[30000] (08/20 16:59:04.455):{0xB94} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 1 (Application Event Log on servername.prd.domain) | 08/20/2010 16:59:04 (AFFF4E43) -> {name.name@company.com} CDOCalendar:rocessReqRespFromMapi - Exception handled
These messages will appear for random users. The MAGT log would state something like:
[40406] (08/20 16:59:04.299):{0x1264} {name.name@company.com}CDOCalendar::GetRIMMeetingR eq - PrepareRIMEventObj (0x8004011b) failed
[20035] (08/20 16:59:04.315):{0x1264} {name.name@company.com}CDOCalendar:rocessReqRespFr omMapi - Exception handled
[40751] (08/20 16:59:04.362):{0x2198} {name.name@company.com}UserControl::GetInvitationI nfo - Cannot locate meeting associated with request. Sending text request
[30085] (08/20 16:59:04.362):{0x2198} {name.name@company.com}New mail has arrived, EntryId=14671
[40509] (08/20 16:59:04.362):{0x2198} {name.name@company.com}Message already has RefId=-1322826039
[40287] (08/20 16:59:04.362):{0x2198} {name.name@company.com} Queuing message, RefId=-1322826039, EntryId=14671, Posted=8/20/2010 8:56:21 AM, Delivered=8/20/2010 8:56:39 AM
This sometimes happens for one particular user, but it will also happen for multiple users at the same time. When this happens for one or more users, the BES high availability state of calendar synchronization will show Not Available in red. When this occurs for a lot of users at the same time, the BES cluster will eventually perform a failover to the standby node.
The CDO Exception messages can be slighty different. Here is a dumb of some CDO Exceptions for one particular day:
Line 200: [30000] (08/19 09:27:12.286):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 2 (Application Event Log on servername.prd.domain) | 08/19/2010 09:27:12 (AFFF4E43) -> {name.name@company.com} CDOCalendar::GetAssociatedApptObj - Exception handled
Line 203: [30000] (08/19 09:35:36.483):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 2 (Application Event Log on servername.prd.domain) | 08/19/2010 09:35:36 (AFFF4E43) -> {name.name@company.com} CDOCalendar::GetAssociatedApptObj - Exception handled
Line 206: [30000] (08/19 09:43:02.261):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 1 (Application Event Log on servername.prd.domain) | 08/19/2010 09:43:02 (AFFF4E43) -> {name.name@company.com} CDOCalendar::GetAChildInstance - Exception handled
Line 209: [30000] (08/19 09:43:02.461):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 1 (Application Event Log on servername.prd.domain) | 08/19/2010 09:43:02 (AFFF4E43) -> {name.name@company.com} CDOCalendar:rocessReqRespFromMapi - Exception handled
Line 228: [30000] (08/19 09:53:04.345):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 2 (Application Event Log on servername.prd.domain) | 08/19/2010 09:53:04 (AFFF4E43) -> {name.name@company.com} CDOCalendar::GetAssociatedApptObj - Exception handled
Line 244: [30000] (08/19 10:39:51.204):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 2 (Application Event Log on servername.prd.domain) | 08/19/2010 10:39:51 (AFFF4E43) -> {name.name@company.com} CDOCalendar::GetAssociatedApptObj - Exception handled
Line 247: [30000] (08/19 10:47:08.957):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 2 (Application Event Log on servername.prd.domain) | 08/19/2010 10:47:08 (AFFF4E43) -> {name.name@company.com} CDOCalendar::~CDOCalendar() - Exception handled
Line 247: [30000] (08/19 10:47:08.957):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 2 (Application Event Log on servername.prd.domain) | 08/19/2010 10:47:08 (AFFF4E43) -> {name.name@company.com} CDOCalendar::~CDOCalendar() - Exception handled
Line 250: [30000] (08/19 10:47:26.635):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 1 (Application Event Log on servername.prd.domain) | 08/19/2010 10:47:26 (AFFF4E43) -> {name.name@company.com} CDOCalendar:rocessReqRespFromMapi - Exception handled
Line 253: [30000] (08/19 10:51:32.562):{0x968} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BES01 Agent 1 (Application Event Log on servername.prd.domain) | 08/19/2010 10:51:32 (AFFF4E43) -> {name.name@company.com} CDOCalendar:rocessReqRespFromMapi - Exception handled
From a user perspective, the users complain about not receiving updates on existing calendar items and not receiving new calendar items on their Agenda. Invitations (mail messages) seem to work fine.
Questions:
Why would there be errors thrown starting with CDOCalendar when the CDO is bypassed and EWS is used?
What would you need as far as informations, logs, etc to be able to troubleshoot the issue?
Steps tried so far:
We split the load of users between the clusters, this did not help, both cluster then had the same issue.
On several occassions we have recreated the MAPI Profile for the BES, same results
We upgraded to SP2, same results
Using SP2 we used both setting on the BES to have the temp CDO profiles to be created with either MAPI or CDO, same results
We have now implemented EWS and the BES is now using EWS to sync calendars, same results
Thanks in advance
|
