Outlook/Exchange 2016 Search: "Something went wrong and your search couldn't be completed."

Outlook/Exchange 2016 Search: "Something went wrong and your search couldn't be completed."

Since upgrading to Exchange 2016 we're seeing this a lot. It is intermittent, meaning occasionally the search will go through. I've tried rebuilding the index in Outlook but it has not helped, and I'm dealing with some frustrated users.
RISLAAsked:
Who is Participating?
 
RISLAConnect With a Mentor Author Commented:
I wound up purchasing ManageEngine's Exchange Reporter. Not perfect, but is giving me what I need for now.
0
 
Hasin Ahmed ChoudharyExchange AdministratorCommented:
Which CU of exchange 2016? Are complaining users on cached mode or online mode?

What are a version of Outlook and any recent update for outlook 2016?

Check if you are hitting few of known issue with security update of last year.
https://support.office.com/en-us/article/Outlook-known-issues-in-the-June-2017-security-updates-3f6dbffd-8505-492d-b19f-b3b89369ed9b?ui=en-US&rs=en-US&ad=US
https://social.technet.microsoft.com/Forums/ie/en-US/b8e24046-0bb1-4624-8ef7-6c268f2a6b13/something-went-wrong-and-your-search-couldnt-be-completed?forum=outlook
0
 
RISLAAuthor Commented:
We're on CU7, both users I checked today were on cached ex mode.

It seems to happen at random. However when one person can't search, I've noticed no one else can. On the same note, when someones search is working it seems as though everyone is working.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Hasin Ahmed ChoudharyExchange AdministratorCommented:
1)Point few of outlook client to one particular server using host file.
2) Increased event log level for search components.
3) Find any error at the time of issue occurrence.
1
 
RISLAAuthor Commented:
Thank you for all your help so far.

I'm seeing this Warning every 5 minutes. I couldn't find anything on Google, but maybe it means something to you?

Untitled.jpgUntitled.jpg
0
 
Michael meredithCommented:
Try switching off indexing for outlook from the control panel
0
 
RISLAAuthor Commented:
I did see that somewhere, but I don't have Outlook listed under Indexing Options

Untitled.jpg
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
Firstly are the problem mailboxes big by any chance? what size are they circa?
0
 
RISLAAuthor Commented:
The largest mailboxes are about 6GB, the average is 1-2.
0
 
RISLAAuthor Commented:
Updating the hosts file seems to have alleviated the issue, but I see this as a temporary fix.

Obviously this has something to do with DNS, but why would it work and fail seemingly at random?
0
 
Michael meredithCommented:
I have solved it for the moment by rebuilding the index, took a while but sorted it out.Let's see how long it will last
0
 
RISLAAuthor Commented:
Scratch that, the issue persists even with the modified hosts file. I've confirmed the hosts file still has the Exchange entry.
0
 
Michael meredithCommented:
I finally solved the issue by allowing Windows to re-index Outlook, and now everything is fine.
0
 
CCICTCommented:
I ran a re-index and it still gives me the same issue. I have Window 10 Pro, Office 2016 PP, and Exchange 2013. For me, it seems related to Windows 10, as the guys on my team run Windows 7, and they don't have any issues.
0
 
RISLAAuthor Commented:
3rd Party Software
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.