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:

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

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
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

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it. No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account . I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way. I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error! " Cannot perform this operation. The file is no longer checked out or has been deleted ." I had no clue what was happening...
10 comments
Read more