OL2002: You Receive the "Cancelable RPC" Dialog Box When You Use the Meeting Planner Options (324374)

MORE INFORMATION

When you select the Show Popup Calendar Details option or the Show Calendar Details in Grid option, the new processing functionality is engaged. The new processing receives the same free/busy data from the Public folder server as it does in Outlook 2000, and then it forces a repaint of the dialog box. This new process provides the user with the visual impression that Outlook is responding. Outlook then tries to open the Calendar folder for each attendee in the meeting. If Outlook does not have access to a particular recipient's calendar, it moves along to the next one. Outlook continues doing this until it has exhausted the list of attendees. If Outlook does have access to an attendee's calendar, it opens the calendar, reads the subject lines of all the attendee's meetings for a particular time range, and then paints it on the Attendee Availability tab for the meeting request. That time range is based on how much free/busy data is published for that recipient.

Next, Outlook tries to open the Calendar folder for each attendee of the meeting. If Outlook does not have access to a particular attendee's calendar, it continues with the next meeting attendee. This is repeated until Outlook has viewed each meeting attendee's calendar. If Outlook does have access to an attendee's calendar, the Popup Calendar box opens, the information is read in the Subject boxes of all the attendee's meetings for a particular time range, and then paints it on the Attendee Availability tab for the meeting request. That time range is based on how much free and busy data was published for that attendee.

The following behavior may occur when Outlook tries to receive the free/busy information and then either does or does not receive that information:

1. User A is the meeting originator and has both the Show Popup Calendar Details and the Show Calendar Details in Grid options turned on. User A creates a meeting request and invites User B, User C, and User D. User B publishes 2 months of free and busy data, User C publishes 12 months of free and busy data, User D publishes 4 months of free and busy data, but User A does not have access to read User D's calendar.
2. When User A clicks the Attendee Availability tab, Outlook contacts the server where the free and busy Public folder is located and retrieves the free and busy data for each meeting attendee.
   
   In this case, User A can view the 2 months of data for User B, the 12 months of data for User C, and the 4 months of data for User D.
   
   After the free and busy data for each meeting attendee is retrieved and the dialog is repainted, Outlook opens User B's calendar and requests the additional calendar details for every meeting and appointment that occurs during the 2-month range that the free and busy data was published in. After that information is retrieved, Outlook continues this process with the next attendee, User C. Outlook opens the calendar for User C and requests the additional calendar details for every meeting and appointment that occurs during the 12-month range that the free and busy data was published in. After that operation is completed, Outlook continues this process with the next attendee. Outlook tries to open the calendar for User D, finds that it does not have the correct security access, and then returns without any additional data.

If you request a large amount of data from multiple users, you can expect to receive the Cancelable RPC dialog box if more than 5 seconds elapse during the data retrieval.

You may also receive Event ID 1016 events on your Microsoft Exchange Server computer during this process. For additional information about the Event ID 1016 that you receive on your Exchange server, click the following article number to view the article in the Microsoft Knowledge Base: .
NOTE: Because of the current design of Outlook 2002, Outlook 2002 may stop responding when the data is being collected. Outlook 2002 functions as expected after the data is returned.