exchange cu20

It's cliché, but see if a reboot addresses the problem, even if it's only temporarily.

I tried it..no luck.

And all the Exchange services are running?

What happens if you telnet to the server on port 25?  Type "EHLO" if it answers, and press <ENTER>.

Please go in to IIS and restart all app pools for Exchange

OK, I restarted all of these but one failed to start.
update the last one started after refresh
is.PNG

Same problem after going to IIS and restarting all app pools for Exchange

Hi, can you check your bindings in IIS that they are bound to your ssl cert? What errors are you seeing in the event log?

Kind regards
Edward (Exchange MVP)

I'm so out of my leage here but....so I found this on the log - this was an sbs 2008 before that got migrated to new server. The new server was running fine until the cu20 was installed last night. under the event viewer I found this

Log Name:      Application
Source:        MSExchangeTransport
Date:          8/14/2018 10:37:41 AM
Event ID:      5016
Task Category: Routing
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EXCHANGE.xx.local
Description:
Microsoft Exchange could not discover any route to connector CN=Windows SBS Company Web Connector SERVER,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mge,DC=local in the routing tables with the timestamp 8/14/2018 5:37:41 PM. This connector will not be used.  Total source server count: 1; unknown source server count: 1; unrouted source server count: 0; non-active source server count: 0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="49156">5016</EventID>
    <Level>2</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-08-14T17:37:41.000000000Z" />
    <EventRecordID>13509228</EventRecordID>
    <Channel>Application</Channel>
    <Computer>EXCHANGE.xxx.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>CN=Windows SBS Company Web Connector SERVER,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mge,DC=local</Data>
    <Data>8/14/2018 5:37:41 PM</Data>
    <Data>1</Data>
    <Data>1</Data>
    <Data>0</Data>
    <Data>0</Data>
  </EventData>
</Event>

If the server does not exist anymore you might need to use adsiesit to delete the old entry for the sbs server.

Do you think that could be causing the problem after the cu20?

I'm surprised it hasn't caused issues before you upgraded but if you came from a lower version and went to cu20 and had a schema/ad upgrade it can, nobody knows what the exchange code does besides Microsoft.

Just to make sure that your dns entries are still there for autodiscover and pointing to the 2013 server?

If you do a test connectivity check from outlook, is autodiscover working or giving an error?

Run the test commands to check Outlook connectivity and check what error it gives.

I hired someone to resolve this issue and he was unable to do so. He worked out of this

https://blogs.technet.microsoft.com/exchange/2018/07/16/issue-with-july-updates-for-windows-on-an-exchange-server/#comment-342755

and also updated my .Net to 4.7.2.

He also worked on verifying my dns and auto-discovery and IIS settings. Attached is a copy of what I get on an outlook 2013 test connections
Inkedandrea_LI.jpg

Dot net 4.7.2 is not supported on exchange

The problem was resolved by a Microsoft rep.
I started this ordeal by trying to get my server to communicate TLS 1.2 encrypted emails with a supplier. At one point I had disabled tsl 1.1 and 1.0.

After I disabled I installed CU 20 and rebooted. By disabling TSL I broke the communication between outlook 2013 and 2010. Only my workstations using outlook 2016 where connecting. After some troubleshooting by the ms tech he figured out my mistake and enabled. All of the workstations connected fine. I'm back to my original task but at least my end users have outlook. I appreciated all of the support!

Thanks

Thanks for sharing your feedback.