Hello, Hopefully someone has seen this and can help me out. I have exchange 2003 SP2 set up in a FE/BE configuration. One of my users reoccurring appointments is showing fine in his outlook 03 client, but will not display on OWA. The error I'm seeing on the the BE server is below. I alsosee this error for half of the others that are included in thisappointment. Event ID 8217 Source EXCDO The processing of the recurring appointment with the subject "appointment" in mailbox: <users mailbox> failed with error code 0x80004005. This appointment will not be visible in the web client or other non-MAPI client. For more information, click http://www.microsoft.com/contentredirect.asp. Most of what I see on this is for an older hotfix for Exchange 2000 SP3 http://support.microsoft.com/kb/327864I've tried making changes and updating the appointment, but it still doesn't show. I've exported the calendar and imported itinto a test account on a different back end server and it acts the same. I haven't seen this before, but he says he's noticed this in the past on other appointments. He can create new ones and they work just fine. I could have him just delete it and recreate it, but I'd like to at least know or understand why it's happening if it comes up again. If anyone has any suggestions I'd appreciate it. Thanks

please test if you can see it in the calendar if you create a reoccuring appointment by OWA. Meanwhile, please check if the user has the correct time zone setting. for your reference, here is a similar case. http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3315766&SiteID=17 Jason

Thanks Jason, I had him check his zone settings and they were already correct.

Any resolution to this issue? We're seeing the same thing, except only users using Outlook 2007 appear to be experiencing it. Additionally, these appointments are not showing correctly on mobile devices in addition to OWA.

I haven't gotten this resolved yet. I thought I did. I spent a fewdays on and offwith supportoverthe phone. Weended up updating the excdo.dll file on the exchange server (usedKB947500). The errors on the server were quiet for a couple days, but eventually came back on a few new appointments. I'm seeing this on a handful of users on outlook 07 who are more concerned about these not showing on their treos. So I'm back looking for a fix still.

thanks for the update, we're still seeing this issue as well, and other than having a few users backup and reimport their entire calendar, I haven't had any luck. If you come across anything, I'd be extremely appreciative if you updated this thread, thanks!

I am also running into this problem with users running Outlook 2007 against an Exchange 2003 server.

I have the exact same problem, client is Outlook 2007, server is Exchange 2003 sp2. In addition to OWA problem in the calendar, if you try to look at the invitation in OWA before accepting it, the meeting invitation is not displayable/openable in OWA, the preview has a 500 error . We have also found that the original meeting invitation or change notice causes two other things to occur: 1) If meeting invitationis read by an internal IMAP client (linux user), the meeting notice has an error and can not be downloaded. Some clients (like Evolution) will just hang and not download any messages past the corrupt message. The Application log will have the following message from the Content Engine: Event Type:ErrorEvent Source:IMAP4SVCEvent Category:Content Engine Event ID:1023Date:10/14/2008Time:12:57:24 PMUser:N/AComputer:xxxxxx_SRVDescription:Error 0x7da occurred while rendering message 0001-0000017a9cd2 for download for userxxxxxx@yyyy.com For more information, click http://www.microsoft.com/contentredirect.asp.Data:0000: 07 0c 0d 00 .... 2) If meeting notice is to an external user (client / customer), the email will get stuck in the outbound SMTP Queue and stay in a "RETRY" status. A sniffer trace of a forced connection to the receiving server shows a good connection, followed by our exchange server sending a "QUIT" command, never even trying to send the message in the queue. When the email is sent, the following error is generated: Event Type:ErrorEvent Source:EXCDOEvent Category:General Event ID:8217Date:10/21/2008Time:7:42:13 AMUser:N/AComputer:xxxxxxx_SRVDescription: The processing of the recurring appointment with the subject "Meeting time change" in mailbox: John Smith failed with error code 0x80004005. This appointment will not be visible in the web client or other non-MAPI client. All these different errors appear to be related to the appointment generated by the Outlook 2007 client.

For us, it seems to only occur when the appt is recurring longer than 7 weeks.We are looking into changing the free/busy published information to more than 2 months to see if this helps.To recap, W2K3, SP2 and Outlook 2007 clients.User on Outlook 2k7 creates a recurring meeting request without an end date or with an end date greater than 7 weeks, and sends it out to external & internal clients. This works fine.Same user tries to update the meeting request and resend it. Internally it works fine, but the update to the external client fails, IMMEDIATELY showing up as being in a retry state in ESM.Edited to Add:If we use Outlook 2003 to create the recurring meeting request and make the change to the recurring meeting request this does not occur. So the question is what is different in how Outlook 2007 processes meeting requests?

Meg, thats exactly what we're seeing. We have some of people on 2k7, and they are mainly the ones experiencing the issue. If changing the published info has any affect, please let us know! Thanks!

I found this KB article, and while it deals with Exchange 2003 to Exchange 2007 I wonder if it might not apply to Outlook 2007 and Exchange 2003.http://support.microsoft.com/kb/938650/en-usAny PSS folks care to comment on this one?

The magical 0x7da render errors. No one from Microsoft will help. Trust me, these family of problems are now 2+ years old, no solution, not Exch 2003, 2007, nothing.

After turning up MSExchangeTransport diagnostic logging, we saw the EXACT same error message report in KB938650. So we are placing a call to PSS and will keep everyone updated as to the outcome.

I'm under the assumption though that the fix under KB938650 isn't correcting the issue, right?

We contacted Microsoft Support via chat yesteday and received the patch. After installing the patch and making the registry key changes on both our servers (we have a cluster) we tested. The tests worked, we are no longer seeing the problem with changed calendar events. We have done multiple tests and every one succeed, the changed events went through the server without error, users are no longer seeing the HTTP 500 errors when viewing via OWA. So I would say that KB938650 does actually fix this problem.Chat with MS = http://support.microsoft.com/contactus/cu_sc_more_master?ws=support

Same issue here(user not seeing appointment on OWA or mobile phone\iPhone ). Got Event 8217 on Exchange Server (2003 SP2) and matching 3005 (http 500) on OWA. On Jason Li's lead, I reviewed the appointment using MFCMAPI and found a different Time Zone on the following property: 0x8201001E. NOTE: opening mfcmapi under the user's profile showed the time zone under a different property tag (6001E) so you may have to scroll through the props, until you find it.Anyhow, the user opened the appointment, changed the time zone, and lo and behold the item synched to the iphone and on OWA.Thanks Jason Li!