locked
Duplicate site after MOSS SP 2007 Service Pack 3 installed RRS feed

  • Question

  • Yesterday, I applied Service Pack 3 and cumulative upgrade April 2012 for WSS and MOSS SP 2007. The installs went well.

    While things are running well, I am getting the following message regularly within the ULS logs.

    I did no restore of database.

    Since I did no restore, how do I resolve this issue?

    Alert: Content Database Synchronization failed

    Source: myserver

    Path: myserver.mydomain.stuff

    Last modified by: System

    Last modified time: 10/21/2012 12:00:08 AM

    Alert description: Event ID 5555 from Source Office SharePoint Server on agent computer myserver.mydomain.stuff has triggered this Alert Description : Failure trying to synch web application a5f6e661-8c06-4b4f-96c4-c280017425a3, ContentDB 237e8905-cc02-41ba-80b6-e9ec00711a74  Exception message was A duplicate site ID 8aaf24d2-0a9e-4db4-990a-4fd56827d1cd(http://myfarm/mysite) 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.

    Sunday, October 21, 2012 12:09 PM

All replies

  • Looking more closely at the emails, I notice that there are a pair of these being issued - one for http://myfarm/mysite and http://myfarm

    I can access each of them. So however I resolve this, I don't want to mess that up.

    Sunday, October 21, 2012 12:16 PM
  • Further research is interesting - it turns out that the sharepoint mysites created do not use the http://myfarm/mysite site ; instead they are created as a series of site collections that are part of the myfarm web app as personal/LOGIN .  I don't know that anything uses the mysite that is being reported as a duplicate.

    I do know, however, that the duplicate site for the top level of the web app is used. Is anyone willing to advise on how to proceed to resolve this?

    Monday, October 22, 2012 12:08 AM
  • There are a pair of events that occur for the 2 sites.

    One is an Event ID 5555 from User Profiles. It says:

    Event Type:        Error

    Event Source:    Office SharePoint Server

    Event Category:                User Profiles

    Event ID:              5555

    Date:                     10/22/2012

    Time:                     7:00:01 AM

    User:                     N/A

    Computer:          myserver

    Description:

    Failure trying to synch web application a5f6e661-8c06-4b4f-96c4-c280017425a3, ContentDB 237e8905-cc02-41ba-80b6-e9ec00711a74  Exception message was A duplicate site ID 8aaf24d2-0a9e-4db4-990a-4fd56827d1cd(http://myfarm/mysite) 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.

    The other event of the pair says

    Event Type:        Error

    Event Source:    Office SharePoint Server

    Event Category:                Office Server General

    Event ID:              7888

    Date:                     10/22/2012

    Time:                     7:00:01 AM

    User:                     N/A

    Computer:          myserver

    Description:         

    A runtime exception was detected. Details follow.

    Message: A duplicate site ID 8aaf24d2-0a9e-4db4-990a-4fd56827d1cd(http://myfarm/mysite) 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.

     

    Techinal Details:

    Microsoft.Office.Server.UserProfiles.ProfileSynchronizationDuplicateSiteIDException: A duplicate site ID 8aaf24d2-0a9e-4db4-990a-4fd56827d1cd(http://myfarm/mysite) 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.

       at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.RegisterSitesForSynch(Guid[] rgGuid, Int32 nGuids, Object dummy)

       at Microsoft.Office.Server.UserProfiles.SynchCollection`2.FlushAdds()

       at Microsoft.Office.Server.UserProfiles.SynchCollection`2.Add(T objAdd)

       at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.AddRemoveSites(String strFirstChangeToken, SPChangeToken lastChangeToken)

       at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.SynchContentDB()

       at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)

     --------

    During the preparation for performing the service pack 3 upgrade, I did go through the steps of removing each of the content databases and then adding them back. I was told by Microsoft that this was a good way to flush out any orphans that might be in the system.

    I did the remove and add from within Central Administration.

    At this point, what operation do I need to perform so that SharePoint no longer generates these errors?

    Monday, October 22, 2012 2:29 PM
  • I have run stsadm -o databaserepair on our 2 content databases, and before and after the service pack process, the orphan count has been 0.
    Monday, October 22, 2012 2:36 PM