Hello, I ran the SP2 upgrade over the weekend. Actually, someone had enabled the machines automatic updates, but there was nearly no space on the disc for the update to run, so it failed halfway through. This brought down my sharepoint site on port 80, but the others were fine. Then I absentmindedly deleted the sharedservices site...And finally the update was run again, successfully, and I thought everything was okay. However, I was getting the "There is no admin site for sharedservices1" error. So, I created a new SSP and sites, associated my application with it, created another SSP and tried to associate the old SSP contentDB with it, but I get an error: The specified SPContentDatabase Name=SSP_DB Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object" Anyway, if I check, the version number in the SSP database is 12.0.6425.1000 The version in my new SSP database is also 12.0.6425.1000 but...if I check the version on my current SP site, it is 12.0.0.6421 Is this what is causing the error? Should I reinstalled the service pack 2 again? It appears it did not apply properly to my existing web applications... Regards, Byron Petersona

That's not what I meant...What I mean is that the users have created "My Sites" which is on the old SSP. I don't want to lose that data and really need to restore the old SSP. Unfortunately the "Restore SSP" doesn't seem to work, and if I try to "AddContentDB" using STSADM, to my new SSP, it still gives me the error "The specified SPContentDatabase Name=SSP_DB Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object"Very very strange...byrona

Ok mantisory, for restore SSP you doesn't use addcontentdb but you use stsadm restoressp command ,can you try stsadm restore SSP command , refer to http://technet.microsoft.com/en-us/library/cc262163.aspx Best Regrads, Ahmed Madany

Hi mantisory,firstly, try restore ssp , often stsadm commands are more powerful than GUI, stsadm -o restoressp -title SSP1 -url http://SSPwebapplication:Port# -ssplogin domain\account -mysiteurl http://MySiteWebapplication:Port# -indexserver indexserver -indexlocation "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Data\OfficeServer\Applications" -keepindex -sspdatabaseserver dbserver -sspdatabasename SSPDBName -ssppassword a -ssl noBest Regrads, Ahmed Madany

thanks for that, but the problem is that I am not sure what to use for -URL and -mysiteurl...do I want to use a site that already exists or a whole new site? If i try a new site, using the command:stsadm -o restoressp -title SSP1 -url http://wcpsqlmoss:8459 -ssplogin WCPSQLMOSS\Sharepointadmin -mysiteurl http://wcp.cgisharepoint.com/mysite -indexserver WCPSQLMOSS -indexlocation "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Data\OfficeServer\Applications" -keepindex -sspdatabaseserver wcpsqlmoss\officeservers -sspdatabasename SharedServices1_DB_8b87109e-7034-45e1-bf8b-8561c3cccf0a -ssppassword mypassword -ssl no- in this case,, wcpsqlmoss:8459 is a blank application that I just created, and wcp.cgisharepoint.com is the site for which the SSP was originally for. In any case, I get the error:A SharePoint database named SharedServices1_DB_8b87109e-7034-45e1-bf8b-8561c3cccf0a already exists. You must supply another name for the new database.This is so goofy...I mean, my impression was the "Restore SSP" meaens to restore the SSP from the existing database, no?!?Regards,byron a

I finally solved the problem. In the config DB there was an entry for the DB. I deleted the entry and was able to restore it finally. byrona