If you attempt to delete the default SSP from within Shared Services Administration, the Delete link will be greyed out. That’s because it’s the default SSP and SharePoint doesn’t allow you to delete the default SSP via the GUI.
One option to get around this is to create a new SSP and change associations to point to that new SSP. Once you do that, the Delete link for the original SSP becomes available because it no longer has any shared services associated with it.
If you’re like me however, and you don’t want to go to all that effort, then there’s a little trick to get around this.
stsadm -o deletessp -title SharedServices -force
The help for the deletessp command won’t actually indicate that -force is a valid switch, but without it, the command may fail. If you run into errors, try running it with -force.
The deletessp command will force the removal of the default SSP. If you receive an error after running the command, that’s fine. Sign back into Shared Services Administration and the delete link for the default SSP should no longer be greyed out.
Once you click Delete, you will be prompted to delete the associated databases, but in my experience, this generally doesn’t work. As a secondary step, I often find myself doing a bit of clean up. Within the database server, I remove all the default SSP databases and within IIS, I remove the SSP web site and application pool.
That should do it! You should now be able to create a new SSP. If you have any problems, or encounted an issue I did not cover here, please contact me or post a comment, I’d be happy to help.
You shouldn’t have to recreate your My Sites web app or any other web app that was associated with that SSP. You should be able to just re-configure those associations. Any search, profile or audience data will be lost and will have to be re-configured.