Looking for Objects in the SharePoint Deployment failed log.

Posted by Jon Bullen on 2009-04-08
Estimated Reading Time 1 Minutes
Words 236 In Total

SharePoint Content Deployment can be a fun beast at times, this article will walk you through a approach for resolving issues. While working with a client we had the following error in a incremental job:

The object has been updated by another user since it was last fetched

Since the client was not on the latest patch level and unable to patch at this point in time I want to see if I could resolve it out manually. The problem was I dod not know which site they had edited and replaced the default page on. Running the job it was failing at object 1829, being the lovely SharePoint that it is I have no way to workout what object is at 1829… or do I? If you have the system setup to leave the failed cabs on the destination server you can open them up and look for the Manifest.xml files. Once you have these copy them to a place on the system. The following powershell commands will allow you to find the object that it stopped on so you can resolve it, delete it or recreate it.

PS C:\> [xml]$man1 = get-content .\Manifest.xml
PS C:\> [xml]$man2 = get-content .\Manifest1.xml
PS C:\> $man1.SPObjects.SPObject[1829]

Id : 2f93cb16-fae5-4344-8549-3f6c5de60863
ObjectType : SPDocumentLibrary
ParentId : b677f641-222c-4185-9cf4-e916174b316b
ParentWebId : b677f641-222c-4185-9cf4-e916174b316b
ParentWebUrl : /SiteCollection/SubSite
Url : /SiteCollection/SubSite/Pages
DocumentLibrary : DocumentLibrary


If you like this blog or find it useful for you, you are welcome to comment on it. You are also welcome to share this blog, so that more people can participate in it. If the images used in the blog infringe your copyright, please contact the author to delete them. Thank you!