SharePoint By Yagya Shree

Posts Tagged ‘search

SP2013: Find All search crawl Property

leave a comment »


Requirement:

How to find all search crawl property in a TEXT or EXCEL file for a specific site collection using PowerShell

 

Resolution:

1st Phase:

Find the GUID for site collection by running below script from Windows PowerShell ISE on any of the sharepoint servers in farm.

Add-PSSnapin “Microsoft.SharePoint.PowerShell”
$site = Get-SPSite https://sharepoint.contoso.com/sites/SP2013
$siteguid = $site.id
echo $siteguid

2nd Phase

Once you got the GUID for site collection from phase 1, run below script

Add-PSSnapin “Microsoft.SharePoint.PowerShell”
$searchapp = Get-SPEnterpriseSearchServiceApplication
Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -SiteCollection <Site_GUID> -limit All >C:\Temp\crawlproperty.csv

Advertisements

Written by Yagyashree

September 19, 2016 at 8:23 pm

SP2013: Search Error – HRESULT: 0x80131904

leave a comment »


ISSUE:

  • When we are trying to click on “Content Sources” OR “Crawl Logs” in our SharePoint 2013 Search service application. We are getting below error:

0x80131904

 

Troubleshooting:

  • ULS gave us below message on Application server:

ManagedSqlSession caught a SqlException executing the following command: ‘proc_MSS_CrawlAdmin’. Connection string was: ‘Data Source=SQL01\SQL01;Initial Catalog=Search_Admin_01;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15’ Original exception message: ‘A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)’ Stack trace ‘
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.Office.Server.Data.SqlSession.OpenConnection()
at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
at Microsoft.Office.Server.Search.ManagedSqlSession.ExecuteNonQuery()’ SQL Errors: Error ordinal: 1 Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified), Class: 20, Number: -1, State: 0

Resolution:

  • Issue was with one server which was hosting “Admin Component” in which event ID 6482
  • We restarted “SharePoint Server Search 15” on the server
  • All three options under Search administration page started working

 

 

Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Server
Date: 9/12/2016 1:09:04 PM
Event ID: 6482
Task Category: Shared Services
Level: Error
Keywords:
User: contoso/user1
Computer: APP1.contoso.com
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (9da9526d-52f0-4ab3-8bb6-7464872bdf04).

Reason: Exception from HRESULT: 0x80131904

Technical Support Details:
System.Runtime.InteropServices.COMException (0x80131904): Exception from HRESULT: 0x80131904
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

Written by Yagyashree

September 8, 2016 at 5:34 pm

SharePoint 2013: Search Service stuck at stopping

leave a comment »


Issue:

When we are trying to stop search services on one of the application server, we are getting below error and search service is stuck in stopping state:

1a

We also ran below PowerShell Commands to try.

PS C:\Users\SRV_SPProd_Setup> $sh = Get-SPServiceInstance -Identity “1738d18b-91
1d-4b27-ad6a-75919e3a485c”
PS C:\Users\SRV_SPProd_Setup> $sh.Unprovision()
Exception calling “Unprovision” with “0” argument(s):
“SharePointVideos.VisualSP.Utilities.LoggingService cannot be deserialized
because it does not have a public default constructor.”
At line:1 char:1
+ $sh.Unprovision()
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : MissingMethodException

1

 

Resolution:

While working on the issue, we looked and found that we had a DLL present for the solution in problem server i.e. SharePointVideos.VisualSP.dll

2

We checked other application server hosting search services but they did not had similar WSP present in GAC folder

3

We checked the Web Front End Servers and found a different version of DLL present.

4

We copied the SharePointVideos.VisualSP.dll from WFE server to problematic application server

5

After the copy, We ran following PowerShell commands to unprovision the search service instance

$sh = Get-SPServiceInstance -Identity “Search_Service_Instance_ID”

$sh.Unprovision()

6

Performed IISRESET on the server

Checked the Central Administration-System settings-Manage Service on server and the services were in stopped state.

7

Written by Yagyashree

February 11, 2016 at 7:59 pm

SharePoint 2013: How to remove search component

leave a comment »


Issue:

We are trying to remove a search component which is no longer required in Search service application.

Resolution:

We ran below powershell commands to remove the component from any application server:

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#To get component ID:
$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active

Get-SPEnterpriseSearchComponent -SearchTopology $clone

#To Remove Component ID:

Remove-SPEnterpriseSearchComponent -Identity 73caecca-2126-4a7d-b45c-2632a90d7109 -SearchTopology $clone -confirm:$false

#Activate the new search topology
Set-SPEnterpriseSearchTopology -Identity $clone

Written by Yagyashree

February 8, 2016 at 10:23 pm

Posted in sharepoint

Tagged with , , ,

SharePoint 2013 : Search Component Error

leave a comment »


BlogIssue:

While trying to create new “Content Processing Component” and activating the topology, we are getting below error:

02/08/2016 14:00:05.88 powershell_ise.exe (0x23E4) 0x1170 SharePoint Foundation PowerShell 6tf2 High Microsoft.Office.Server.Search.Administration.Topology.SearchTopologyActivationException: Topology activation failed. Service call AddNodeMapping failed with message ‘Exception while communicating with Host Controller at ServerName: No matching nodes found for the specified system and node name [SystemName = 9EB7B3, NodeName = ContentProcessingComponent3]’ at Microsoft.Office.Server.Search.Administration.Topology.SearchTopology.ActivateSilently() at Microsoft.Office.Server.Search.Administration.Topology.SearchTopology.Activate() at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord() 7c54cdb3-43ec-4736-ae7f-8fb1be49c252

Resolution:

The issue would be occurring on the particular server where you are provisioning the new component. Hence please do below steps on that particular server:

1. From services.msc on server, Restart “SharePoint Search Host Controller” Service
2. Within Services.msc stop “SharePoint Timer Service”

Assuming you default SharePoint installation location is C Drive, We are going to do config cache clear step i.e.

1. Open Windows explorer and go to C Drive
2. Locate C:\ProgramData\Microsoft\SharePoint\Config\GUID and make copy of GUID folder
3. Delete all the XML files inside the GUID folder except Cache.ini
4. Open Cache.ini and replace the current value with any random value.
5. Save the Cache.ini
6. Go to services.msc again and start “SharePoint Timer Service”
7. Wait for all the XML to generate and then match the generate XML count with any other server in farm

Now you should run below Powershell commands to provision your search component (PS. You can have your script)

##Creating all variables##
$hostA = Get-SPEnterpriseSearchServiceInstance -Identity “ServerName”
$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone -SearchTopology $active

##Creating new Content processing Component##
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance $hostA

Get-SPEnterpriseSearchComponent -SearchTopology $clone

##Setting up new topology##
Set-SPEnterpriseSearchTopology -Identity $clone

##Verifying the topology##
Get-SPEnterpriseSearchTopology -Active -SearchApplication $ssa

Written by Yagyashree

February 8, 2016 at 10:18 pm

WSS 3.0: When trying to search on sharepoint site, Getting message “No results matching your search were found.”

with 13 comments


1. Symptom –
=============

–>When you are trying to perform search on your SharePoint site  on your sharepoint server, you are getting following error message:

No results matching your search were found.
Check your spelling. Are the words in your query spelled correctly?
Try using synonyms. Maybe what you’re looking for uses slightly different words.
Make your search more general. Try more general terms in place of specific ones.
Try your search in a different scope. Different scopes can have different results.
 
–>Windows SharePoint help search is working fine and it gave results when we searched for “SharePoint”

–>Unable to get results on the SharePoint site

2. Cause –
==========

–>Issue due to windows Updates

3. Resolution –
================

–>We created a registry entry in the following location

HKLM\System\CurrentControlSet\Control\Lsa

–>Created a new DWORD key named “DisableLoopbackCheck” and modified the value to 1

–>We performed Full Crawl by the command

stsadm -o spsearch -action fullcrawlstart

–>We performed Search and it worked successfully

Written by Yagyashree

June 5, 2009 at 9:16 pm

Posted in sharepoint

Tagged with , , , , , , ,

unable to search content inside *.RTF [Rich Text Files]

leave a comment »


ISSUE DESCRIPTION
********************************
We have upload *.RTF [Rich Text File] files in you SharePoint document library http://sharepoint/yagya/test%20Library/Forms/AllItems.aspx
When we try to search for keywords like “alligator & applicable” which are inside the RTF files, no results are found.We are able to get results from Microsoft Word documents like *.doc and *.docx. A summary of the solution is detailed below.

SYMPTOMS
*****************************
We have upload *.RTF [Rich Text File] files in you SharePoint document library http://sharepoint/yagya/test%20Library/Forms/AllItems.aspx
When we try to search for keywords like “alligator & applicable” which are inside the RTF files,
you get following message

No results matching your search were found.
Check your spelling. Are the words in your query spelled correctly?
Try using synonyms. Maybe what you’re looking for uses slightly different words. Make your search more general. Try more general terms in place of specific ones. Try your search in a different scope. Different scopes can have different results.

We are able to get results from Microsoft Word documents like *.doc and *.docx

CAUSE
******************************
By default *.RTF [Rich Text Format] files are not searchable in SharePoint site as they cannot be crawled.

RESOLUTION
******************************
http://download.microsoft.com/download/SharePointPortalServer/Utility/1/NT5/EN-US/RTF.exe
1. Copy rtffilt.dll to C:\windows\System32 on the operating system drive of the SharePoint Server computer.
2. Register rtffilt.dll. – On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt. – Type Cd /d %windir%\system32 and then press ENTER to navigate to windows\System32 on the operating system drive. – Type regsvr32 rtffilt.dll and then press ENTER. – Click OK to close the message box. – Close Command Prompt.
3. Restart Office SharePoint Server Search and Windows SharePoint search service. – On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Services. – Right-click the service and then click Restart.
4. Add the .rtf extension to included file types, and start a full update. – Go to Central administration–Shared Services 1–Search settings–File Types – Click on New File Type and add “rtf” – On the Rules tab, click File Types. – Go to “Content sources and crawl schedules” and right click “Local Office SharePoint Server sites” and start a Full crawl
5. Wait for the crawl to complete

ADDITIONAL ARTICLES
********************************
– Rich Text Format File Content Is Not Indexed
http://support.microsoft.com/kb/291676

Written by Yagyashree

April 3, 2009 at 12:28 am

%d bloggers like this: