Query-0 Server Not Responding - Event ID 2587

Error :

SERVER1:

 Windows 2008 R2 (x64)
SharePoint 2010

SERVER2:

 Windows 2008 R2 (x64)
SQL 2008

Services running on SERVER1: (none as localsystem, localservice, networkservice)

SharePoint 2010 Administration (started/auto)
SharePoint 2010 Timer (started/auto)
SharePoint 2010 Tracing (started/auto)
SharePoint 2010 User Code Host (stopped/disabled)
SharePoint 2010 VSS Writer (stopped/manual)
SharePoint Foundation Search V4 (started/manual)
SharePoint Server Search 14 (started/manual)

The RELATED ISSUE(s):

 Search/indexing is not working, and in return, backups are failing claiming:
Failure Message Object Query-0 (D: on SERVER1) failed in event On Backup

Search Service Application reports:

Index Partition - 0 - SERVER2\Search_Service_Application_PropertyStoreDB_9a482efd99954748a062952a3d2617d7
Query Component 0 SERVER1 Not Responding

System Event Log on SERVER1 reports:

Event ID 2587
The following conditions are currently affecting index propagation to this server for search service application 'Search Service Application':
1. Query 0, catalog Main: failing to copy index files from crawl component 0 for 1490 minutes. Access is denied.   0x80070005
2. Query 0 is not being automatically disabled because the minimum number of ready query components per partition is 2.

Solution :

1. Please try to disconnect the query server from the search topology,
2. stop the Search service in central admin, clear the index files in the query server. 
3. After that, starts the search service instance using Start-SPServiceInstance PowerShell.


Run the following PowerShell to reset the Query server:

$ssa =  Get-SPEnterpriseSearchServiceApplication -Identity "SSAName"
$queryComponents = $ssa | Get-SPEnterpriseSearchQueryTopology -Active | Get-SPEnterpriseSearchQueryComponent
$component = $queryComponents | where {$_.ServerName -eq "QueryServerName" }
$component.Recover()

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read