Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 29
  • Last Modified:

Sharepoint 2016 - different search results depending on who searches - all have same permissions

Hi experts.

We setup sharepoint 2016 trial. The enterprise search center works as expected - for anyone. The search box of the project site however, does return results only for some users. So the same documents are not found, only for some users.
There is no logical explanation to me. All users are allowed to view these documents, so search should find them as well. This effect is not seen on another sharepoint test machine that the same people have setup.

We searched the net and found people with this problem who claimed, their solution was to change permissions on that problem user's AD object, which we tested, but no success.

Any idea?
0
McKnife
Asked:
McKnife
  • 3
  • 2
1 Solution
 
Walter CurtisSharePoint AEDCommented:
Maybe this will help. A few things to look at:
  • Double check permissions again, down to the document level. Maybe the document has unique permissions and some users aren't allowed access. In that case, SharePoint security is doing what it is suppose to do.
  • Have permissions recently changed? Changes to the search index's ACL are not indexed until the next full crawl. A full crawl may correct the issue.
  • In some cases, search results are set to filter what it thinks are duplicates and this will "hide" documents sometimes. The setting to change that is a property of the search results web part found on the search results page.
  • Are documents checked in and/or published. Only owners will see documents in their draft version.

Hope that helps...
0
 
McKnifeAuthor Commented:
Hi. None of those apply
All users have permission to read it and a new crawl was already done. The search center find those, only the search box at the site level does not. No draft status, no duplicates.
0
 
McKnifeAuthor Commented:
Found the problem. The developer who tests used the fqdn. Without the full name, it works everywhere. We'll find out, why that is.
0
 
Walter CurtisSharePoint AEDCommented:
Glad it is working for you
0
 
McKnifeAuthor Commented:
Self solved.
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.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now