Failure trying to synch web application
We had to rebuild our SharePoint environment as part of VM migration. After moving the old content database to new VM SharePoint server and attaching the same, we started seeing logging of error every hour. It relates to a database that was renamed and thus disassociate with its original web application, then reassociated with new one using stsadm -addcontentdb method.
- There are 2 ways to go about in resolving this issue.
Within the table – Sitesynch in Sharedservices database, I foun out that the database id in this do not match with the database id from the config database of the SharePoint. Site ID seems to be ok in this table though. After deleting the rows from this tabase, the errors went away and this table was repopulated back (during next timer job run) correct sites. - I found that you can actually run this stsadm command which helps in resolving this issue and is a better way since this is a command provided by Microsoft.
Here are the details for the second option.
Run the command mentioned below. The value you are passing is how many days old the record are. Just a side note, you are deleting the records that are associated and NOT the database itself.
stsadm -o sync -deleteolddatabases 0
Deleted sync information for DB 36428ec4-00ab-4140-861f-05510dfef27b
Deleted sync information for DB 08f30507-8b24-4cf1-9b9f-1d0464002d57
Deleted sync information for DB 70d0a080-e864-451f-ac9e-9c7047038350
Deleted sync information for DB e6da9e0f-1093-450a-9521-d2e61122b71b
The below command lists all the old databases, which should return 0 rows since the old database entries are deleted using our earlier command.
stsadm –o sync –ListOldDatabases 5
