The recurring appointment expansion in mailbox user1@ourDomain.tld has taken too long. The free/busy information for this calendar may be inaccurate. This may be the result of many very old recurring appointments. To correct this, please remove them or change their start date to a more recent date. Has anyone encountered this warning message? Is the solution simply to ask the user to do what is suggested above or is there anything to be done on the server end? Tried to Google on this and found link below, but it looks like it is by subscription: http://www.eventid.net/display.asp?eventid=8264&eventno=5362&source=EXCDO&phase=1

What version of Exchange? Are you on the latest service pack and roll up? For 2007 should be sp3 RU3. Event ID : 8264 Raw Event ID : 8264 Category : General Source : EXCDO Type : Warning Message : The recurring appointment expansion in mailbox <someone's address> has taken too long. The free/busy information for this calendar may be inaccurate. This may be the result of many very old recurring appointments. To correct this, please remove them or change their start date to a more recent date. An Exchange Server 2007 mailbox server randomly generates many transaction logs in an Exchange Server 2007 Service Pack 1 environment http://support.microsoft.com/kb/947014James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Post the entire event id and version of the exchange server.Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com

Only Exchange 2007 SP2 Outlook 2007 SP2 User also has a Blackberry. Complete error message: Log Name: Application Source: EXCDO Date: 6/1/2011 8:35:35 AM Event ID: 8264 Task Category: General Level: Warning Keywords: Classic User: N/A Computer: -------- Description: The recurring appointment expansion in mailbox user1@mydomain.com has taken too long. The free/busy information for this calendar may be inaccurate. This may be the result of many very old recurring appointments. To correct this, please remove them or change their start date to a more recent date. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="EXCDO" /> <EventID Qualifiers="32771">8264</EventID> <Level>3</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-06-01T12:35:35.000Z" /> <EventRecordID>235839</EventRecordID> <Channel>Application</Channel> <Computer>-------</Computer> <Security /> </System> <EventData> <Data>user1@mydomain.com</Data> </EventData> </Event>

Do you follow the workaround in KB 947014 to have a try? Here is some related information for you, hope can give you some help: Check for any excessive ExCDO warning events related to appointments in the application log on the server. (Examples are 8230 or 8264 events). http://support.microsoft.com/kb/947014 is just one example of this issue. If recurrence meeting events are found, then try to regenerate calendar data server side via a process called POOF. See http://blogs.msdn.com/stephen_griffin/archive/2007/02/21/poof-your-calender-really.aspx for more information on what this is. Thanks, Evan Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Evan, It looks like KB947014 pertains to E2K7 SP1. I am at SP2. So I thought that would not apply? Otherwise, I will take a look at your other link ASAP.

A lot of old recurring meeting request on a user mailbox and if it does not have an end date may record this event. So you can try to update these meeting requests with an end data, or delete them and create new ones. You can try it and please post your result.Jack Zhou

Yes, I looked at the link and it involves editing the registry on the server, which I am not inclined to do for an error message that appears every now and then for a single user. If the result is a discrepancy between Outlook and OWA, that may not even be an issue for the user in question, who only uses Outlook (well... provided that the Outlook dates are the good dates). I will just ask the user to adjust their calendar as suggested.