Howdy,

I have a custom master page that leverages a lot of CSOM/JSOM/REST. Unfortunately there seems to be a conflict when using the required MicrosoftAjax.js library in conjunction with Search Web Parts.

Symptoms:

Search results, search box and refiner added to a page - they render while in edit mode. When the page is saved/not in edit mode the web parts do not fully render (I can tell by analyzing the DOM for a default master page vs. custom). The page is blank.

When I remove the reference to MicrosoftAjax.js from my custom master page, then the search results work.

I also tried adding the reference to MicrosoftAjax.js to the OOTB seattle.html (master) and verified that doing so will also break the Search web parts.

Suggestions?

• Edited by Henry Ong Wednesday, February 11, 2015 6:11 AM

Hi Henry,

I downloaded js file from //ajax.aspnetcdn.com/ajax/4.0/1/MicrosoftAjax.js, and added reference to seattle master page. As I tested, content search web part is not working. After remove the reference from master page, it works.

Then I searched on the Internet, here is a similar issue:

http://sharepoint.stackexchange.com/questions/123124/content-search-web-part-not-displaying-results

Could you please consider using JQueryAjax to replace this one? For your reference:

http://api.jquery.com/jquery.ajax/

If there is some function needed while you couldn't find in JQueryAjax file, let me know, I will try to be help as possible.

Regards,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

FYI, I'm still working with MSFT Support via a case to resolve this issue. I'll follow up later with the results.