SSP - trying to create/restore after web app issues
A little farm / SSPbackgroundWe recently upgraded our test farm to SP2. Long story short, we had some issues partially related to the upgrade process with our web apps. Content DBs are fine, so per Microsoft we did the whole create new web app, strip content db from new web app, attach content db from previous web app, etc. So that all works fine. The problem is that the SSP web app and My Sites web app are also impacted.The SSP issueWhat I'm trying to do is either restore the SSP (and keep in mind that the DBs are fine, it's the web apps that are the issue) or create a new SSP using the existing search and SSP DBs.Here's what I've tried so far. First, I created new web apps for the SSP and My Sites. All good. Restoring SSP from Central Admin ->Manage Farm's Shared Services. I supplied the new web app locations in the url locations, gave the SSP a new name. I got an error message telling me the DBs had to be upgraded (keep in mind, we did the SP2 upgrade with issues - had seen a similar error message with other web apps and had to attach content dbs via stsadm). (full error message text follows numbered items) Creating a new SSP from Central Admin ->Manage Farm's Shared Services. Same failure message. Restoring and Creating SSP via stsadm. Got the descriptive "command line error" here. I've posted my syntax below. Central Admin Error Message "Failure! Shared Services Provider restore failed. Reason: The database(s) you specified need to be upgraded before they can be used to create an SSP. You must use the stsadm command 'restoressp' to create an SSP from these databases. Check the event log for details. Note: SSP provisioning will be retried periodically. If you correct the error that caused this failure, provisioning will subsequently succeed. To stop provisioning from being retired, delete the SSP. Command Line Syntax stsadm -o restoressp -title NewSSP -url http://server:port -ssplogin domain\account -mysiteurl http://server:port -indexserver server name -indexlocation C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications -sspdatabaseserver dbserver\instance -sspdatabasename SharedServices db name -ssppassword password -searchdatabaseserver dbserver\instance -searchdatabasename Search db nameFor the Command line I tried both the -o restoressp and -o createssp (the rest of the syntax was the same). The urls are the new web apps. Haven't tried with old wep app names.What am I missing here?
September 10th, 2009 10:19am

When you tried creating a new SSP, did you see anything useful in the SharePoint logs? If not, you could try going into Central Admin > Operations > Diagnostic Logging and increase the log verbosity detail. I would also try connecting to these databases in another SP environment (for example, create a copy in your Test environment and try it there). If it worksin a different farm, then you know it's a problem with your current app server. Andre Galitsky, MS-Certified SharePoint Administrator, Lexington, KY -- My SharePoint Blog: http://www.sharepointnomad.com
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2009 3:18pm

Good morning! unfortunattly, I have the same problem. Please, can You tell me the issue of this problem?
August 10th, 2012 3:50am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics