A duplicate site ID {0} 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.
A duplicate index entry exists in the registry. No other indexes are affected, but it is recommended that the duplicate entry ...
A duplicate index entry exists in the registry. No other indexes are affected, but it is recommended that the duplicate entry ...
A duplicate of this document was detected, and the document will be retried. If this problem persists, recreate the content ...
A duplicate of this document was detected, and the document will be retried. If this problem persists, recreate the content ...
A duplicate site ID {0} was found. This might be caused by restoring a content database from one server farm into a different ...
A error occurred while changing the page order in the meeting workspace. For assistance, contact your site administrator. ...
A failure may have corrupted the content of the item. Copy the content to a new item, or save the item as a text file or ...
A failure occurred when accessing the registry entry {0} located at registry key {1}. Please ensure that SharePoint Products ...
A failure occurred when accessing the registry entry {0} located at registry key {1}. Repair this product by selecting it ...