Solved

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

Posted on 2016-07-21
5
24 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 19

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 55

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 55

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 19

Expert Comment

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

Author Closing Comment

by:McKnife
ID: 41729216
Self solved.
0

Featured Post

Veeam gives away 10 full conference passes

Veeam is a VMworld 2017 US & Europe Platinum Sponsor. Enter the raffle to get the full conference pass. Pass includes the admission to all general and breakout sessions, VMware Hands-On Labs, Solutions Exchange, exclusive giveaways and the great VMworld Customer Appreciation Part

Question has a verified solution.

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

Last week I faced a strange issue recently, i have deployed SharePoint 2003 servers for one project and one of the requirements was to open SharePoint site from same server. when i was trying to open site from the same server i was getting authentic…
These days socially coordinated efforts have turned into a critical requirement for enterprises.
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…

636 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