Exchange 2010 Transport service fails without errors or warnings
Running an old Exchange 2010 server for a small client. Problem started out of the blue. The indicators were that SMTP connections were timing out from both the Outlook clients and the Internet mail relays. Service was apparently running, but could not be stopped. Would just hang at "stopping". TASKKILL without force would say that it could not stop it, and TASKKILL with /FORCE said it was not running, yet it was listed by TASKLIST.
Only way to get the server back up and running is a full reboot. When it started to happen, it happened about every 8 hours. After deleting the old mail.que, which was 250MB, it now gets to 12hrs at a time. It is up to SP3 and Roll-up 21, although the admin interface still displays the basic SP3 version, but from what I have read, this is reasonably common, and the versions on the executables seems to be correct.
It isn't out of disk space, it isn't out of RAM, there are no back pressure warnings, in fact there are no warnings at all. Store cache has been limited and the box sits at 65% RAM. I have been looking at all sorts of options, even restarting the service every hour, but that didn't help.
Nothing in the anti-virus logs that would indicate it was doing anything. No clue anywhere in the Event Logs, nothing that I can see in the transport logs.
I am very confused :-(
Only way to get the server back up and running is a full reboot. When it started to happen, it happened about every 8 hours. After deleting the old mail.que, which was 250MB, it now gets to 12hrs at a time. It is up to SP3 and Roll-up 21, although the admin interface still displays the basic SP3 version, but from what I have read, this is reasonably common, and the versions on the executables seems to be correct.
It isn't out of disk space, it isn't out of RAM, there are no back pressure warnings, in fact there are no warnings at all. Store cache has been limited and the box sits at 65% RAM. I have been looking at all sorts of options, even restarting the service every hour, but that didn't help.
Nothing in the anti-virus logs that would indicate it was doing anything. No clue anywhere in the Event Logs, nothing that I can see in the transport logs.
I am very confused :-(
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
tec_interway: What a star: Am about to restart after uninstalling (BTW I think this is the wrong way round "Yes I uninstalled KB4340556 which is the Win2008R2 version of KB4338420 (which is for Svr 2008) "). The server I am looking at is 2008R2 and KB4338420 was installed, not KB4340556.
Will let you know in 8 to 12 hours !
Will let you know in 8 to 12 hours !
Hi,
MS finally says it is aware of July update :)
https://blogs.technet.microsoft.com/exchange/2018/07/16/issue-with-july-updates-for-windows-on-an-exchange-server/
Regards,
Ivan.
MS finally says it is aware of July update :)
https://blogs.technet.microsoft.com/exchange/2018/07/16/issue-with-july-updates-for-windows-on-an-exchange-server/
Regards,
Ivan.
Another link that may help.
https://www.experts-exchange.com/questions/29109331/Exchange-update.html
https://www.experts-exchange.com/questions/29109331/Exchange-update.html
ASKER
Awarding tec_interway as he was first to point me in the right direction. Not 100% sure the problem is fixed yet but there are now some many people pointing the finger in the same direction that I am happy this will allow me to fix the problem
In our case these are IPv4/IPv6 dual-stack configured servers and only the IPv4 Port25 listener stops working, (can also be seen via netstat -an | find ":25 ") but not the IPv6 one or the ones for port 465 or 587.
Stopping/Restarting the Exchange Transport Service does not fix the issue, as the "Edge Transport.exe" process keeps hanging and cannot be killed under any circumstances. (tried with process explorer, pskill, etc.)
Only a server reboot does help.
We are desperate to find a solution, but no luck yet.