SharePoint 2013 Search Service application - Unable to create after deleting a corrupted one

Question

Server details:

• Multi server SharePoint Farm 2013
• 1 APP and 1 WFE
• Search was installed on App previously
• Search was corrupted, tried below option before deleting SSA.

a. Cleared Config cache and reset the value to 1
b. Stop and Start Timer service on both servers,
c. Index reset, Ran Full crawls It did not work.... In process of re-creating SP13 search service application.

I followed below post https://social.technet.microsoft.com/wiki/contents/articles/48051.sharepoint-2013-how-to-completely-remove-search-service-application.aspx

I end up deleting search service related content from this default index path C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search\Nodes\5CDD35. (Unfortunately I haven't made a back up of search content from the above path)

Error details - Sorry Something Went Wrong - Object reference is not set to reference of an object.

Now I'm unable to create new search service application using central admin

CA > Application Management > Mange Service Applications > New on top left > Search service application.

I was able to create using a PS script found online, but it is not creating any databases on SQL server as well as unable to create 5 components of SSA

Crawl Component.
Content processing component.
Indexing component.
Query processing component.
Analytics processing component.
Search administration component.

Ended up deleting SSA again as it stuck on error.

Any help is much appreciated, I've spent immense time on this and posting here as a last option.
Please let me know if you need further information.

Thanks,
Hari

Answer 1

@harikiran pallerla

First, please use Get-SPServiceApplication to check whether there is search service application in the server.

If there’s search service application in the server, please use below command to remove it.

$SSA = Get-SPServiceApplication -identity "GUIDRetrievedAbove"  
Remove-SPServiceApplication $SSA  

You could try to run SharePoint 2013 Configuration Wizard to fix this issue.

And check ULS logs to find more clues.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

just to check: did you try to restart app and wfe servers?