Unable to send calendar appointments internally for all users on Exchange 2007 - undeliverable messages

I have migrated from Exchange 2003 to Exchange 2007 and updated my address lists and email address policies.  I started decommissioning the Exchange 2003 server and immediately new calendar appointments are undeliverable for all users.  I checked the ExchangeLegacyDN as described in the Microsoft KB article and those are correct.  I have created two new mailboxes on the 2007 server and still get the same undeliverable messages.  I am running Exchange SP1 Rollup 7.  I have disabled the virus scanning software. The three errors recorded on the Exchange 2007 server after each appointment sent are 8199 8213 and 8230.

Any suggestions?
A communication failure occurred during the delivery of this message. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or provide the following diagnostic text to your system administrator
#550 4.4.1 STOREDRV.Deliver: connection timed out. The following information should help identify the cause: "MapiExceptionUnableToComplete:16.18969:961D0000, 17.27161:0000000066020000000000007D00000000000000, 255.23226:00000000, 255.27962:7A000000, 255.27962:0A000000, 255.27962:0E000000, 255.27962:0A000000, 255.27962:0C000000, 255.17082:00040480, 0.18273:00000000, 4.21921:00040480, 255.27962:FA000000, 255.1494:10000000, 255.1238:4F000000, 6.21970:0F010480020185670F010480, 6.21970:0F01048040008F660F010480, 6.21970:0F010480020186670F010480, 6.21970:0F01048040008F660F010480, 6.21970:0F010480020186670F010480, 6.21970:0F01048040008F660F010480, 6.21970:0F010480020186670F010480, 4.8916:E7FAFFFF, 4.14219:E7FAFFFF, 4.15243:E7FAFFFF, 4.12427:E7FAFFFF, 4.8916:E7FAFFFF, 4.14219:E7FAFFFF, 4.15243:E7FAFFFF, 4.12427:E7FAFFFF, 4.9867:E7FAFFFF, 6.21970:0F01048000801336E7FAFFFF, 4.31473:0F010480, 6.21970:0F01048000801336E7FAFFFF, 4.31473:0F010480, 4.6926:00040480, 255.1750:00040480, 255.31418:2B0A0000, 0.21457:2B0A0000, 4.19665:00040480". ##

Open in new window

Who is Participating?
robertswmConnect With a Mentor Author Commented:
Re-applying Exchange SP1 rollup 7 has resolved the issue.
Did you also migrate the public folder hierarchy to the 2007 server?
And actually the public folders for that matter?
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

robertswmAuthor Commented:
Yes, I replicated all the public folders/hierarchy over to Exchange 2007 and then removed the replica set from 2003 before starting the decom process.
robertswmAuthor Commented:
This is also happening in OWA when sending calendar appointments to users internal.  I send/receive appt from external sources with no problems.

Url: https://mail.domain.com:443/owa/ev.owa?oeh=1&ns=EditCalendarItem&ev=Send
User host address:
User: Bill Roberts
EX Address: /o=Company/ou=Exchange Administrative Group (XXXXXXXXXXXXX)/cn=Recipients/cn=broberts
SMTP Address: Bill.Roberts@company.com
OWA version: 8.1.359.2
Mailbox server: Exchange.corp.company.com
Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException
Exception message: Cannot save changes made to an item to store.
Call stack
Microsoft.Exchange.Data.Storage.MapiPropertyBag.SaveChanges() Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.SaveChanges(Boolean commit) Microsoft.Exchange.Data.Storage.AcrPropertyBag.SaveChangesWithAcr(SaveMode saveMode) Microsoft.Exchange.Data.Storage.Item.SaveInternal(SaveMode saveMode, Boolean commit) Microsoft.Exchange.Data.Storage.CalendarItemBase.SendMeetingMessages(Boolean isToAllAttendees, Boolean copyToSentItems) Microsoft.Exchange.Data.Storage.CalendarItem.SendMeetingMessages(Boolean isToAllAttendees, Boolean copyToSentItems) Microsoft.Exchange.Clients.Owa.Premium.EditCalendarItemEventHandler.Send()
Inner Exception
Exception type: Microsoft.Mapi.MapiExceptionUnableToComplete
Exception message: MapiExceptionUnableToComplete: Unable to save changes. (hr=0x80040400, ec=-2147220480) Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=1308] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=598][latency=31] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropSetProps [10] Lid: 27962 ROP: ropFlushRecipients [14] Lid: 27962 ROP: ropSetProps [10] Lid: 27962 ROP: ropSaveChangesMessage [12] Lid: 17082 ROP Error: 0x80040400 Lid: 18273 Lid: 21921 StoreEc: 0x80040400 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 1238 Remote Context Overflow Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 Lid: 23921 StoreEc: 0x3EC Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67F10003 Lid: 21970 StoreEc: 0x8004010F PropTag: 0xE630003 Lid: 23921 StoreEc: 0x3EC Lid: 21970 StoreEc: 0x8004010F PropTag: 0xE640003 Lid: 4781 StoreEc: 0xFFFFF9BF Lid: 4269 StoreEc: 0x46C Lid: 7821 StoreEc: 0x46C Lid: 6293 StoreEc: 0x46C Lid: 7181 StoreEc: 0x8004010F Lid: 61001 Lid: 11621 StoreEc: 0x8004010F Lid: 21970 StoreEc: 0x8004010F PropTag: 0xF000102 Lid: 28877 Error: 0x0 Lid: 8424 StoreEc: 0x8004010F Lid: 5750 StoreEc: 0x8004010F Lid: 4884 StoreEc: 0x80040400 Lid: 4465 StoreEc: 0x80040400 Lid: 6926 StoreEc: 0x80040400 Lid: 1750 ---- Remote Context End ---- Lid: 31418 --- ROP Parse Done --- Lid: 21457 Lid: 19665 StoreEc: 0x80040400
Call stack
Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo) Microsoft.Mapi.MapiProp.SaveChanges() Microsoft.Exchange.Data.Storage.MapiPropertyBag.SaveChanges()

Open in new window

I still have the problem inspite i have Exchange 2007 SP2!!!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.