Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

Resolve errors after moving content databases to new farm

Asked By: Bob Bolton Date: Feb 10, 2009 Category: Sharepoint Views: 491

I moved all of our content databases from one farm to another.
Our production portal crashed, Our portals are up and running on
their new server, I'm picking up the pieces...

I'm getting a lot of errors like:
Failure trying to synch web application 96675923-f4e5-4ace-a240-
2a8895da44bd, ContentDB 5108afe9-84d5-4bf1-9790-9cc786c47791
Exception message was A duplicate site ID 051314e0-d3e5-49e0-b40d-
d3d90d870439(http://moss3/ssp/admin) was found. This might be caused
by restoring a content database from one server farm into a different
server farm without first removing the original database and then
running stsadm -o preparetomove. If this is the cause, the stsadm -o
preparetomove command can be used with the -OldContentDB command line
option to resolve this issue.

I ran the following command. "This command will list all databases
that have not synced up correctly with the SSP in greater than 0 days.

stsadm -o sync -listolddatabases 0

Shared Service Provider SharedServices1
ID: c8bd0ce0-06df-4acf-8300-1fb354085c19 Synchronized: 5/28/2008
11:00:03 PM
ID: 7d58e12d-d165-4714-a04b-66caf7ab1761 Synchronized: 6/13/2008
11:00:01 AM
ID: a117d43c-7afa-4ddb-b197-67d2d4363c97 Synchronized: 6/13/2008
11:00:01 AM
ID: 5ed512c5-72f0-40dc-a137-685ba8d15052 Synchronized: 5/29/2008
2:00:00 AM
ID: 91e98f13-c435-4d5c-8ef6-9f53ff865aa0 Synchronized: 6/13/2008
11:00:01 AM
ID: 71dd3fa8-98d0-47e0-bf29-d968be753dbd Synchronized: 6/13/2008
11:00:01 AM
ID: cdcfb3d6-4d13-41ed-b0bf-dcd9d06df0a8 Synchronized: 6/13/2008
11:00:01 AM
ID: fd64eab9-2609-4478-8d2a-e4acb5f1388b Synchronized: 6/13/2008
11:00:01 AM

To fix my errors I intend to run:

stsadm -o sync -deleteolddatabases 0

"...this will delete all GUID entries in the SSP for anything that is
out of sync for more than 0 days. You have now successfully cleaned
all inconsistencies with syncing in your SSP. All out of sync alerts
should now subside."

So... I hope if I run this command it will clear my errors and allow
proper syncing for my content databases. Has anyone gone through
this problem? Have you had to run any other stsadm commands to sync
the content databases after they have already been moved and working
in another farm?

Here was my reference document:
blogs.technet.com/.../detaching-
databases-in-moss-2007-environments.aspx

Tagged:resolve errors after moving content databases to new farm

2 Answers Found

Answer #1 Answered By: Brooke Lewis Answered On: Feb 10, 2009

Failure trying to synch web application
09a21da5-4485-4b00-8268-772aea7fea12, ContentDB
65301403-c277-4b4c-ad5a-e822572d10ea: A duplicate site ID
3b3a4372-aa91-4e0c-ba57-2567958d81bb(http://portal/sites/test1
<http://portal/sites/test1> ) was found. This might be caused by
restoring a content database from one server farm into a different
server farm without first removing the original database and then
running stsadm -o preparetomove. If this is the cause, the stsadm -o
preparetomove command can be used with the -OldContentDB command line
option to resolve this issue.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I would also suggest giving a unique name for your content databases
when creating them instead of using the auto generated contentdb's.
This really helps identify the correct db associated with a web
application inside of SQL. Also ensure you review the logs of the
SharePoint server located in "C:\Program Files\Common Files\Microsoft
Shared\web server extensions\12\LOGS
<file:///C:\Program%20Files\Common%20Files\Microsoft%20Shared\web%20serv
er%20extensions\12\LOGS> " .

I have encountered the same experience to which you are having and fixed
it by following the article listed here:

blogs.technet.com/.../detaching-databases-i
n-moss-2007-environments.aspx

Answer #2 Answered By: Talia Johns Answered On: Feb 10, 2009

We'll see what happens. I'm going to try fixing this later today.

The database naming is a must for sure. We are starting to build small
farms using the same SQL server. I'm starting to name databases with a
prefix which is the name of the web server the applications are running
on.

Didn't find what you were looking for? Find more on Resolve errors after moving content databases to new farm Or get search suggestion and latest updates.