locked
Unprovisioning an SSP? RRS feed

  • Question

  • I have several MOSS 2007 sites running on a farm. I created a new site, and a separate SSP for it to limit its Search scope.

    I had to make some AAM changes for the new site, and search stopped working for this site. I wish to delete and recreate the SSP. When I selected 'delete', it began to run. It has been about 24 hours and when I look at "Manage this Farm's Shared Services", I'm still seeing a "!" (Unprovisioning). The site is relatively small, a couple gigs at the most. Any way I can track whether this has hung up?

    The DB's are small:
    SSP I'm trying to delete is 13.5MB, SSPSearchDB is 70MB
    SSP for all other sites it would be merging with: 1022MB and 2231MB

    Thanks!

    Thursday, December 2, 2010 8:00 PM

Answers

  • Make sure to use the "title" switch  in the command Nagesh mentioned if you do have several SSP's.  stsadm -o deletessp -title SharedServices -force  Using this without the switch will delete the primary or default SSP forcibly with no chance of recovery. This is a full reference link to TechNet http://technet.microsoft.com/en-us/library/cc262003(office.12).aspx#section4 

    I also recommend moving any associated web applications to another SSP (if possible) before deleting the SSP. http://technet.microsoft.com/en-us/library/cc262003(office.12).aspx 

    Also note any search or profile data will be lost when removing the SSP this way but i'm assuming that's fine since you're deleting it anyway.  Just wanted to call that out.

    Thanks and please report back any progress or challenges.


    Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog
    • Proposed as answer by Pratik Vyas Friday, December 3, 2010 5:50 PM
    • Marked as answer by Mike Walsh FIN Friday, December 3, 2010 6:55 PM
    Thursday, December 2, 2010 8:43 PM
    Moderator

All replies

  • I have had this happen to me. only way i could get it to go away was to Restart the server. then delete SSP using STSADM - DELETESSP - FORCE

     


    HTH
    Nagesh S

    Days and years do not mean anything to me. Moments shared are frozen
    in their time frame. Distance or time never fades them for me. I cherish them
    like my life. I have never let them sleep alone. Sachi
    Thursday, December 2, 2010 8:30 PM
  • Make sure to use the "title" switch  in the command Nagesh mentioned if you do have several SSP's.  stsadm -o deletessp -title SharedServices -force  Using this without the switch will delete the primary or default SSP forcibly with no chance of recovery. This is a full reference link to TechNet http://technet.microsoft.com/en-us/library/cc262003(office.12).aspx#section4 

    I also recommend moving any associated web applications to another SSP (if possible) before deleting the SSP. http://technet.microsoft.com/en-us/library/cc262003(office.12).aspx 

    Also note any search or profile data will be lost when removing the SSP this way but i'm assuming that's fine since you're deleting it anyway.  Just wanted to call that out.

    Thanks and please report back any progress or challenges.


    Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog
    • Proposed as answer by Pratik Vyas Friday, December 3, 2010 5:50 PM
    • Marked as answer by Mike Walsh FIN Friday, December 3, 2010 6:55 PM
    Thursday, December 2, 2010 8:43 PM
    Moderator
  • Thanks guys. Will do.

    Kris: if I understand you correctly, i did try to create an "SSPSearchDB2" before trying to delete SSPSearchDB. Both would have been associated with the same site collection. However, when I created the new SSP, selecting the site collection I want wasn't available, so it seems I'll need to delete, recreate, and, hopefully, associate it with the site collection.

    Thursday, December 2, 2010 9:18 PM
  • Yes in that case they should auto associate just remember the following.

    Also note any search or profile data will be lost when removing the SSP this way but i'm assuming that's fine since you're deleting it anyway.  Just wanted to call that out.


    Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog
    Thursday, December 2, 2010 10:39 PM
    Moderator
  • As far as reboots go, should the WFE hosting CA cover it, or would you recommend rebooting the other WFEs (three all together) along with the Index server?

    Friday, December 3, 2010 3:48 PM
  • You shouldn't need too but I've see MOSS get stuck before and a reboot helps... Did the SSP delete for you?  What's the status?
    Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog
    Friday, December 3, 2010 5:05 PM
    Moderator
  • Ran

     

    stsadm -o deletessp -title SSPName -force 

     

    Deletion worked. I’m now recreating SSPName. Operation in Progress.

     

    Will report back if/when Search works.

    Thanks!

    Friday, December 3, 2010 5:48 PM
  • Okay, I created a new SSP with a different name. Ran fine. However, when I clicked "Content sources and crawl schedules", I got this error:

    Could not find stored procedure 'dbo.proc_MSS_GetCrawlHistory'.   at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchAdminPageBase.ErrorHandler(Object sender, EventArgs e)
       at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchSSPAdminPageBase.OnError(EventArgs e)
       at System.Web.UI.Page.HandleError(Exception e)
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
       at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
       at System.Web.UI.Page.ProcessRequest()
       at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
       at System.Web.UI.Page.ProcessRequest(HttpContext context)
       at ASP._layouts_listcontentsources_aspx.ProcessRequest(HttpContext context)
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Any ideas?

    Friday, December 3, 2010 8:17 PM