Here is what's happening when I or anyone else tries to send a meeting request to this user only under exchange 2007. We can send email and he can send email requests. Help!!!#550 4.4.1 STOREDRV.Deliver: connection timed out. The following information should help identify the cause: "MapiExceptionUnableToComplete:16.18969:261D0000, 17.27161:000000005E020000000000001302000000000000, 255.23226:00000000, 255.27962:7A000000, 255.27962:0A000000, 255.27962:0E000000, 255.27962:0A000000, 255.27962:0C000000, 255.17082:00040480, 0.18273:15000000, 4.21921:00040480, 255.27962:FA000000, 255.1494:10000000, 255.1238:4F000000, 6.21970:0F01048002018A670F010480, 4.23921:EC030000, 6.21970:0F0104800300F1670F010480, 6.21970:0F010480020185671DFAFFFF, 6.21970:0F01048040008F660F010480, 6.21970:0F010480020186670F010480, 6.21970:0F01048040008F660F010480, 6.21970:0F01048002018667EC030000, 6.21970:0F01048040008F660F010480, 6.21970:0F010480020186670F010480, 4.8916:E7FAFFFF, 4.14219:E7FAFFFF, 4.15243:E7FAFFFF, 4.12427:E7FAFFFF, 4.5312:0F010480, 6.21970:0F010480008013360F010480, 4.31473:0F010480, 6.21970:0F010480008013360F010480, 4.31473:0F010480, 4.6926:00040480, 255.1750:00040480, 255.31418:2E736B66, 0.21457:726F7570, 4.19665:00040480". ##

Do you see any related errors on your CAS server? Is the affected user able to send meeting requests to others? Are you able to send the user meeting reqeusts using outlook?Milind Naphade | MCTS:M | http://www.msexchangegeek.com

Not that I have found. The effected user can send meeting requests and we can send email. I am able to send others meeting requests.I have found one more user out of 65 that have the same problem.Thanks,-Greg

Hi,This issuemaycause bythe legacyExchangeDN was corrupted.First we need to improve the transport phase of the Diagnostics Logging levelin order to find the value information in Event log.For Exchange 2007http://technet.microsoft.com/en-us/library/bb201668(EXCHG.80).aspxAfter that, please view whether the below article can help you fix this issue:http://support.microsoft.com/kb/556074ThanksAllen

Hello,Could you grab the application log after enabling the diagnostic loggin as per Allen's suggestion?Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

Thanks for the responses I recieved. The problem was that the KB article existed but the information I used (error message, error codes, etc) did not bring up the article. Once we had that, it was fairly reasonable to fix. I would advise that anyone thinking of converting/upgrading to 2007 from 2003 or 2003SBS, setup the mail server and import the PST's. Converting was a night mare. We ran across several problems because 2007 does not seem compatible with 2003 or 2003SBS. I used two companys MCSE/MCP certified on Exchange 2003 and 2007. Even with MS Tech support, it took 3 weeks to resolve issues related due to compatibility. Niether MS or the two companies could point me to the three KB articles that saved the install.Thanks,-Greg

Greg,So finally the issue got resolved?Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

Yes, I was able to fix the problem.Thanks for all your help!-Greg

and Greg, what was the resolution?Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

Hi GregWatson,I am glad to hear the issue was resolved and the KB article can help you.ThanksAllen

Thanks for the responses I recieved. The problem was that the KB article existed but the information I used (error message, error codes, etc) did not bring up the article. Once we had that, it was fairly reasonable to fix. I would advise that anyone thinking of converting/upgrading to 2007 from 2003 or 2003SBS, setup the mail server and import the PST's. Converting was a night mare. We ran across several problems because 2007 does not seem compatible with 2003 or 2003SBS. I used two companys MCSE/MCP certified on Exchange 2003 and 2007. Even with MS Tech support, it took 3 weeks to resolve issues related due to compatibility. Niether MS or the two companies could point me to the three KB articles that saved the install.Thanks,-Greg What were the three KB articles you mention above? :-)

I know it's a little late, but we would like to share our experience with this issue. We were having the same problem in our organization during the migration from ex2003 to ex2007. The problem was happening between users in the same Exchange 2007 server, but not with exchange 2003. We didn't see any problems with legacyExchangeDN attributes, but tried changing it anyway. It obviously didn't help. We also tried isinteg and it seemed to work, but finally realized that by just dismounting and remounting the databases fixed the problem. At the end, a failover solved all of our problems with calendaring. Greetings.