Internal Server Exception Error SharePoint 2010 Search

Users complained that they are getting  : Internal Server Exception Error  whenever they search on a SharePoint Portal.

This error occurs only on the very first search , when the page is refreshed search results appear normally.



Explanation : As the Search Functionality whenever a user searched with their query in the search box the query hits the WFE  and from the WFE the request will be processed to the server on which the Search Query and site settings service is configured (Started).

Analysis : After looking into the below logs I searched for the above mentioned service (Search Query and site settings service is configured (Started). on all the servers but this error logs were found only 1 server and this is a WFE. It is marked in bold below.

The search is not configured on this server , however I noticed that the service for Search Query and site settings service is started on this WFE. So Ideally this service should be running only on the servers where Search has been configured or where indexing or query components exist.

Hence I went ahead and stopped the Search Query and site settings service .

Now this was permanent fix for the error. But stop the service only during off  business hours to avoid any risk .

Event Viewer Logs : 

SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
Process Name: w3wp
Process ID: 10120
AppDomain Name: /LM/W3SVC/1000845466/ROOT-1-130697290206383020
AppDomain ID: 2
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:d9cf9af2e36e4da396faf0089959ebb3#authority=urn:uuid:dcaec3c122874a9998af4b9eef5a2eb4&authority=https://sv42080oel1191:32844/Topology/topology.svc
Active Endpoints: 2
Failed Endpoints:1
Affected Endpoint: http://sv42080oel1226:32843/d9cf9af2e36e4da396faf0089959ebb3/SearchService.svc

Comments

Post a Comment

Popular posts from this blog

Migrate Secure Store Service Application from SharePoint 2013 to SharePoint 2016

Image
Migrate Secure Store Service Application Whenever we migrate SharePoint from one version to the next version , we recreate most of the service applications. However, in few cases where we have dependencies  with service applications like secure store and Managed metadata service which may have several credentials and term stores. recreating all the service IDs may be a tedious job and can easily land us in to issues. Hence, it is recommended to upgrade the Secure store service application.  Title: Steps to Migrate Secure Store Service Application from SharePoint 2013 to 2016 In on of my SharePoint Migration Projects from SharePoint 2013 to SharePoint 2016  Secure Store Service Application was one of the critical services used by the customer due to its dependency with Data Refresh Jobs from SSAS.  This article is a step by step approach to migrate Secure Store from SP 2013 to SP2016. Steps: Identify the Secure store database used in the SharePoint 2013 Database and restore a copy to th
Read more

Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm.

Image
Unable to start Secure Store Service : Error : Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm. Solution : Delete the Secure Store Service Application. Close all the browsers and runt the sharePoint Configuration wizard and retry to configure the secure store service and the issue should be fixed. If the issue still persists , start the Secure Store Service Application using the following commands. $proxy = Get-SPServiceApplicationProxy | where {$_.TypeName -eq "Secure Store Service Application Proxy"} $proxy.Status = "Online" $proxy.Update() In few cases it may happen that the Proxy service may start and the secure store service still has an error.In this case please delete the Secure Store service  and recreate using PowerShell as below : $sa = New-SPSecureStoreServiceApplication -Name "Secure Store Service Applicatio
Read more

HTTP 403 Forbidden SharePoint 2013

Image
Today  I faced an Issue in SharePoint where I got the error :"HTTP 403 Forbidden" for any site collection under a Web Application and this problem existed on Central Admin. Error : HTTP 403 Forbidden This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage. This problem occured after I tried configuring the SSL certificate for Central admin and the other Web Application. In this attempt I managed to Crash my SharePoint Farm. I have tried accessing the site from IIS with no go. Did Run the SharePoint Configuration Wizard successfully. Tried accessing the Central Administration Page with no go :( Resolution: After Trying the above options which did not work , finally I have deleted the Central Administration site from IIS. Run the SharePoint Products Configuration Wizard again and the Central Administration site has  been recreated. Launched Ce
Read more