SharePointSupport

What is iFilter ? * IFilters are components that allow SharePoint to index content of specific file types, letting users to search for content in those files. * Using the SharePoint Search we can find documents based on their filename, metadata or content within a document. * By default the content of Office documents is indexed by the SharePoint crawler, but PDF files are not crawled. * To add support for PDF files you have to add an I-Filter which the SharePoint crawler uses to read through PDF files and add the information to the search index. There are two steps in configuring PDF Search IFilters for SharePoint 1.       Install the PDF iFilter 2.       Configure the iFilter Installing IFilter The Installation of the iFilter 9.0 has to be done on the Index Server(s) How to install ifilter in SharePoint 2010? Download  and install the iFilter installation file for 64-bit machine from http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025 Cho

Issue: Unable to add user properties for user profile connection. Getting Unable to process Create message error in the event log and ULS logs. Error’s in the event log and ULS Logs: OWSTIMER.EXE (0x075C)            0x0DD4 SharePoint Portal Server User Profiles      9q17     High            UserProfileApplication.SynchronizeMIIS: Failed to configure ILM MA, will attempt during next rerun. Exception: Microsoft.ResourceManagement.WebServices.Faults.ServiceFaultException: Unable to process Put message     at Microsoft.ResourceManagement.WebServices.Client.Resource.Update()     at Microsoft.ResourceManagement.WebServices.ResourceManager.UpdateResource()     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMMAConfiguration. UpdateSQLConnectionInformation(String server, String databaseName, String user, String domain, SecureString password)     at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.UpdateILMMA(String databaseServerIlm, String da

Managed properties are metadata that can be searched or used in other ways, such displaying data in search results. The default index schema provides a set of mappings from crawled properties to managed properties . The default mappings are adapted to common content formats when crawling using the Content SSA. Specific content sources or other indexing connectors can expose other crawled properties that have better quality for your content. You can associate a managed property with one or more full-text indexes . You must use a full-text index to achieve ranked results for queries. You can enable Query Refinement for a managed property so that you can add the data from this property as a drill-down option on the query result page. You can configure a hit highlighted summary for a managed property. This is a summary of a managed property that appears on the search results page for each query result. The summary displays an excerpt from the item that contains the query text

Crawled properties are metadata that is extracted from content sources to make the data available for searching. Crawled properties are typically reported by the Content SSA or other FAST Search Server 2010 for SharePoint connectors, but can also be created during item processing by an IFilter or a property extractor . A crawled property is uniquely defined by the parameters of Name , Propset , and VariantType . Two specific managed properties are populated with the crawled property names and values discovered for the given item, as follows: crawledpropertynames   Holds discovered crawled properties that have a value for a specified item. crawledpropertiescontent   Holds the value of every crawled property in crawledpropertynames . Some discovered crawled properties are not mapped into these managed properties. The disadvantage of automatically indexing the content of discovered crawled properties is that not all content is relevant for searching. There may be several reas

What needs to be done? 14 steps for a simple Search Topology – 1 powershell can do them all. 1.Create a Service Application Pool for the Search Service Application (15-22) 2.Create a Search Service Application (22-28) 3.Create a Search Service Application Proxy (30-36) 4.Get the current Search Instance (38) 5.Save the current Search Topology for later use (39) 6.Create a new Search Topology (40) 7.Create all the Search Components (Analytics- , Content Processing, Query Processing, Crawler-, Admin Component) (42-46) 8.Remove the Index-Folder and recreate it (50-51) 9.Create a new Index Component (53) 10.Activate the new Topology (56) 11.Call the method synchronize on the old topology – this errors but forces an update on the old topology object (59) 12.The “forced updated” Topology object becomes inactive and can be deleted. (62) 13.Everything  done – start a full crawl order set it to the new shiny continuous crawling. Enjoy! Here is my powershell script for creati

In this blog post, I would write about most generic issue in SharePoint 2010 search service application and I am sure many of you have already come across this: In SharePoint 2010 - When you try to browse to a Search Service Application (SSA), it shows he below error: "System Status: Crawl: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component c8519b74 status -<GUID> in search application Search Service Application is in a good state and try again." Additionally, you should see below errors in the Event logs: "Description: The Execute method of job definition Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition (ID 6dd22d5b-45cb-4860-aa01-d7f7d227a2f6) threw an exception. More information is included below. The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '9e

ISSUE Error when creating the search service application- Errors were encountered during the configuration of the Search Application" CAUSE * We see the following in the ULS logs When the search service application creation fails * The call to SearchServiceInstance.Provision (server 'GmallyaSP') failed. Setting back to previous status 'Disabled'. System.InvalidOperationException: Service is offline at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Provision() at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.DeployLocalServiceInstance[T](T localSearchServiceInstance) RESOLUTION * Use the PowerShell commandlets to bring the search service online. Following are the PowerShell commandlets I used to resolve to verify the status of the service and then bring the service instance online: $ssa= Get-SPEnterpriseSearchServiceInstance -local $ssa RESULTS: TypeName : SharePoint Server Search Description : Index content and

If your Usage and Health Data Collection Proxy is in a stopped state here is a quick bit of PowerShell to to get it started: $sap = Get-SPServiceApplicationProxy | where-object {$_.TypeName -eq “Usage and Health Data Collection Proxy”} $sap.Provision() The above can easily be adapted to allow you to start any Service Application Proxy. Video: service application proxy sharepoint