EXCDO Event ID 8263

[Jim Scavuzzo]

I originally posted this to the exchange2000.development newsgroup, but
received no response. I am hoping that someone that regularly reads the
posts in the related newsgroups might have some idea...


We are developing an application integrated with Exchange 2000 using CDO and
the Event Sink technology. The problem being experienced relates to the
identification of all appointments for a recurring appointment. This is
being done by performing a SELECT SQL statement over a date range
(accomodating for the funky backwards usage syntax necessary to find
appointments), which works fine in the development and testing environment
locally.

In the production environment (medium to large volume of user accounts, and
resource mailboxes with high volume of appointments, both recurring and
single), the customer is getting this event warning:

Event Type: Warning
Event Source: EXCDO
Event Category: General
Event ID: 8263
Date: 10/27/2003
Time: 3:22:54 PM
User: N/A
Computer: Our-EXCHANGE
Description:
The recurring appointment expansion in mailbox Gary
has taken too long. Some recurring appointment instances
may not be visible at this time. To ensure that the
calendar view is correct, please refresh the calendar
view in Microsoft Outlook Web Access.


I do not currently know if the expansion of a recurring appointment is is
failing, but the customer is concerned. Is this a valid concern? Can
anything be done to alleviate/resolve these warnings?

The customer is using Exchange 2000 Server with the latest service packs.

 

[Steve Antonio [MSFT]]

These entries are completely harmless. They indicate that a user has too
many appts in the calendar view to be expanded in a single OWA calendar
query. If the user sees missing items in the calendar view, he/she can
simply press the refresh button on the browser -- then, the expansion starts
where it left off and produces more instances for the view.

The warning messages above informational only.


--
Cheers,

Steve Antonio
Microsoft Exchange Support

This posting is provided "AS IS" with no warranties, and confers no rights.

Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.

 

[Jim Scavuzzo]

Would there be any concern if a custom developed event sink was installed
and causing this Warning message?