pchettri
asked on
Exchange 2013 event logs
I have hybrid deployment of office365 and recently I have been seeings lots of event logs for Front end transport and transport, as mentioned on this article
https://support.microsoft.com/en-us/kb/2989382
I have all email users and DB in on premise. Recently, I moved one user mailbox to office365 and user is unabel to send/receive email. I am seeing above error only afer recent CU update or I was not paying attention to those error when I upgraded my certificate on September. It is hard to tell if it started showing up after CU update o Jan 1 or after cert change, as I only have logs showing up from Jan 1 on app log. But I do see system logs with "An error occurred while using SSL configuration for endpoint 0.0.0.0:444. The error status code is contained within the returned data." from Sep 9th.
If I follow the above article, is there any chances that it will stop my mail flow on production on premise email? My connector are setup to deliver email from on premise to cloud and receive from on premise to cloud.
**************************
I have two DAG round robin Exchange 2013 with hybrid and all emails hosted on premise, except the one test user on office365 moved from on premise. Which is failing to receive emails with OutboundProxyTargetHostNa
On my on premise Exchange server I have few event error
Exchange 12014 error for Transport and Frontend transport
I was able to suppress Front end transport error with this article -
https://support.microsoft.com/en-us/kb/2989382
When I checked send connector I still see default client proxy, front end etc FDQN ECHLO connector as physical server (exchange2013.fc.local and the same for second server on DAG) name instead of FQDN on cert (mail.fabcm*.com)
Should I just go ahead and change it to certified FQDN as suggested on article? -
http://www.expta.com/2010/09/how-to-fix-msexchangetransport-event-id.html
Would it cause possible inbound mail issue on production on premise mailboxes, if I force this change?
https://support.microsoft.com/en-us/kb/2989382
I have all email users and DB in on premise. Recently, I moved one user mailbox to office365 and user is unabel to send/receive email. I am seeing above error only afer recent CU update or I was not paying attention to those error when I upgraded my certificate on September. It is hard to tell if it started showing up after CU update o Jan 1 or after cert change, as I only have logs showing up from Jan 1 on app log. But I do see system logs with "An error occurred while using SSL configuration for endpoint 0.0.0.0:444. The error status code is contained within the returned data." from Sep 9th.
If I follow the above article, is there any chances that it will stop my mail flow on production on premise email? My connector are setup to deliver email from on premise to cloud and receive from on premise to cloud.
**************************
I have two DAG round robin Exchange 2013 with hybrid and all emails hosted on premise, except the one test user on office365 moved from on premise. Which is failing to receive emails with OutboundProxyTargetHostNa
On my on premise Exchange server I have few event error
Exchange 12014 error for Transport and Frontend transport
I was able to suppress Front end transport error with this article -
https://support.microsoft.com/en-us/kb/2989382
When I checked send connector I still see default client proxy, front end etc FDQN ECHLO connector as physical server (exchange2013.fc.local and the same for second server on DAG) name instead of FQDN on cert (mail.fabcm*.com)
Should I just go ahead and change it to certified FQDN as suggested on article? -
http://www.expta.com/2010/09/how-to-fix-msexchangetransport-event-id.html
Would it cause possible inbound mail issue on production on premise mailboxes, if I force this change?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.