Solved

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

Posted on 2016-07-21
5
22 Views
Last Modified: 2016-07-26
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
Comment
Question by:McKnife
  • 3
  • 2
5 Comments
 
LVL 17

Expert Comment

by:Walter Curtis
ID: 41723007
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
 
LVL 54

Author Comment

by:McKnife
ID: 41723299
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
 
LVL 54

Accepted Solution

by:
McKnife earned 0 total points
ID: 41723378
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
 
LVL 17

Expert Comment

by:Walter Curtis
ID: 41723386
Glad it is working for you
0
 
LVL 54

Author Closing Comment

by:McKnife
ID: 41729216
Self solved.
0

Featured Post

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Note:  There are two main ways to deploy InfoPath forms:  Server-side and directly through the SharePoint site.  Deploying a server-side InfoPath form means the form is approved by the Administrator, thus allowing greater functionality in the form. …
If you create your solutions on SharePoint sooner or later you will come upon a request to set  permissions of the item depending on some of the item's meta-data - the author, people assigned as approvers, divisions, categories etc. The most natu…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question