Forum Discussion
Sharepoint 2016 no search results.
mikjac21549 no proxy? A proxy should exist. You could try creating one using PowerShell
https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spenterprisesearchserviceapplicationproxy?view=sharepoint-ps
Alternatively, if you haven't configured your search service application a lot or you know exactly what you did you could as well recreate your search service application too. I wonder what way you provisioned your search service application. If you create one using Central Administration the proxy should be automatically created. If you used PowerShell you probably missed some steps...
mikjac21549are you sure the account you're performing your searches with (still) has permissions to the content that was crawled successfully?
I am not completely sure which account is performing the searching. How do I find that? How do I check it's permissions. There is a lot more that i don't know than what I do know about all this.
Thank you so much for your response
mikjac21549that account is just the account you're logged in with. In other words, are you able to browse to the content you're searching for?
yes I can open a list, look at an item, try to search for an item that I see, and it can't find it.
mikjac21549So you don't receive an error message after performing your search, just an empty results page? Is this the same when you search from inside the library/list instead of using the site wide search? Did you take a look at the logs on the server? (Event log, ULS log). Are you able to find other content that was not part of your migration?
Few more thoughts / hints:
- Does your Query Processing component show a green checkmark in Central Admin / Search Service Application Settings / Search Application Topology
- Are your searches being performed against the correct Result Source?
- Do you have any query rules configured that might have impact on your search results?
- Have you
- I assume you have only 1 Search Service Application configured in your Farm and it is associated to your Web Application via the correct Service Application Proxy group.