Quantcast
Channel: SharePoint 2013 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 21070

Service service application state is stuck

$
0
0

Hi all,

Quick background on what I was trying to do here. I added the Search Service via the GUI, then later attempted to rename the DB's to match our naming standard. Used this doc: http://blogs.technet.com/b/wbaer/archive/2013/12/18/how-to-rename-search-service-application-databases-on-the-same-server.aspx

Had some issues where the SQL role for the search service and it's securables didn't come over with the backup, but I was able to restore those and it looked ok from there. However, I noticed from CA when viewing the crawl log, it was showing the name of the old Crawl database. I tried pausing the service, then removing the crawl database "remove-spEnterpriseSearchCrawlDatabase". That ended up removing the database from SQL, but the command just hung there a for a couple hours so I thought it was stuck. I cancelled it and restarted the server.

Now attempting to add a new DB "new-spEnterpriseSearchCrawlDatabase" yields the error:

"State 'AddCrawlStore' can't be set due to current application state 'RemovCrawlStore'."

The Search Administration screen says the status is "running", and under "Crawl Log > Databases" there are no DB's listed.

get-spEnterpriseSearchServiceApplication shows no CrawlStores now (was showing the old DB name).

get-spEnterpriseSearchCrawlDatabase retruns no database name.

This seems to be where I want it (everything is removed) except for the fact that I can't add back a new Crawl database.

Any thoughts or suggestions on how to clear up the service application state?

Thanks for any help.

Jared


Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>