by dipbiswas
17. January 2010 11:16
One of the scenarios this happens is when someone renames a database and makes a site lock on site collection and then forgets to unlock it after restoring.
This is difficult to troubleshoot because you think that you made everthing correct. Everything looks fine but you have no access to your site collection. If you have no access to your site collection first check the sitelock on the command line!
stsadm -o getsitelock -url http://
Your output should be
If not you can review your eventlog and will see below errors (this two error are repeating each hour)
Event Type: Error
Event Source: Office SharePoint Server
Event Category: User Profiles
Event ID: 5555
Date: 7/14/2008
Time: 8:00:01 PM
User: N/A
Computer:
Description:
Failure trying to synch web application ac716e97-0297-4ddf-a6c4-a751034147c6, ContentDB 465225b1-5ced-4a34-8a0c-381cd54d5199 Exception message was A duplicate site ID 86fe2e72-5347-46b2-b7c5-73b92fc8c6db(http://
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888
Date: 7/14/2008
Time: 8:00:01 PM
User: N/A
Computer:
Description:
A runtime exception was detected. Details follow.
Message: A duplicate site ID 86fe2e72-5347-46b2-b7c5-73b92fc8c6db(http://) 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 86fe2e72-5347-46b2-b7c5-73b92fc8c6db(http://) 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.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)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
If you try to access the site collection you will get following error (only if you try to access!)
Event Type: Information
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1314
Date: 7/14/2008
Time: 9:08:16 PM
User: N/A
Computer:
Description:
Event code: 4011
Event message: An unhandled access exception has occurred.
Event time: 7/14/2008 9:08:16 PM
Event time (UTC): 7/14/2008 7:08:16 PM
Event ID: 8de7884ebe164cdc9110021e83992184
Event sequence: 77
Event occurrence: 9
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/5294604/Root-1-128605293299491491
Trust level: WSS_Custom
Application Virtual Path: /
Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\\
Machine name:
Process information:
Process ID: 3684
Process name: w3wp.exe
Account name:
Request information:
Request URL:
Request path: /Pages/default.aspx
User host address:
User:
Is authenticated: True
Authentication Type: NTLM
Thread account name:
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
As it always is the resolution is just simple.
Check the sitelock on your site collection
stsadm -o getsitelock -url http://
Your output should be “”
type following command
stsadm -o setsitelock -lock none -url “http://”
check again the sitelock status
stsadm -o getsitelock -url http://
Your output should be “”
Because your database is now out of synchronisation you should make following steps:
1) Make a full index of your site collection
2) Check your sync after you crawled the site collection (You should see that the sync of one site collection is different to the others)
stsadm -o sync -ListOldDatabases 0
3) Wait one day (you see the time above)
If you type
stsadm -o sync -ListOldDatabases 0
your see that one database is out of sync
Delete the database which is out of sync
stsadm -o sync -DeleteOldDatabases 1
Now everything should be fine.
6b5b6cd6-fcda-4401-8140-1ec190e893c5|0|.0
Tags:
Event IDs
The opinions expressed herein are personal opinions and do not represent others' view in anyway. All posts are provided AS IS with no warranties, and confers no rights.
Subscribe