Skip to main content

A meeting update message or a meeting cancellation message is not delivered.

One of my user complained that he wasn't able to send a meeting update or meeting cancellation to any outside recipients. This is a big issue in our company because the organizer coordinate schedules of 5 to 25 (even more) consultants in the field. If they received the initial meeting schedule but not the cancellation or meeting update, then the coordinator is in trouble.

Microsoft Exchange Server 2010 Best Practices (Best Practices (Microsoft))In technical scenario. A Microsoft Exchange Server 2003 and a Microsoft Exchange Server 2007 organization exchange communication. An Exchange 2003 user organizes a meeting and then send a meeting requests to an Exchange 2007 user. Then, the meeting organizer uses Microsoft Outlook to send a meeting update or meeting cancellation message to the Exchange 2007 user. The update or cancellation update is not delivered to the Exchange 2007 user. To troubleshoot this issue, you can check your Exchange 2003 SMTP queue where you can see this update or cancellation message still waiting to deliver.

How to fix this issue? Microsoft already received a lot of complain about this issue, so the Hotfix is already available for you. Here's the link:

There is also a way "Let me fix it myself" guide on how to accomplish this task manually, also included in the KB938650. Here's the step-by-step guide:

  1. Click Start, click Run, type Regedit, and then click OK.
  2. Locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent\MimeHandlers\{85D2DDB8-6225-11D2-BDF1-00C04FD655B5}
  3. On the Edit menu, point to New, and then click DWORD Value
  4. In the details pane, type FixRecipientTrackStatusTime for the new value, and then press ENTER.
  5. Right-click FixRecipientTrackStatusTime, and then click Modify.
  6. In the Edit DWORD Value dialog box, click Decimal under Base.
  7. In the Value data box, type 1, and then click OK.
  8. Exit Registry Editor.
The server will not require to restart the server but I highly recommend it to make sure that everything is working as expected.



Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​ - Wordpress (Open Source and Free) - (Open Source and Free)Commercial Social Networks software ($299 Stand Alone, $29/mo Cloud) (run with Joomla, need to know CMS) (very expensive, $399 for Standard) (from free to Commercial, I left my networks and they are selling it (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company) (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here: