Bert McFerrin
asked on
Mail flow stops
Exchange 2013 running on virtual server Hyper V
Hyper V server windows Server 2012 R2
Exchange 2013 setup in hybrid mode with Office 365
Mail stops flowing for no reason, I opened a ticket with Office 365 Support, and after several checks and adjustments no solution.
Last suggestion from Office 365 Support team was to check Time sync Issues/configuration on Hyper V Server.
Can this cause mail to stop flowing?
No NDR's
Solution to get mail flowing again has been to shut down Exchange down
Reboot Hyper V server and restart Exchange
Average uptime for exchange is 24 to 36 hours.
Thanks
Bert McFerrin
Hyper V server windows Server 2012 R2
Exchange 2013 setup in hybrid mode with Office 365
Mail stops flowing for no reason, I opened a ticket with Office 365 Support, and after several checks and adjustments no solution.
Last suggestion from Office 365 Support team was to check Time sync Issues/configuration on Hyper V Server.
Can this cause mail to stop flowing?
No NDR's
Solution to get mail flowing again has been to shut down Exchange down
Reboot Hyper V server and restart Exchange
Average uptime for exchange is 24 to 36 hours.
Thanks
Bert McFerrin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Mark is correct.
Here are my notes on Backpressure.
Back Pressure Logging Information
The following list describes the event log entries that are generated by specific back pressure events in Exchange 2010:
} Event log entry for an increase in any resource utilization level
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15004
Description: Resource pressure increased from Previous Utilization Level to Current Utilization Level.
} Event log entry for a decrease in any resource utilization level
Event Type: Information
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15005
Description: Resource pressure decreased from Previous Utilization Level to Current Utilization Level.
} Event log entry for critically low available disk space
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15006
Description: The Microsoft Exchange Transport service is rejecting messages because available disk space is below the configured threshold. Administrative action may be required to free disk space for the service to continue operations.
} Event log entry for critically low available memory
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15007
Description: The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold. This may require that this service be restarted to continue normal operation.
From <https://technet.microsoft.com/en-us/library/bb201658(v=exchg.141).aspx>
Here are my notes on Backpressure.
Back Pressure Logging Information
The following list describes the event log entries that are generated by specific back pressure events in Exchange 2010:
} Event log entry for an increase in any resource utilization level
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15004
Description: Resource pressure increased from Previous Utilization Level to Current Utilization Level.
} Event log entry for a decrease in any resource utilization level
Event Type: Information
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15005
Description: Resource pressure decreased from Previous Utilization Level to Current Utilization Level.
} Event log entry for critically low available disk space
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15006
Description: The Microsoft Exchange Transport service is rejecting messages because available disk space is below the configured threshold. Administrative action may be required to free disk space for the service to continue operations.
} Event log entry for critically low available memory
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15007
Description: The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold. This may require that this service be restarted to continue normal operation.
From <https://technet.microsoft.com/en-us/library/bb201658(v=exchg.141).aspx>
Yes, Guest machines are running under your Host machines.
The mail has to be queuing up somewhere. We need to find where and see if there is a problem where the mail is being queued up on.
The mail has to be queuing up somewhere. We need to find where and see if there is a problem where the mail is being queued up on.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a lot for all the input I am going thru all suggestions.
B
B
ASKER
Issue was resolved by correcting Time sync setting on Exchange server to point to correct domain controller.
Thanks to all for their suggestions
Bert McFerrin
Thanks to all for their suggestions
Bert McFerrin
ASKER
No info in Applications Logs.
Stop and restart of transport service will not restore flow
Restart of Hyper-V server and restarting Exchange restores Mail flow
The que will have some pending status conditions but Office 365 Support could not see any meaningful info from them