Issues following partial upgrade of MOSS 2007 environment to SP3.
Folks, In a test MOSS environment (MOSS 2007, W2K3) we attempted an upgrade to SP3. In advance of the upgrade we took VMWARE snapshots of the database server, central admin server, and two Web Front End servers. In advance of the upgrade we detached the databases using stsadm. An issue was encountered during the upgrade, and after some investigations we decided to roll back the changes using the VMWARE snapshot. So all changes made were discarded. However, we now have an unusual problem. An attempt to reattach the databases using stsadm (stsadm -o addcontentdb -databaseserver dbshptst01 -databasename ACME_ACMEI_DMC_Content_1 -url http://acmemosstest) results in the following error message. The attach operation cannot continue because another object in this farm already contains the same ID. Each object in a farm must have a unique ID. In order to proceed with the attach operation you must assign a new ID to this database. To attach this database with a new ID, use the "stsadm.exe -o addcontentdb" operati on with the -assignnewdatabaseid parameter. Note that if this new database and a n existing database contain the same site collections, attaching this database w ill likely result in orphaned site collections due to conflicts between the two databases. I then attempted to add the database using the additional -assignnewdatabaseid parameter. Error message was "A SharePoint database named acme_acmeI_DMC_Content_1 already exists. You must supply another name for the new database. However if you look in the Central Admin Console (Central Administration > Application Management > Site Collection List ) it shows no site collections. Central Administration > Application Management > Content Databases shows no content databases. So before the upgrade we had multiple content databases, and multiple site collections. We detached them using stsadm, performed upgrade, rolled back to before upgrade using VMWARE, and now cannot see any content databases or site collections via the console (or stsadm). We cannot attach them as can be seen above, and so are in limbo. The databases themselves are up and running, and we can access the console and other information. Has anyone encountered this problem, or have any tips/advice on how to resolve?
May 10th, 2012 4:32pm
Hi, Since you have already restored the databases via snapshot why are you attaching them again? You should have your environment ready with the first step itself.Thanks, Rahul Rashu
May 11th, 2012 6:18am
Hi Rahul I am working with the OP on this. The snapshot was taken with the databases attached, but when we restored the snapshot the databases were not attached - ie stsadm did not list any databases, likewise central admin shows no content databases in the web application. The urls of the site collections associated with these databases are inaccessible via a browser (http 404 error). [note the content databases I refer to are the user content databases - other content databases of other web applications, such as My Sites and the SSP, do appear as attached and are accessible via a browser] This lead us to try and reattach the user content databases, resulting in the error. From the error message it appears sharepoint believes the databases to already be attached. I have today attempted a SQL restore of every database in the farm, but I am still getting the same error. Thanks for any suggestions you may have.....
May 12th, 2012 11:05am
HI, Try executing a configuration wizard and connect to your existing config database to see if it fixes the problem.Thanks, Rahul Rashu
May 12th, 2012 4:40pm