Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Event ID 7888

  Asked By: Antoinette    Date: Feb 08    Category: Sharepoint    Views: 1243

Can used a export/import for this site collection from one farm to
another and on just one of my WFE Servers I can getting these error
every hour.



Can I just run this command



Stsadm -o preparetomove -contentdb sql.domain.com\moss:VSSite_Content
-site http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com -oldcontentdb VSSite2_Content



Or do I have to find the GUID for the old content DB? Is this is old
content DB GUID 5b5c5ea4-8a37-472f-a741-b88f1a3e0570?



Event Type: Error

Event Source: Office SharePoint Server

Event Category: Office Server General

Event ID: 7888

Date: 9/17/2008

Time: 1:00:03 PM

User: N/A

Computer: NJMOSSWEB02

Description:

A runtime exception was detected. Details follow.

Message: A duplicate site ID
5b5c5ea4-8a37-472f-a741-b88f1a3e0570(http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com) 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.ProfileSynchronizationDuplicateSite
IDException: A duplicate site ID
5b5c5ea4-8a37-472f-a741-b88f1a3e0570(http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com" target="_blank" rel="nofollow">http://site.moss.domain.com) 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.RegisterSites
ForSynch(Guid[] rgGuid, Int32 nGuids, Object dummy)

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

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

at
Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.SynchContentD
B()

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



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

Share: 

 

1 Answer Found

 
Answer #1    Answered By: Sheena Ray     Answered On: Feb 08

I have already run



stsadm -o sync -DeleteOldDatabases 0

 
Didn't find what you were looking for? Find more on Event ID 7888 Or get search suggestion and latest updates.




Tagged: