Unable to create a Search Service Application - "Errors were encountered during the configuration of the Search Application"

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 serve search queries
Id : 4da7eac7-95ce-4a69-bfd2-910f023aed7c
Server : SPServer Name=GmallyaSP
Service : SearchService Name=OSearch14
Role : None
QueryComponents : {}
CrawlComponents : {}
AdminComponents : {}
Status : Disabled

* Starting the service instance using the powershel gives an error

start-SPEnterpriseSearchServiceInstance -id $ssa

ERROR:

Start-SPEnterpriseSearchServiceInstance : Service is offline
At line:1 char:40
+ start-SPEnterpriseSearchServiceInstance <<<< -id $ssa
+ CategoryInfo : InvalidData: (Microsoft.Offic...ServiceInstance:StartSearchServiceInstance) [Start-SPEnterpriseSearchServiceInstance], InvalidOperationException
+ FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.StartSearchServiceInstance

* Check the status of the service -

Get-SPEnterpriseSearchService

RESULTS:

TypeName : SharePoint Server Search
Id : 8f86556d-f84c-4253-bebb-33512b77bc5a
ServiceName : OSearch14
ProcessIdentity : AD-ENT\isgssp2010
ContactEmail : <xyz@gmail.com>
Applications : {}
PerformanceLevel : PartlyReduced
Status : Disabled
Following are the Powershell to get the service online:
•Start the search service
$sa=Get-SPEnterpriseSearchService
$sa.Status=0
$sa.update()
$sa=Get-SPEnterpriseSearchService

Get-SPEnterpriseSearchService

RESULTS:

TypeName : SharePoint Server Search
Id : 8f86556d-f84c-4253-bebb-33512b77bc5a
ServiceName : OSearch14
ProcessIdentity : AD-ENT\isgssp2010
ContactEmail : <xyz@gmail.com>
Applications : {}
PerformanceLevel : PartlyReduced
Status : Online

* Now start the search service instance

$ssa=Get-SPEnterpriseSearchserviceinstance -local
$ssa.status=0
$ssa.update()
$ssa

RESULTS:

TypeName : SharePoint Server Search
Description : Index content and serve search queries
Id : 4da7eac7-95ce-4a69-bfd2-910f023aed7c
Server : SPServer Name=ISG-DAGOR
Service : SearchService Name=OSearch14
Role : None
QueryComponents : {}
CrawlComponents : {}
AdminComponents : {}
Status : Online

* Now create a search service application.

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013 and InfoPath 2013 - Creating Web Enabled Forms

Image
In this article, you will learn how to create web enabled InfoPath forms. InfoPath is an information gathering tool and is used to create XML forms. People have always been trying to come up with a standard for creating electronic forms. Before InfoPath, companies created electronic forms in different formats. InfoPath has helped companies to adhere to a standard. Coding XML manually may not be an interesting job but creating XML forms with InfoPath has really made this job quite easier. All clients must have InfoPath installed on their machines in order to open the forms. It could be a problem for smaller companies to provide InfoPath client to all the users. What can be the solution then? Solution is to create web enabled forms that can be opened in web browser without having to install InfoPath client on user machines. Following is a step-by-step guide that will show you how to create and deploy a web enabled form: 1.Open InfoPath (Start > All Programs > Microsoft Offic...
Continue Read

"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

MORE CACHE HOSTS ARE RUNNING IN THIS DEPLOYMENT THAN ARE REGISTERED WITH SHAREPOINT

Image
So, I’ve just installed SharePoint Foundation 2013 on a clean Windows 2012 server yet the Health Analyzer is complaining about a few things.  I’ll work my way through fixing them and the first one I’ll tackle is “More Cache hosts are running in this deployment than are registered with SharePoint”. The clue for fixing this one is in the explanation: “This operation uses the SharePoint Administration service (spadminV4), which could not be contacted”.  I don’t know why this is stopped by default but starting the service (and setting it to automatic) has stopped this being flagged as a problem. More details of the Windows Server AppFabric Caching features can be found here: http://msdn.microsoft.com/en-us/library/ff383731(v=azure.10).aspx
Continue Read