Content Database Synchronization Failed
For the past three/four weeks now, the Application Log(s) within my SharePoint Farm (Moss 2007, Windows 2003 R2, SQL 2005) are being sporadicaly updated with the following entry: Failure trying to synch web application 152ec958-ecf6-476b-9de4-607f446f0275, ContentDB b1dc64b0-7b95-478e-a121-c9dbe8531036 Exception message was Lock request time out period exceeded. A severe error occurred on the current command. The results, if any, should be discarded. ----------------------------------------------------------------------------------------- Previously I had seem similar errors, with the advice to run the 'stsadm -o prepare to move command: Failure trying to synch web application 152ec958-ecf6-476b-9de4-607f446f0275, ContentDB 68f9f8ec-947b-4349-a9e9-c205f12f5c12 Exception message was A duplicate site ID 127fbff5-5396-4bf4-b7b4-41603647f0b5(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 --------------------------------------------------------------------------------------------- I do believe that the above errors are a direct result of porting content databases from one Farm to another (ie, from Staging to Production). However, when we did this, we never previously ran the 'stsadm -o preparetomove' command. What I have done since then, whenever alerted to a content database out of sync, is to perform the following (in an effort to create a new GUID) stsadm -o preparetomove -site %url% -oldcontentdb %guid% stsadm -o deletecontentdb -url %url% -databasename %dbname% -databaseseserver %servername% stsadm -o addcontentdb -url %url% -databaseserver %dbname% -databasename %servername% I have also run 'stsadm -o sync -DeleteOldDatabases 5' But, despite all this, I'm still getting this synch errors - does anyone have any further advice? Recreation of the SSP was my last alternative!
October 26th, 2010 6:39am

Ah indeed! The very last sentence in your entire message is the give away. The whole time it appeared like you were actually working with a CONTENT database when in fact you were working with a SSP database. The two are NOT the same. Moving content databases are as easy as just deleting/moving/adding to SharePoint, but SSP databases are quite another beast. You have to follow a specific approach in order to move those. That is why, in many cases, people opt to recreate their SSPs rather than endure the pain of moving SSP databases. Anyway, to move an SSP database correctly, follow this process: I trust that answers your question... Thanks C
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2010 6:38am

Hi, Thanks to share your problem. Have you checked the connection between the SharePoint server and the DB Server? And the following links might give you a hand: Hope it helps! Leo
October 27th, 2010 10:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics