Forum Discussion
Outlook Cannot Send Email After 1907 Build 11901.20080 Upgrade
Have also tried these builds and still having the same issue
August 13, 2019
Version 1908 (Build 11929.20114)
July 27, 2019
Version 1907 (Build 11901.20176)
July 25, 2019
Version 1907 (Build 11901.20156)
July 22, 2019
Version 1907 (Build 11901.20120)
Downgrade back to July 9, 2019 Version 1906 (Build 11727.20244) and all working fine again.
Dude you definately saved me from throwing my laptop against the wall. I fought this issue, too after the latest office update and first I found absolutely nothing on the internet that covered that problem.
We also have an on-premises Exchange 2010 SP3, currently Build 14.3.442.0 and O365 with password-hash SSO.
Did you already check it with newer builds of Exchange 2010?
- GrubsySep 02, 2019Copper Contributor
Interesting, we also have Build 14.3.442.0 and O365 with password-hash SSO
I haven't tried any of the newer builds of Exchange yet.
I have tried these with no luck:
August 25, 2019
Version 1908 (Build 11929.20254)August 16, 2019
Version 1908 (Build 11929.20182)We've scheduled to install Update Rollup 29 for Exchange Server 2010 SP3 July 9, 2019 14.3.468.0 this week. Will report back if that helps at all
- kerobraSep 02, 2019Copper Contributor
We are on Exchange 2010 SP3 UR29 since last friday, windows updates done except the previews for next patch day. I hoped it will solve the problem, but it didn't.
I can't believe that this combination is so "exotic" that nobody else has the problems we have.
One of our customers with Office 2016 seems to have the issue, too since last week but our tech department is still investigating. Since Office 2016/2019/365 share the same build numbers I gave them the hint to downgrade to the June version of office.
- GTuserSep 02, 2019Copper Contributor
Since the 1908 (11929.20254) update last week we've started to see this issue as well.
So far it's only been reported on a few systems and my only work around has been to enable cached exchange mode (were previously online).
What is annoying is that it's only affecting some users and I haven't been able to work out why.
We are also running Exchange 2010 SP3.