Exchange 2010 SP3 sort of stopping

[Jawloms]

Morning,

 

Weird problem with my exchange server. It stops delivering email. It seems to receive it all, just stops putting it in mailboxes. I reboot it and all is then delivered after only a few minutes. It then works for a few hours and then stops again. Anyone got any suggestions? All the services are running. Restarting the Information Store makes no difference. I can't see anything obvious in the logs. It did it the first time on Wednesday, and won't go 24 hours without stopping. Where to start??

 

Thank you

 

Stuart

[AJWhite1970]

Disk space on the server? Defrag needed on the exchange databases? Roll-up patches up to date?

[Jawloms]

230GB of disk space free. I'll look at defragging over the summer. All patched up to date.

[Domino]

Does that space include the drive where the exchange binaries are located?

[Jawloms]

It only has a C drive with everything on it. (I didn't set it up)

[k-strider]

not at work but personal email is handled by an exchange 2010 server and exactly the same has happened... last wed it stopped receiving mail from my postfix edge server.... restart and its fine.... i looked again today and the same mail queued up on postfix reboot it and it comes through... as its just my personal mail server and i am about to go on holiday i may just set it to reboot every night... and look at it later or may make me look at decommission and replacing with some thing else... i'm guessing its a windows update issue...

[tosh74]

Do you have .net framework 4.7 installed on the exchange server? If so remove it and stay with .net 4.5

[Jawloms]

4.7.1 is on and has been since March. Are there known issues with Exchange and 4.7 then?

[k-strider]

my Private email server has 4.7.1 on also and also since march...

[mjk]

Where to start??

 

I'd start here

https://tools.google.com/dlpage/exchangemigration

[tosh74]

https://blogs.technet.microsoft.com/exchange/2017/06/13/net-framework-4-7-and-exchange-server/

[Jawloms]

@tosh74 - Thank you, I think I'll uninstall it once we have broken up.

@mjk - Hell no!

[Jawloms]

I'm getting quite a few event 36888, source "Schannel". They say;

 

The following fatal alert was generated: 10. The internal error state is 1203.

 

Sometimes the internal error state is 10 rather than 1203. Any clues? I've obviously done some Googling, but nothing obvious is leaping out at me.

 

Stuart

[NetworkServices]

I've been having the exact same issue since Microsoft Updates installed over the weekend. Have a read through this and see if this is the same issue you're experiencing...

 

 

I've just uninstalled the mentioned updates and am waiting for it to fail again so that I have a good excuse to reboot the Exchange server to complete the uninstall.

 

See if you can spot Event ID 1009 popping up in the event logs.

Edited July 17, 2018 by NetworkServices

[Jawloms]

I've been having the exact same issue since Microsoft Updates installed over the weekend. Have a read through this and see if this is the same issue you're experiencing...

 

 

I've just uninstalled the mentioned updates and am waiting for it to fail again so that I have a good excuse to reboot the Exchange server to complete the uninstall.

 

I shall await your outcome I think, but thanks for letting me know.

 

Stuart

[NetworkServices]

After rebooting the server yesterday afternoon following another crash out, the updates finished uninstalling and this morning the server was working when I arrived. Previously it wouldn't go for more than 6 hours without crapping out but it seems to have survived the last 18.

 

For reference the update(s) causing the issue seems to be KB4338823 (July security only update) but it's likely that KB4338818 (July quality update) causes the same problem.

[Jawloms]

Uninstalled, rebooted, now waiting........

 

Thanks for the info. Much appreciated.

[Arthur]

For reference the update(s) causing the issue seems to be KB4338823 (July security only update) but it's likely that KB4338818 (July quality update) causes the same problem.

Microsoft have fixed the issue now...

 

Issue with July Updates for Windows on an Exchange Server

 

The Exchange team is aware of issues with the Windows Operating System updates published 10th July 2018 causing Exchange to not function correctly. The Windows servicing team has advised us that they will be releasing updates to the affected packages. We encourage Exchange customers to delay applying the 10th July updates, including the security updates released on the same date, on to an Exchange server until the updated packages are available.

 

Update: 17th July

 

We wanted to provide you an update on this issue.

 

The issue has been resolved and new updates will be available through Windows Update for all operating systems by end of day 17th July (PDT). The Exchange Team recommends that customers use Windows Update or update the catalogs on their own SUS servers to ensure the latest version of the update is available for installation on your Exchange Servers. Doing so will avoid any possible disruption to the MSExchangeTransport service which may have been impacted by the 10th July update.

[jthompson]

I'm so glad I found this thread. This problem has been driving me potty for the last week or so. Tried restarting various combos of services, convinced myself that it was a DNS issue, but only server reboots would fix it.

 

Will be very relieved if the update fixes it.