Meeting invitations received from external domains show as regular email messages on the BlackBerry smartphone

Article ID: KB20866

Type: Support Content

Last Modified: 06-26-2013

 

Product(s) Affected:

  • BlackBerry Enterprise Server for Microsoft Exchange
CollapseEnvironment
  • BlackBerry Enterprise Server 5.0 SP1 to SP4 for Microsoft Exchange
  • Microsoft Exchange Server 2007 SP1 to SP3
  • Microsoft Exchange Server 2010 RU1 to SP1
  • Microsoft Exchange Web Services
CollapseOverview

When a BlackBerry smartphone user in a Microsoft Exchange Server 2007 or 2010 environment receives a meeting invitation from an external domain, the meeting invitation appears as a regular email message on the BlackBerry smartphone.The BlackBerry smartphone user is unable to send an Accept, Tentative, or Decline response to the meeting request.

In Microsoft Outlook, the user is able to reply with an Accept, Tentative, or Decline response to the meeting request; however, instead of Please respond, the meeting message changes to This meeting is not in the Calendar; it may have been moved or deleted.

See the following BlackBerry Messaging Agent and BlackBerry CalhelperWS log examples:

MAGT_01


[40423] (03/12 09:08:34.113):{0x1690} {user01@rim.com} Queuing new mail through notification (external). EntryId=2036
[40724] (03/12 09:08:34.113):{0xDB8} {user01@rim.com} Get record key for this MAPI object, EntryId=2036
[40435] (03/12 09:08:34.129):{0xDB8} {user01@rim.com} Queuing new mail through notification. EntryId=2036. Msgs Pending 0
[40751] (03/12 09:08:48.645):{0xDB8} {user01@rim.com} UserControl::GetInvitationInfo - Cannot locate meeting associated with request. Sending text request
[30085] (03/12 09:08:48.645):{0xDB8} {user01@rim.com} New mail has arrived, EntryId=2036
[40287] (03/12 09:08:48.645):{0xDB8} {user01@rim.com} Queuing message, RefId=-86372058, EntryId=2036, Posted=03/12 09:08:12, Delivered=03/12 09:08:33
[30066] (03/12 09:08:48.645):{0xDB8} Total Msgs Pending 1
[40000] (03/12 09:08:48.661):{0x1684} RpcGetSubject is called. [CH=28367696, MH=28342752]
[40000] (03/12 09:08:48.661):{0x1684} RpcGetFirstAttachment is called. [CH=28367696, MH=28342752]
[30081] (03/12 09:08:48.661):{0x16F0} {user01@rim.com} Sending message to device, size=487, EntryId=2036, RefId=-86372058, TransactionId=-879147197, Tag=20769
[40279] (03/12 09:08:48.661):{0x16F0} {user01@rim.com} SubmitToRelaySendQ, Tag=20769
[40000] (03/12 09:08:48.661):{0x1464} [BIPP] Send data, Tag=20769
[40000] (03/12 09:08:55.849):{0x145C} [BIPP] Received status DELIVERED, Tag=20769
[30097] (03/12 09:08:55.849):{0xDB8} {user01@rim.com} Message has been delivered to device, Tag=20769, EntryId=2036

CALH_01

[30580] (03/15 12:11:43.206):{0x1730} {user01@rim.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #1
[30580] (03/15 12:11:43.206):{0x1730} {user01@rim.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #2
[30580] (03/15 12:11:43.206):{0x1730} {user01@rim.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #3
[30580] (03/15 12:11:43.206):{0x1730} {user01@rim.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #4
[30580] (03/15 12:11:43.206):{0x1730} {user01@rim.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #5
[30602] (03/15 12:11:43.206):{0x1730} {user01@rim.com} WSRequestParams::MeetingRequestWsToCiCAL - Cannot find associated meeting in calendar

CollapseCause
The flags for ProcessExternalMeetingMessages, AutomateProcessing and RemoveOldMeetingMessages are not set properly to allow the BlackBerry Enterprise Server to deliver the meeting invite to the BlackBerry smartphone as an actual meeting invite.
CollapseResolution

Please follow the steps below to configure the desired flags based on the version of Microsoft Exchange.

Retrieve the Microsoft Exchange Server calendar settings for the associated BlackBerry smartphone user account:

Microsoft Exchange Server 2007 SP1

Get-MailboxCalendarSettings -identity [Accountname] | Format-List

Microsoft Exchange Server 2010

Get-CalendarProcessing -identity [Accountname] | Format-List

The following is a sample output from the command against an Microsoft Exchange Server 2010. The resulting output is the same for a mailbox on Microsoft Exchange Server 2007:

[PS] C:\Windows\system32>Get-CalendarProcessing -identity user01 | Format-List

AutomateProcessing : None
AllowConflicts : False
BookingWindowInDays : 180
MaximumDurationInMinutes : 1440
AllowRecurringMeetings : True
EnforceSchedulingHorizon : True
ScheduleOnlyDuringWorkHours : False
ConflictPercentageAllowed : 0
MaximumConflictInstances : 0
ForwardRequestsToDelegates : True
DeleteAttachments : True
DeleteComments : True
RemovePrivateProperty : True
DeleteSubject : True
DisableReminders : True
AddOrganizerToSubject : True
DeleteNonCalendarItems : True
TentativePendingApproval : True
EnableResponseDetails : True
OrganizerInfo : True
ResourceDelegates : {}
RequestOutOfPolicy :
AllRequestOutOfPolicy : False
BookInPolicy :
AllBookInPolicy : True
RequestInPolicy :
AllRequestInPolicy : False
AddAdditionalResponse : False
AdditionalResponse :
RemoveOldMeetingMessages : True
AddNewRequestsTentatively : True
ProcessExternalMeetingMessages : False
DefaultReminderTime : 15
RemoveForwardedMeetingNotifications : False
Identity : rim.com/TestAccounts/user/user01




If using Microsoft Exchange Server 2007 SP1

By default, ProcessExternalMeetingMessages is set to False on Microsoft Exchange Server 2007. The correct setting for BlackBerry Enterprise Server is TrueIn order to use Microsoft Exchange Web Services, verify that this setting is enabled:

  • To apply to all user mailboxes on a specific Exchange Mailbox Server:
    Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Set-MailboxCalendarSettings -ProcessExternalMeetingMessages $true
     
  • To apply to a specific User:
    Set-MailboxCalendarSettings -ProcessExternalMeetingMessages $true "UserName"

1)  Confirm the setting applied to AutomateProcessing

By default, AutomateProcessing is set to AutoUpdate on Microsoft Exchange Server 2007. This is the correct setting. In order to use Microsoft Exchange Web Services to perform operations such as calendaring, verify that the setting is correct:

  • To apply to all user mailboxes on a specific Exchange Mailbox Server
    Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Set-MailboxCalendarSettings -AutomateProcessing AutoUpdate
     
  • To apply to a specific User:
    Set-MailboxCalendarSettings -AutomateProcessing AutoUpdate "UserName"

Note: Setting the - AutomateProcessing property to AutoUpdate only applies to User Mailboxes. Do not adjust this setting on Resource Mailboxes like Meeting Rooms.

 
2)  Confirm AddNewRequestsTentatively is set to True

By default, AddNewRequestsTentatively is set to True. This also corresponds to Automatically place new meeting requests on my calendar, marked Tentative in Outlook being checked. However this is a user changeable parameter.

Ensure AddNewRequestsTentatively is set to True or Automatically place new meeting requests on my calendar, marked Tentative in Outlook should have a check on it.

  • To apply to all user mailboxes on a specific Exchange Mailbox Server:
    Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Set-MailboxCalendarSettings -AddNewRequestsTentatively $True
     
  • To apply to a specific User:
    Set-MailboxCalendarSettings -AddNewRequestsTentatively $True "UserName"

Note: These two settings can be combined:
Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited | Set-MailboxCalendarSettings -ProcessExternalMeetingMessages $true -AutomateProcessing AutoUpdate -AddNewRequestsTentatively $true

3)  Confirm RemoveOldMeetingMessages is set to True

By default, RemoveOldMeetingMessages is set to True on Microsoft Exchange Server 2007. The correct setting for BlackBerry Enterprise Server should be TrueIn order to use Microsoft Exchange Web Services, verify that this setting is enabled:

  • To retrieve the Microsoft Exchange Server calendar settings for the associated BlackBerry smartphone user account:
    Get-MailboxCalendarSettings -identity [Accountname] | Format-List
     
  • To apply to all user mailboxes on a specific Exchange Mailbox Server:
    Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Set-MailboxCalendarSettings -RemoveOldMeetingMessages $true
     
  • To apply to a specific User:
    Set-MailboxCalendarSettings -ProcessExternalMeetingMessages $true "UserName"




If using Microsoft Exchange Server 2010


1)  Confirm the setting for ProcessExternalMeetingMessages

By default, ProcessExternalMeetingMessages is set to False on Microsoft Exchange Server 2010. The correct setting for BlackBerry Enterprise Server is True.

In order to use Microsoft Exchange Web Services, verify that this setting is enabled:

  • To apply to all User Mailboxes on a specific Exchange Mailbox Server:
    Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Set-CalendarProcessing -ProcessExternalMeetingMessages $true
     
  • To apply to a specific User:
    Set-CalendarProcessing -ProcessExternalMeetingMessages $true "UserName"

 
2)  Confirm the setting for AutomateProcessing

By default, AutomateProcessing is set to AutoUpdate on Microsoft Exchange Server 2010. This is the correct setting.

In order to use Microsoft Exchange Web Services to perform operations such as calendaring, verify that the setting is correct.

  • To apply to all User Mailboxes on a specific Exchange Mailbox Server:
    Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Set-CalendarProcessing -AutomateProcessing AutoUpdate
     
  • To apply to a specific User:
    Set-CalendarProcessing -AutomateProcessing AutoUpdate "UserName"

Note: Setting the -AutomateProcessing property to AutoUpdate only applies to User Mailboxes. Do not adjust this setting on Resource Mailboxes like Meeting Rooms.

 
3)  Confirm the AddNewRequestsTentatively setting

By default, AddNewRequestsTentatively is set to True. This also corresponds to Automatically place new meeting requests on my calendar, marked Tentative in Outlook being checked. However this is a user changeable parameter.

Ensure AddNewRequestsTentatively is set to True or Automatically place new meeting requests on my calendar, marked Tentative in Outlook should have a check on it.

  • To apply to all User Mailboxes on a specific Exchange Mailbox Server:
    Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Set-CalendarProcessing -AddNewRequestsTentatively $true
     
  • To apply to a specific User:
    Set-CalendarProcessing -AddNewRequestsTentatively $true "UserName"

Note: These three settings can be combined:
Get-Mailbox -Server "<messaging_server_name>" -ResultSize Unlimited | Set-CalendarProcessing -ProcessExternalMeetingMessages $true -AutomateProcessing AutoUpdate -AddNewRequestsTentatively $true

CollapseAdditional Information

The ProcessExternalMeetingMessages parameter specifies whether to process meeting requests that originate outside the Microsoft Exchange organization. If set to $false, meeting requests that originate outside of the organization are rejected. Valid input for this parameter is $true or $false.

Use the AutomateProcessing parameter to enable or disable calendar processing on the mailbox. If this parameter is set to None, both resource booking and the Calendar Attendant will be disabled on the mailbox. If set to AutoUpdate, the Calendar Attendant will process meeting requests and responses. If this parameter is set to AutoAccept, resource booking will be enabled on the mailbox.

Set the AddNewRequestsTentatively parameter to $true to have the Calendar Attendant insert new calendar items tentatively on the calendar. If the AddNewRequestsTentatively parameter is set to $false, only existing calendar items are updated by the Calendar Attendant.

 

Additional information on the Set-CalendarProcessing command can be found on Microsoft's TechNet.

Additional information on the Set-MailboxCalendarSettings command can be found on Microsoft's TechNet.

Disclaimer

By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.


Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.