Search not working – Query component failed status

Hi all!

I still don’t know if it’s related or not, but after changing the time in our UTC zone, all the query search in a SharePoint farm suddenly stopped working.

At the beginning with the errors that I had, I was thinking in the Index component, but when I accessed to the components, I was able to see that the query component was in red, so it was the first indicator that something was not working fine.

My first thought was to check the logs to see If was able to see anything, and in fact I found a lot of errors related with the query component, some of them like the following:

SearchServiceApplicationProxy::Execute–Error occured: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Tried IMS endpoints for operation Execute: Operation sent to IMS failed: Resource saturation, try again later. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: Microsoft.SharePoint.SPException: Tried IMS endpoints for operation Execute: Operation sent to IMS failed: Resource saturation, try again later. at
WcfSendRequest: RemoteAddress: ‘net.tcp://servername/97C247/QueryProcessingComponent1/ImsQueryInternal’ Channel: ‘Microsoft.Office.Server.Search.Query.IImsService’ Action: ‘’ MessageId: ‘urn:uuid:86db249c-bb2a-427f-bbbb-219f0d00e87c’ f861b39d-b40f-b033-363b-cc73f6b053c4
Ims::Execute–Error occured: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://servername/97C247/QueryProcessingComponent1/ImsQueryInternal that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Server stack trace: at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) at

So… at the beginning I was thinking what can I do with this errors? My first thought was to check available disk free space.

Everything was fine, so.. next thing to check, the following thing I checked was the SharePoint cache, everything was fine, but just in case I cleaned SharePoint cache, then I checked the components of Search and was still in red, so the problem started to be big.

But, suddenly It pops out of my mind that something in the logs, so my next move was to restart the search services. In first case the host controller service. I restarted the service, once it was restarted I checked again the components and were all in green. Yihaaa!

I checked the search results on the portal and I was able to perform queries and all the WP configured were working.

I stopped investigating what was the root cause of the problem, but for next time I know what to do first.

Till nex time!


How to disable IPv6 with Powershell

In some scenarios, working with IPv6 causes a lot of issues, because the request is made to IPv6 rather than IPv4, so the DNS lookup just fails. Typically, IPv6 is not deployed but if you’re in the same boat as me, do the following:

New-ItemProperty -Path HKLM:SYSTEMCurrentControlSetservicesTCPIP6Parameters -Name DisabledComponents -PropertyType DWord -Value 0xffffffff
Restart-Computer -ComputerName $env:computername -Force

And that’s all!

The search application “SEARCH SERVICE APPLICATION” on server did not finish loading

Hi folks,

Recently, I came across with the following issue, I Opened the Search Service Application in one of the Servers in the farm, and when I click on Content Sources I was getting:

The search application ‘XXXX’ on server XXXX did not finish loading. View the event logs on the affected server for more information.

After spending some time to fix the problem I found the following command:

Psconfig -cmd secureresources


It takes a couple of minutes to finish it.After doing this I was able to enter again to Content Sources in the Search Application

Hope it helps!


SharePoint Apps: “Sorry, something went wrong with adding the app. Click to retry.”

I was configuring a dev onpremises farm in SharePoint 2013 to support apps, I followed the guide in

But, everytime I tried to add the app to a site I received thhe following error:

“Sorry, something went wrong with adding the app. Click to retry.”

The first thing I did, it was an iisreset, but that didn’t work, so I started to figure out what was happening at all. Suddenly I remembered that the SPTimer Service would need to be restarted.

Once I did this, it started working like a charm. So, take into account that any change on SharePoint configuration, will be very smart to restar the SpTimer service.

Hope this helps someone out there getting the same error… if you are sure you did everything right in the configuration – you might actually be correct! Just remember to restart services for them to pick up your changes…

Microsoft .NET Framework to disable RC4 in Transport Layer Security installation error

Hi All!

During a fresh installation of a SharePoint 2016 farm I encountered this error, I was installing all the prerequisites, I rebooted the server when it demanded, but when I continued with the installation I faced the following error message:

Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850): installation error

The error patch description is “A security issue has been identified that could allow an unauthenticated remote attacker to compromise your system and gain access to information”

So you can download the security patch from Microsoft Download Center through this URL

Install by hand this update and try another time to check all the prerequisites in the SharePoint farm. After that I was able to continue with my new installation os SharePoint 2016.

Hope it helps!

Site Collection stuck in Read Only mode

Hello everybody,

I was doing a backup-spsite but I interrupted it during the process, after doing this I get a pretty message in the site collection that was in Read Only mode.

$site =Get-SPSite -Identity http://xxx


Set-SPSite -Identity “http://xxx” -LockState “Unlock”

stsadm -o setsitelock -url http://xxx -lock none

But unfortunately was not possible to unlock the state of the site collection. Hopefully I found the following PS that did the trick:

$Admin =  new-object Microsoft.SharePoint.Administration.SPSiteAdministration(“http://xxx”)

After that, my site collection is not read-only any more

Till next time!

RecordsManagement.Preservation.PreservationJobDefinition threw an exception

While crawling in SharePoint 2013, I got an error below:

“The Execute method of job definition Microsoft.Office.RecordsManagement.Preservation.PreservationJobDefinition threw an exception. More information is included below.

The search request was unable to connect to the Search Service.”

To resolve above issue, please follow steps below:

  • Navigate to SharePoint 2013 Central Administration >> Monitoring >> Review Job Definition
  • Select All from drop down
  • Find eDiscovery In-Place Hold Processing timer job. Click on it.
  • Click on Disable

hope it helps!

SharePoint 2013 Setup error if the .NET Framework 4.6 is installed

This happened to me in a customer installation, during the installation, the installer verifies if .Net Framework 4.5 is available and fails to install SharePoint if Framework 4.6 is installed.

First think that you would think is: I did not install .Net Framework 4.6… but you have to be aware that this version is included in a Windows Update, so we need to uninstall this Windows Update to be able to install SharePoint.

But before uninstalling :net 4.6 or 4.6.1 we can verify which version we are using, to do this we can use the .NET Framework Setup Verification Utility and confirm which version is installed.

Then, what we need to do is to search one of the following updates and uninstall it:

  • On Windows 7 SP1 and Windows Server 2008 R2 SP1, the Microsoft.NET Framework 4.6.1 is listed as an installed product under the Programs and Features item in Control Panel.
  • On Windows 8 and Windows Server 2012, it’s listed as Update for Microsoft Windows (KB3102439) under theInstalled Updates item in Control Panel.
  • On Windows 8.1 and Windows Server 2012 R2, it’s listed as Update for Microsoft Windows (KB3102467) under the Installed Updates item in Control Panel.
  • On Windows 10, it’s listed as Update for Microsoft Windows (KB3102495) under the Installed Updates item in Control Panel.

Once uninstalled the update, will be necessary to restart the server in order to apply the changes. After the server has been rebooted it is possible to start the SharePoint installation process again.

Hope it helps!

Related info:–visual-studio-2015-with.aspx


Product / patch installation or server upgrade required

Hi folks,

Recently I had a problem in a farm I was deploying, everything was fine, but when I tried to see “servers in this farm” option I could see that one of the servers has the state as “Upgrade Required”. At first instance I thought, ok I have installed the same CU in all the servers, but in this one I am having some problems, I will try to reboot the server and check it again.

So, I rebooted the server and I checked it again, for my surprise, it was stuck in the same state as before. So, I tried the next option, run the SharePoint configuration wizard. I run the configuration wizard, and it showed an error while upgrading the server… the thing started to become weird… I checked the log file, expecting to find something that points me with the solution, but nothing…

Thus, I fired my next bullet which was PowerShell, I opened the shell and executed the following: Get-SpProduct -local expecting that probably it will show me that a CU or LP was missing or something like that, but still no luck 😦

I tried by PS and I was receiving the following error:

“An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown.  Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20160429-101200-949 was updated by MYDOMAINspinstall, in the PSCONFIG (3540) process, on machine SERVER1.  View the tracing log for more information about the conflict.”

So, what was happening? I tried my last chance which was to clean the SharePoint cache and try another time with PS. So I clean the cache (if yo don’t know how to do it, I have a post about it), and then I run the following:

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

So, what happened?? It worked! So, I was able to continue with my work, and forget the evening that I spent to solve this problem.
Till the next time!!

Request was rejected by the HTTP filter

Recenlty a client had published a SharePoint site through TMG.  Everything looked great until you went to view/edit the properties of a document in a document library.  I got the following error:

“Error Code: 500 Internal Server Error. The request was rejected by the HTTP filter. Contact the server administrator. (12217) ”


Trying the same actions on any other list/library worked fine; just not for a document library.

The problem turned out to be related to HTTP filtering in TMG.

To fix the issue, Open the properties of the firewall policy.  Click Filtering > Configure HTTPunder the Traffic tab.


Uncheck Verify normalization.


Save and apply changes and you should be all set.

But in case your problem is related with the people picker you should uncheck the value “Block high bit characters.”  This will fix the problem. This problem also happens when you publish the OWA urls thorugh TMG or ISA

Hope that helps!