Reports that this month’s Outlook update knocks out Search via Exchange Server

Topic

New Reply

I’ve seen several reports along this line, from u/leaker929 on Reddit: Over the weekend Outlook updated version 2004 build 12730.20236 and now they ha
[See the full post at: Reports that this month’s Outlook update knocks out Search via Exchange Server]

1 user thanked author for this post.

lmacri

Reply | Quote

Replies

And, sure enough, @tressie reported the same problem yesterday on AskWoody.

@b has a couple of updates, including this, posted yesterday:

The author of this Microsoft article indicates, in a comment at the bottom a couple of hours ago, that he’s aware that this update has affected Outlook search and is apparently escalating for a fix:

How Outlook 2016 utilizes Exchange Server 2016 FAST Search – abdias_ruiz Microsoft

Worth noting: We’re talking about a Monthly Channel release here.

Reply | Quote

I’ve just got a mail from my client who’s using Office 2016, that the all were hit by this problem. The search is not working anymore. They all are using outlook’s cached mode and local search.

Reply | Quote

These settings get the search working again:

Exchange on Premise

Key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Search

Value name: DisableServerAssistedSearch

Value type: REG_DWORD

Value: 1

Exchange Online (365)

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Search Value name: DisableServerAssistedSearch Value type: REG_DWORDValue: 1

Reply | Quote

Should be fixed today:

https://techcommunity.microsoft.com/t5/outlook-global-customer-service/how-outlook-2016-utilizes-exchange-server-2016-fast-search/bc-p/1381050/highlight/true#M28

Reply | Quote

Microsoft: Fix for Outlook search failures coming later today

1 user thanked author for this post.

lmacri

Reply | Quote

I use MS Office Home and Business 2019 Version 2004 (Click-to-Run) on a 64-bit Win 10 Pro v1909 Build 18363.778 OS (May 12, 2020 KB4556799 / Build 18363.836 not installed yet) and just encountered this issue with the Search function in MS Outlook 2019. I was on Build 12730.20250 yesterday (16-May-2020) when I first noticed this problem with the Search feature and a manual update today to the latest Build 12730.20270 hasn’t fixed the problem. If I click the “Let’s look on your computer instead” link shown in the attached image the Search function works correctly and finds matches for messages downloaded to my local machine.

I don’t know if the two problems are related but I should have received an automatic update to Build 12730.20270 (rel. 12-May-2020) a few days ago since MS Office 2019 is C2R. Fortunately, I was able to apply this patch manually per my post # 2263256 in Woody’s Reports that this month’s Outlook update knocks out Search via Exchange Server.

Reply | Quote

lmacri wrote:

I don’t know if the two problems are related

The search issue and the updating issue are separate.

The search issue started more than 10 days ago and is still not fixed.

The updating issue started less than 2 days ago and appears to be fixed.

Reply | Quote

When I first read Woody’s article about this Outlook search problem on 08-May-2020 I immediately tested on my own Win 10 Pro v1909 machine and was pleasantly surprised to see the Search function was still working correctly with my MS Office 2019 Home & Business Version 2004 Build 12730.20250 (rel. 04-May-2020).  I understand that reports about this problem date back to 06-May-2020 but I use the Search function in Outlook 2019 almost every day so I have no idea why this issue didn’t appear on my machine until 16-May-2020.

Sergiu Gatlan’s 13-May-2020 article Microsoft: Fix For Outlook Search Failures Coming Later Today on BleepingComputer was updated this past Friday and now states “Update May 15, 13:00 EDT: Microsoft is rolling out a fix for the Outlook search issues to all affected environments…“. Does anyone know the Outlook build number for the Version 2004 hotfix that is supposed to correct this problem? I don’t see anything listed beyond Build 12730.20270 (rel. 12-May-2020) in the update history at https://docs.microsoft.com/en-us/officeupdates/update-history-office-2019#retail-versions-of-office-2016-c2r-and-office-2019.

Reply | Quote

Just an update that Search function appears to be working correctly today in my MS Office Home and Business 2019 Version 2004 Build 12730.20352 (Click-to-Run), although I’m not sure what solved the problem. I ran a manual update on 25-May-2020 to update MS Office 2019 to Build 12730.20352 (see my post <here> about known issues with automatic C2R updates), but I had previously confirmed that this MS Outlook 2019 build didn’t fix my search problem on the Exchange Servers. My OS hasn’t changed recently – I’m still using 64-bit Win 10 Pro v1909 Build 18363.778.

I don’t know if it’s relevant, but my Windows Search box is currently on Build 2020.05.28.8245621.

1 user thanked author for this post.

b

Reply | Quote

Exchange Online service alert

Advisory information

Title: Many users will see searches failing in the Outlook desktop client
ID: EX212460

Status

Service Restored

Details

Title: Many users will see searches failing in the Outlook desktop client

User Impact: Users may have experienced search failures in the Outlook desktop client.

More info: Users’ searches would default to a local search and they would have been unable to search for content that resides within the Exchange Online service. This issue was only affecting on-premises users using non-modern authentication.

Users who had access to Outlook on the web may have been able to use that protocol as an alternative method to search the service.

Final status: Following a period of monitoring the affected environment, we’ve confirmed that our fix to correct the routing of search requests has been successful in remediating impact.

Scope of impact: This issue may have potentially affected any of your users attempting to search in their Outlook desktop clients.

Start time: Monday, May 4, 2020, at 4:00 PM UTC

End time: Thursday, May 21, 2020, at 10:00 PM UTC

Root cause: A code issue within the authentication process was misrouting search requests, causing some requests to fail.

Next steps:

– We’re reviewing our authentication and search request routing processes, to find ways to prevent this problem from happening again.

This is the final update for the event.

Thank you,
The Microsoft team

https://techcommunity.microsoft.com/t5/outlook-global-customer-service/how-outlook-2016-utilizes-exchange-server-2016-fast-search/ba-p/381195/page/2#comments
[reposted near bottom of comments]

Reply | Quote