Hello,
This morning I suddenly received several messages that the instant search in Outlook is no longer working. So far there didn't seem to be any problems and now Outlook suddenly spits out an error message.
"Something didn't work out, the search couldn't be completed. "
Below the note:
"Let us look on your computer instead."
If you click on it, the search works normally.
I have already gone through the usual solutions.
Remove Outlook from the index.
Add Outlook to the index again.
Recreate index.
Repair Pst.
Start Outlook in safe mode.
Disable Windows Search completely.
Nothing seems to help.
Why does this message appear at all? Shouldn't Outlook always search locally first?
Incidentally, everything runs locally in connection with Exchange 2016, not in the cloud.
Does anyone have any ideas?
Sorry, just typed that down on my cell phone. Can't edit the post either?
Additional info:
The search works both on the cell phone (Outlook app) and via OWA. Only Outlook itself seems to produce the problem :/
Even if I only write to myself :D
I have found a solution and have been able to use it successfully several times.
Here in the link:
https://community.spiceworks.com/topic/2201491-outlook-2019-search-fix
I pushed the settings via GPO and now the instant search works again.
Outlook in cache mode?
Yes, I have already posted the solution, but it is still in moderation.
Okay. But it's a double-edged sword. It's a fix that corrects the symptoms but not the cause, unfortunately. I have a bunch of customers who only have 3-6 months in their cache, they depend on the search on the server. If it helped you ok, but that's the kind of thing that you fall over again 2 years later because something else doesn't work and nobody thinks to look in the registry (or the GPO) ;-)
That is of course correct. But until MS has a fix, this is a working stopgap solution.
Hello,
We have also recently started experiencing this error and have not yet been able to narrow it down any further. We have an Exchange 2016 server and the errors actually only occur with Outlook 2019/2016, Outlook 2013 works perfectly.
Greetings Ingo
I now also have a user who has problems with the search. Same error pattern. I'll take a look at it this week.
Have also had the problem for a few days, Exchange Server 2013, error only occurs with Outlook 2019/2016, Outlook 2013 works perfectly - as with Ingo's Exchange Server 2016
I also support several customers with Exchange 2016 and Office 2016/2019, both in the 32- and 64-bit version. Same error. It started with one workstation (the workstations are maintained via WSUS and shut down daily), then several more were added daily. There is no plausible reason for this, the users always receive the error message
Something went wrong and your search could not be completed.
In 2017, there were various Microsoft updates that have already caused this error. If there isn't something up again ;)
Since so many have it, there will probably be a general problem at MS.
As an emergency solution I can only give this Reg entry:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Search]
"DisableServerAssistedSearch"=dword:00000001
For me, deactivating the cache mode solved the problem for the time being. But as the others have already written, the problem poof poof poof popped up. First one client, then a few more and so on.
Hi,
For a few weeks now, the problem has also been occurring in an environment that I administer. So far noticeably only one user. Exchange Server 2016 and Outlook 2016 (Office Home and Business) in cache mode.
LG
Timbo
