If your Outlook returns a yellow box saying “Something went wrong and your search couldn’t be completed” the most likely issue is your Windows Search Service is damaged. Show
You can verify this in two ways:
To fix this problem you should RIGHT click on the WINDOWS SEARCH service and select START. In the unlikely event that works, you are done, but most likely you will need to flush an rebuild the Windows Search service. The fastest way to solve this is to delete the Windows Search Service data and have it rebuild from scratch.
As this point all search indexes have been removed and will take time to rebuild. Outlook, in particular, will only rebuild it’s index when it is running so make sure you leave Outlook up for a few hours. You can tell it is working because when you do a search in Outlook it will have a ‘we’re indexing right now, try again later’ type message and not the yellow bar ‘Something Went Wrong…’ message. If you are adventurous you can also try to force the start from the command line. If the Search Service has corrupted data, you will see SERVICE SPECIFIC ERROR 2147750271 if you try to start the WINDOWS SEARCH service from a CMD line (NET START “WINDOWS SEARCH”). This can be a tedious process if you are just trying to complete homework and need to find some old content. Some will give up and same it is DomyEssay for me . So you have a new computer, setting up a fresh copy of Office, and you go to login to the users email for the first time and get this lovely little error: “Something went wrong” Whats most frustrating about this for me is, each time I had it happen it was with a user account that was getting a new computer, but had been working perfectly fine on the old system prior. I had come across a lot of suggested fixes that may work, but didn’t resolve my issue: Resolution 1 (Didn’t work for me) : Make sure office and windows are up-to-date. Resolution 2 (Didn’t work for me) : Disable IPV6 ( tools for disabling ipv6 here ) Resolution 3 (Didn’t work for me) : Try the 64 bit version of the installer Resolution 4 (WORKED FOR ME!) : So – in my case, it turns out there were some DNS entry records that dissipated (thanks 3rd party web guy!) that messed up auto discovery. This resolution includes a diagnostic step, a permanent fix, and a work around to get your user up and running on mail fast. Step 1 : Check if DNS is broken. Use the microsoft tools and these instructions to diagnose your DNS and make any recommended changes : https://support.microsoft.com/en-us/help/2776497/the-office-365-dns-diagnostic-and-dns-configuration Step 2 : Registry edits, this will get your user up and running right now without waiting for your DNS changes to take effect – editing your registry is dangerous, if your not sure of what your doing – talk to a pro. </disclaimer> Open regedit as an Administrator and add the following registry keys (All are 32 bit DWORD’s with a value of 1) You might see this error if your primary alias's name is the same as an existing work or school account in Microsoft 365 or Azure Active directory. To resolve this error, try any of these steps: Rename your account to something elseChanging the name of your account might fix the issue.
For more information on how to do this, go to Rename your personal account. Set one of your other aliases as the primary aliasIf you have more than one alias, try setting another alias as the primary alias.
For more information on how to do this, go to Manage aliases on your Microsoft account. Add another alias to your account and make it the primary aliasIf you have only one alias, or your other aliases don't work, try adding another alias to your account and making it the primary alias. Note: You cannot add an alias that is already associated with another Microsoft account. Aliases cannot be used to share information between two Microsoft accounts. Existing @hotmail.com, @live.com, @outlook.com, and @msn.com addresses can't be added as aliases.
|