This issue occurs due to the changes in the Outlook 2016 architecture that does not create the MAPI attribute "ROHFLAGS_USE_ROH" when Outlook 2016 connects to Exchange 2010 mailboxes. Note: For information on how to perform an Enterprise Vault client trace review article : Microsoft Windows XX, XX Edition (build XXXXX 10240), : Enterprise Vault Client XX.X.X.XXX (Light/Full functionality enabled) : ~DesktopCommon::UseRPCOverHTTP: Read PR_ROH_FLAGS: 0x40380 : RPC over HTTP is not enabled (flags = 0) : DesktopCommon::UseRPCOverHTTP: Read PR_ROH_FLAGS: 0x0 The following lines are captured in the workstation's Enterprise Vault client trace log: We can see this by clicking to expand the entry using the arrow on the left hand side of the Message Events table.Outlook 2016 users can no longer use several Enterprise Vault functions when mailboxes reside on Exchange 2010, and Outlook is using RPC over http/https from an external network. Taking one message as example, we can see that the message delivery to on-premises failed and that a specific error code of 4.4.316 was reported. Multiple messages were then seen in the queue. For more complex situations please review Andrew’s excellent EOP blog, specifically the Parsing an extended message trace post.Īfter entering the relevant time slot, and expected recipient the trace was executed. This was sufficient to troubleshoot this issue.
This can also be customised to suit the specific requirement. There are pre-canned queries to search emails from the last 24 or 48 hours. In the below example note that the focus is on the Mail Flow, and then message trace.
Reviewing the Queues in Office 365 is also straightforward. Queue Viewer can be found under the Exchange toolbox, which is built into the Exchange 2010 MMC and as a separate Start Menu item in Exchange 2013/2016. In order to look at the mail queues on-premises, we can use the Get-Queue cmdlet or the Queue Viewer. The issue was the mail flow from cloud to on-premises.
There were no issues sending email from the on-premises Exchange servers to Office 365. Some email was flowing from Office 365, but some was delayed or not delivered at all. Apparently this had been working previously with no issues, then mailflow started to have problems. This is a repro of a customer reported issue where they were having issues sending email from Office 365 to on-premises Exchange servers.
0 kommentar(er)
