Hello, after applying Exchange 2013 CU2, our users can no longer forward calendar invites to other users.  We have read online that Office 365 users are having this issue as well, but can't find a workable solution.  Anyone else having this issue and found any solutions?  Here is snip-it from the NDR:

The following recipient(s) cannot be reached: John Smith on 7/31/2013 2:55 PM This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].

Thanks!

Hello,

Please check if outlook and owa have the issue. If outlook and owa have the issue, you may need to wait CU3 to check the result.

You can see pesos's post in the following blog.

Released: Exchange Server 2013 RTM Cumulative Update 2

http://blogs.technet.com/b/exchange/archive/2013/07/09/released-exchange-server-2013-rtm-cumulative-update-2.aspx                                            

If owa is fine, I recommend you recreate outlook profile to check the result.

Besides, there is no article to explain the issue. To solve your issue as soon as possible, you can contact microsoft support to verify the issue.

If you have any feedback on our support, please click here

Yes, the issues occurs both Outlook and OWA.  In OWA, you don't get the NDR, but instead an error message stating you don't have permission to forward the invite (which should not be the case).  This a major CU2 bug?

Thx

Hello, thanks for the reply.  I have confirmed NT AUTHORITY\SELF has Full Access on the mailbox.  I have also created new meeting request and can easily reproduce the issue.

We have also be able to confirm that this worked right up until installing CU2. 

Also, we found this post: http://community.office365.com/en-us/forums/158/t/176107.aspx?PageIndex=2.  This refers to Office 365 (which to my understanding runs the same code).  The post implies its a known issue with a fix, but I can't find any interim update available for on-premise customers.

Thx!

Hello,

At present,  we don't verify whether this is a CU2 bug.

From the error code, this is a permission problem.

So I recommend you check if you have full permission for self on your mailbox.

Besides, I recommend you to create a new meeting request and then forward it to check the result.

If you have any feedback on our support, please click here

Hello,

Yes. There is no related article to verify whether this is a known issue.

You can wait CU3 to check if the issue occurs.

If you have any feedback on our support, please click here

Isn't CU3 still about 3 months away?  Our users need this fixed asap (as they do this everyday), and 3 months is way to long to wait to get fixed.  We would uninstall CU2 and roll back, but unfortunately this isn't possible in the current model. Are there no solutions for our users to do something that they need to be able to do?

Hello,

Sorry for delayed response.

We mainly refer to technet article and some blogs. I have read some materials ,I'm afraid there is no solution to troubleshooting the issue at present.

If your issue is emergency, I recommend you contact microsoft support.

My organization is having the same issue. Has a solution been found?

thanks

I support several Exchange environments. Now, after applying CU2v2 to all the Exchange servers, people can no longer forward meetings like they could just last week.

Thanks.

I had opened a case with MSFT and they said it was a known issue.  HOPEFULLY it will be fixed in CU3, but MS would not confirm a fix is scheduled for CU3.

We have been fighting the same issue..

MS support has told us it will be fixed in CU3 due in late November.

Our work around for now is to use the "forward as iCalendar" option in outlook.

The biggest problem is that most of our user base uses OWA. iCalendar is not an option. It makes me look like a fool for updating the server to CU2v2.

Hi

My organization having same issue running.

"The following recipient(s) cannot be reached: User Full name on 7/31/2013 2:55 PM This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000]."

if anyone resolved this issue before , please let me know.