Skip to main content

Sorry, Something went wrong - SharePoint Search Results

How many times have we seen this in SharePoint 2013!

I was working on custom search results page that had custom display templates. These display templates weren't complex and were almost similar to OOB templates.

Everything seemed fine, I was getting results based on my query and managed metadata settings. All looked well until users started hitting these search pages. They were greeted with the message "Sorry, something went wrong". Search refiners in the page was working fine but not the results webpart.

I had no clue what was going wrong. I tried ULS logs and found access denied error on the .js file that gets created part of the display template while logging in to the site as an end user with read access. I saw similar error in fidler while logging in to the site as an end user. Here are the errors I found using fiddler and IE dev toolbar:

"file was blocked due to mime type mismatch"

 "Access denied. Item does not exist. It may have been deleted by another user"

 The fact that users with administrator privilege could view search results without this error made me think about the custom results page being not published properly. I double checked and triple checked but the page was checked in and published.

I did remember that I had similar issues working with custom master pages with previous versions of SharePoint. With not much hope I navigated to the folder in master page gallery where SharePoint stores display templates through browser and published the .html file of my custom display template. That did the trick and now users could view search results.

That was strange because the file was not in unpublished state and still we had to publish it once!

Labels

Labels:

Comments

Anonymous said…
same problem, that is correct, save me the trouble thank you :)
May 13, 2014 at 7:30 PM
Anonymous said…
Too Good! Thanks much - saved me some trouble.
December 16, 2014 at 6:59 AM
Anonymous said…
Thank you soooooooo much dude!! it helped me.
December 30, 2014 at 3:25 PM
Anonymous said…
Thank you so much...perfect solution!
January 21, 2016 at 4:27 AM
Anonymous said…
Perfect solution...thanks!
January 21, 2016 at 4:27 AM
Post a Comment

Popular posts from this blog

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker: ...
Post a Comment
Read more

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Page layout HTML changes not reflected in associated aspx

I had this issue for quite sometime with a SharePoint Online project I was working on. I use Design Manager to create a new layout page and add snippets to the html layout. I would create webpart zones, add my webpart snippets on to the html, save and publish but the resulting aspx page wouldn't have any of my webparts in it. I checked it from SPD 2013 and everything looks perfect, I can see all the code snippets in there. It was really strange and I had no clues. I had some content search webparts in the layout and one content editor webpart with a link to a text file with some css in it. After countless hours on the internet I read about few other people having similar issues when they had custom css on the layout pages to hide quick launch. I tried removing my content editor webpart and everything seems to be normal. A new page created using the layout had all the webparts in it and even the layout preview was displaying fine. I needed this css somewhere on the page and ...
Post a Comment
Read more