Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Users are unable to receive meeting requests and meeting updates in Exchange Server 2007


Author: Shijaz Abdulla MVP

View products that this article applies to.

Summary

This article discusses a problem which causes certain calendaring features to be unavailable to certain users in Exchange Server 2007.

↑ Back to the top


Symptoms

Affected users�are be unable to receive meeting requests, meeting updates and meeting cancellations. However, these users will be able to send and receive email messages. The incoming meeting requests will remain in the delivery queue on the machine running the Exchange Server 2007 hub transport server role with the following error:

Status: Retry
Last Error: 430 4.2.0
STOREDRV.Deliver.Exception:MAPIExceptionCanNotComplete


Additionally, the following events may be logged in the Application log of the Exchange Mailbox server that contains the user's mailbox:

Event Type:�Warning
Event Source:�EXCDO
Event Category:�General
Event ID:�8230
Date:��3/19/2008
Time:��10:24:24 AM
User:��N/A
Computer:�
<servername>
Description:
An inconsistency was detected in user@domain.com : /Calendar/Test.EML.� The calendar is being repaired.� If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access.� If a problem persists, please recreate the calendar or the containing mailbox.


For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:�Error
Event Source:�EXCDO
Event Category:�General
Event ID:�8206
Date:��3/19/2008
Time:��10:24:24 AM
User:��N/A
Computer:�
<servername>
Description:
Calendaring agent failed with error code 0x80040215 while saving appointment.


For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:�Error
Event Source:�EXCDO
Event Category:�General
Event ID:�8213
Date:��3/19/2008
Time:��10:24:24 AM
User:��N/A
Computer:�
<servername>
Description:
Calendaring agent failed to update the free/busy cache during an appointment save or delete operation.


For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:�Error
Event Source:�EXCDO
Event Category:�General
Event ID:�8199
Date:��3/19/2008
Time:��10:24:24 AM
User:��N/A
Computer:�
<servername>
Description:
Calendaring agent failed in message save notification with error 0x800703eb on user@domain.com
: /Calendar/test.EML.

For more information, click http://www.microsoft.com/contentredirect.asp.

Additionally, the user may not be able to create appointments in his calendar and may be unable to dismiss or snooze reminders while using Outlook Web Access.

↑ Back to the top


Cause

This problem may be caused by�malformed value for the�legacyExchangeDN attribute on the affected user object

↑ Back to the top


Resolution

If the cause of the problem is a malformed legacyExchangeDN attribute, this can be verified and rectified as follows:

  1. On a machine that has the Windows Support Tools installed, click Start, Run and type�adsiedit.msc and click OK.
  2. In�the�ADSIEDIT utility, expand Domains, dc=domain,dc=com and�expand the container OU of the affected user.
  3. Right click on the user (CN=Full name) of the user and choose Properties.
  4. In the Attributes list, scroll down and�select the legacyExchangeDN attribute.
  5. Click the Edit button.
  6. Check if the value is of the form: /o=OrganizationName/ou=First Administrative Group/cn=Recipients/cn=username and that it is not malformed. Most commonly, it maybe malformed to read /o=OrganizationName/ou=First Administrative Group/cn=Recipientsusername with a missing '/cn=' after '/cn=Recipients'.
  7. Correct the value, click OK twice and close ADSIEDIT.

↑ Back to the top


More information

When you change the legacyExchangeDN attribute for a user, you should rebuild the Global Address List. Emails sent by other users in the organization may not deliver to the affected user after fixing the legacyExchangeDN attribute if the sender�types the name of the affected recipient from�the Outlook�"cache"�(AutoComplete). However, if the sender selects the affected user from the GAL, the e-mail message is delivered.

A workaround for this would be to add the old (incorrect) value�of the legacyExchangeDN as a value in the proxyAddresses attribute for the affected user to ensure e-mail delivery even from cached incorrect entries in Outlook.

For an Exchange Server 2003 version of this article, see KB article 556073 (http://support.microsoft.com/kb/556073)

↑ Back to the top


Properties

COMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

↑ Back to the top


Community solutions content disclaimer

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.

↑ Back to the top


Keywords: KB556074, kbhowto, kbpubtypecca, kbpubmvp

↑ Back to the top

Article Info
Article ID : 556074
Revision : 1
Created on : 3/20/2008
Published on : 3/20/2008
Exists online : False
Views : 363