Saturday, February 06, 2016

How to Delete a Service Application Database that is Not Responding

Posted in SharePoint, Technical By Doug Allen @ 1/29/2013

powershell_iconOn a recent project, I hit an issue with databases that was interesting.  We were restoring a lot of databases over to a development environment from production, as well as the managed metadata database.  I had gone through the whole deal, backed up the database in the old server, restored it to the development SQL server, etc.  There was an issue with the Managed Metadata service that required to have service application re-created.  This lead to a situation where the service application database was unprovisioned, but not deleted. 

What first caught my attention was the errors in the ULS log.  I was getting a SQL “login failed” for that database which I thought was strange as I thought the database had been deleted when the old service application was deleted. This wasn’t the case.  To see the status of all the databases, go in Central Administration, click Upgrade and Migration –> Review database status.

SharePoint database not responding

Normally you see all the databases as no action required, but our database shows Not Responding.  What does that mean?  If you remember, we got in this scenario because when we deleted the service application, it didn’t fully remove the database. It unprovisioned the database, but failed to remove the entry for the database from the configuration database, which leaves the database as Not Responding. So all we need to do at this point is delete the entry from the config database. 

So how do we get rid of the database?  In our example, we’re dealing with a service application database.  Fire up our trusty friend PowerShell.  The following will show all service application databases:

Get-SPDatabase | where {$_.Type -notcontains "Content Database" -and `
$_.Type -notcontains "Configuration Database"} | sort Type | format-table –autosize

From the output, get the GUID of the our problematic database.  Then run:

$db2delete = Get-SPDatabase “GUID”

This just verifies we have the object correctly.  Once we verify this, we can get rid of it.  Before we delete it, let’s check it’s status:


A normal database will show Online.  The status property on a database object uses an SPObjectStatus value.  You can see all of the available statuses, with the exception noted when in the context of the SPContentDatabase object.  Now let’s delete it.  Run the following:


Done!  Note, this will not delete the actual database in SQL, just removes the entry in the Config DB. 

, , , , , , ,


Got something to say? Join the discussion »
    Posted by Doug Allen on 10/1/2015
    Tom, thanks for pointing that out and yes Get-SPDatabase will get all databases. That is what I'm doing as see in the command, I'm just putting some filters on it to just the service app databases. But they aren't necessary. Glad it was helpful!

    Posted by tom on 9/30/2015
    Get-SPDatabase alone will return the GUID's.

    Other than that, this article really helped me out.
    Posted by skrasher on 9/30/2013
    Thanks! I had an orphaned State Service DB that was 'Not Responding' when I checked in Central Admin. The service app was deleted, and the DB was not there in SQL, but it remained there and caused errors when upgrading (Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException). Removing it this way fixed it and things are clean again.
    Posted by Goran Husman on 5/21/2013
    Excellent article - Exactly what I was looking for!
    Office 365 MVP
    Posted by Dimitri C. on 5/16/2013
    This solved my issue, thanks !

leave a reply

 [Quick Submit with Ctrl+Enter]

Remember my details
Notify me of followup comments via e-mail


About C5 Insight

We are a Microsoft Gold Certified partner focusing on SharePoint, Microsoft Dynamics CRM and  Learn more about us by visiting our website.

We Wrote the Bible on Microsoft SharePoint and Dynamics CRMBook-Microsoft Dynamics CRM 2011 and SharePoint 2010 Bible

Upcoming Events

Comparing Salesforce and Dynamics CRM for Sales

02/10/16 @ 2:00 PM ET "Our CRM is so good that our sales team members WANT to use it," said no sales manager ever. Are yo... ...

The Evolution of the Intranet: Creating a Culture of Collaboration

02/18/16 @ 3:00 PM ET This webcast will be broadcast LIVE from Transitioning Your Intranet to a Digital Workplace - See mo......

Deminar: Microsoft Social Engagement for Marketing, Sales, Service and Research

02/24/16 @ 2:00 PM ET In this deminar (that's demo + seminar) session, we will take a look at the Microsoft Social Engagem......

Top Downloads

SharePoint 2013 Feedback Solution - collect feedback from users into a custom feedback list that captures their feedback and exactly where they were in SharePoint when they provided it.

Why CRM Fails - research into CRM failure, best practices, and how to recover from a failing project.

The 60 Second Collaboration Readiness Self-Evaluation - is your team really ready to collaborate?  If they're not, software isn't going to help.  Take the quick self-evaluation in each department to understand how well your culture collaborates.

Identify Your Support Gaps - collaboration and CRM projects often fall short when it comes to supporting users, because support for these projects is different from other projects.  



The information herein may be used solely at your own risk.  No warranty is made by the author or by C5 Insight, Inc.

The opinions expressed herein are those of the individual authors and do not necessarily represent C5 Insight, Inc in any way.

Copyright 2011-2013 by C5 Insight