Wednesday, March 04, 2009

Unable to delete Shared Services Provider in SharePoint (MOSS)

Sometimes The SSP you create in MOSS are not created properly. This can be result of interruption while SSP was being created or in result of bad migration from SPS03 or MCMS to MOSS.

1. In left nav of SharePoint Central Administration, the name of your new SSP will not render rather, it will show up as text.
2. If you try to delete that from the Central Admin, the Delete option is disabled.

You should delete the SSP using stsadm command line tool (NOTE: My SSP's name is "SSP" which is specified after "title" in command:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa
dm -o deletessp -title "SSP"

However, if you have any dependencies, you will have to delete them first or you will get following error when you try deleting it through command line tool:

An object in the SharePoint administrative framework, "SharedResourceProvider Na
me=SSP Parent=SPFarm Name=SharePoint_Config", could not be deleted because other
objects depend on it. Update all of these dependants to point to null or diffe
rent objects and retry this operation. The dependant objects are as follows:
SPWebApplication Name=SSP_MYSITE Parent=SPWebService
SPWebApplication Name=SSP2 Parent=SPWebService
SPWebApplication Parent=SPWebService

To get rid of the dependencies, you will have to use a trick:
(*Warning: As you can see Stefan Goßner's comment, directly tweaking with DB violates licensing terms so use it for your experiment only if you have to. I would suggest to open a ticket with Microsoft for this)
Open SQL Server Management Studio and execute following query to fetch the SSP dependencies:
SELECT * from Objects WHERE like '%SSP%'
Note that in the "Status" column, you'll find "3". Changing that back to default "0" does the job:
UPDATE Objects SET Objects.Status=0 WHERE'SSP'
Now again run the command:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o deletessp -title "SSP"

Your currupt SSP is gone!

Now you should be able to create a new SSP without problems.


  1. Hi Tahir, How are you? It's been such a long time. You are one of the few friends in my Google Reader who blog. Seems like working actively on Sharepoint. Goodluck !


  2. Sorry, but this approach will cause an unsupported environment as direct manipulation of the database is not allowed.
    See here for details:

    1. Although this is a very old post, but my blog-stats show that people are still searching for it. I have updated the post to have a warning and a suggestion to open a ticket with Microsoft. I am sure MS would have a patch for this...


Feel free to give constructive feedback or let me know if it was helpful.