Monthly archives: June 2010

Timothy

Mystery of the Failing Meeting Appointment Updates on Exchange 2003

A very brief tech mystery today!

We have not upgraded to Exchange 2010 yet at work and are still on Exchange 2003 (yes, 2003).  That upgrade is scheduled for a little later this year, but until then, I have to continue to support 2003.

I ran into a strange mail flow issue today that ends up being the result of a combination of Exchange 2003 and Outlook 2007 or newer.  One of my users was trying to send an update to a meeting request, but recipients outside of our domain (external SMTP recipients) were getting stuck in the queue.  The additional information in the queue just said "Unable to open the message for delivery."  That clued me in that it wasn't an external SMTP rejection of the message (invalid email address or whatever).  So I did some googling.

It turns out there's actually a known issue for Outlook 2007 or Outlook 2010 (or newer) clients sending meeting updates via Exchange 2003.  It must not happen all the time, because we've had Outlook 2007 deployed for years and never saw this issue before.  In fact, it didn't start happening until a user on Outlook 2010 sent a meeting update.  Maybe it's just coincidence – I'm not really sure.

Anyway, here's the KB with all the details.  The article isn't clear, but to double check if you have this error by enabling diagnostic logging, you need to set MSExchangeTransport\Exchange Store Driver to Maximum.  Once you do that, go back to the queue, select the outbound server the stuck message is sitting in, right click and select "Force Connection."  Then you can look in the event viewer for the specific error to confirm this is your issue.

Don't forget to set the registry entry after applying the hotfix!

Blog

Search Posts

Recent Comments

  1. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Brian: Thank you so much Edward! :-)

  2. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Tom: Thank you Edward! After beating my head against a wall for days, tried your suggestion out and lo and...

  3. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Mike: DPM 2016 setup will fail if you have SQL Server Management Studio (SSMS) V17.x installed. Re-Install...

  4. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Rob: Edward, thanks man! you were a lifesaver. My scenario was Win Server 2016 from scratch, SQL 2016 (N...

  5. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Edward: It also crashes with the 4387 error if you have the SQL Management Studio 17 tools installed. Installing...

  6. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Ram: Hi - I followed richsmif instruction and was able to successfully install DPM 2016 on SQL 2016. Completed...

  7. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Neighborgeek: Thanks for the post, this is exactly the issue I am running into. I'm disappointed to see that you didn...

  8. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    richsmif: I have DPM 16 working with SQL 16. Install SQL 16 first, don't touch, install DPM 16 , upgrade to ...

  9. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    ptbNPA: That should have been *ID 810*, not 820

  10. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    ptbNPA: For anyone else coming across this in the future and have an ID 820 error: For some strange reason...

Archive

Tag Cloud