Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan Go??ner : Deep Dive into the SharePoint Content Deployment and Migration API - Part 1

Sat, 12 Apr 2008 02:39:42 GMT

PingBack from http://blogs.technet.com/stefan_gossner/archive/2007/08/30/deep-dive-into-the-sharepoint-content-deployment-and-migration-api-part-1.aspx

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Ranjan Banerji — Sun, 13 Apr 2008 18:43:28 GMT

Thanks for posting this. I was about to write up something similar but now it will be easier to just point to your blog.

A few additional items that I would consider adding are:

1. Be careful about the frequency of deployment jobs. Content deployment has a severe impact of performance if your site heavily uses cross list queries, CQWP, or the object cache. Deployment wipes clean the object cache.

2. Be careful about how many jobs you run not just their frequency. for the same reason as number 1. Sometimes its necessary break down deployment into smaller jobs to get initial deployment.

3. Write a script to change the default timeout for transport/import to a larger number. Default is 10 seconds and on a slow netwrok it will kill deployment.

4. Be careful about full deployments. Your database size will grow with each full deployment.

5. Evaluate whether you want versions turned off at the destination. If so write a script to turn it off. Full deployment will turn it on and grow the database again. So be careful.

I am sure I will think up of a few more :-).

Thanks for this series of articles. They have been very useful.

Ranjan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Mon, 14 Apr 2008 10:21:38 GMT

Hi Ranjan,

that is great input!

Maybe you could post the important pieces of the scripts you mentioned as well?

And keep your input coming!

:-)

Cheers,

Stefan

Content Deployment - Getting it Right

Ranjan Banerji — Wed, 16 Apr 2008 08:12:36 GMT

Content Deployment - Getting it Right

Ranjan Banerji — Fri, 18 Apr 2008 03:55:15 GMT

Content Deployment - Getting it Right

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Hamzeh Ayesh — Mon, 12 May 2008 15:08:28 GMT

Hi Stefan,

First of all I would like to thank you for the great series of articles, they were useful and direct to the point.

Now I have successfully exported/imported my SharPoint site from one server to another one, all the contents were moved but I faced 2 points:

1. I faced error in my custom master page, although I can see it in the designer that it’s there but when I set my custom master page as the site master page it gives this error: File not found. What’s the reason behind this error although the page was migrated as I saw in the designer but it shows the above error when I select it. Any clue??

2. Another point is the security migration, when I migrate the security groups it stars find during the import process then stopped with this error: User or group 23 cannot be resolved.

Below is part of the log file related to the error:

[5/11/2008 3:04:18 PM]: Progress: Importing Group NAS Owners.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 1.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 9.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 11.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 13.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 14.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 15.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 16.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 30.

[5/11/2008 3:04:18 PM]: Progress: Importing Group NAS Visitors.

[5/11/2008 3:04:18 PM]: Progress: Importing Group NAS Members.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Style Resource Readers.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 7.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Designers.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 1.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 10.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 16.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hierarchy Managers.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Approvers.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 1.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 9.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 14.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Restricted Readers.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Quick Deploy Users.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Duty Officer.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Staff Agent.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Operational Admin.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Shift Supervisor.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Financial Admin.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Marketing Admin.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Corporate Admin.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Hala Online Customer.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 9.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 17.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 18.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 19.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 21.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 22.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 23.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 24.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 25.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 26.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 31.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 32.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 33.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 34.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 35.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 36.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 37.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 38.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 39.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 40.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 41.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 42.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 43.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 44.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 46.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 47.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 48.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 49.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 50.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 55.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 56.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 57.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 60.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 61.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 62.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 63.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 64.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 65.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 66.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 72.

[5/11/2008 3:04:18 PM]: Progress: Importing Group NAS Survey Subscribers.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 9.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 17.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 18.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 19.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 21.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 22.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 34.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 44.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 54.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 55.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 65.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 72.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Editor.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 1.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 9.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 27.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 70.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Content Supervisor.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 9.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 67.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 73.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 74.

[5/11/2008 3:04:18 PM]: Progress: Importing Group News–FAQs–Polls Supervisor.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 9.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 54.

[5/11/2008 3:04:18 PM]: Progress: Importing Group Nassir Group.

[5/11/2008 3:04:18 PM]: Progress: Importing Group member 1.

[5/11/2008 3:04:18 PM]: Progress: Starting content import.

[5/11/2008 3:04:18 PM]: Progress: De-Serializing Objects to Database.

[5/11/2008 3:04:19 PM]: Warning: User or group 23 cannot be resolved.

[5/11/2008 3:04:19 PM]: FatalError: User or group 23 cannot be resolved.

at Microsoft.SharePoint.Deployment.DeploymentLogger.Log(DeploymentLogSeverity severity, SPDeploymentObject deplObject, String message, Boolean throwException)

at Microsoft.SharePoint.Deployment.DeploymentLogger.Log(DeploymentLogSeverity severity, String message)

at Microsoft.SharePoint.Deployment.ImportObjectManager.ConvertToDestUserId(Int32 userid, Boolean bAllowFallback, Boolean& bIsGroup)

at Microsoft.SharePoint.Deployment.WebSerializer.DealWithGroupsOnImport(ImportObjectManager objectManager, DictionaryEntry property)

at Microsoft.SharePoint.Deployment.WebSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)

at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)

at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)

at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)

at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)

at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)

at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()

at Microsoft.SharePoint.Deployment.SPImport.Run()

[5/11/2008 3:04:19 PM]: Progress: Import Completed.

[5/11/2008 3:04:19 PM]: Finish Time: 5/11/2008 3:04:19 PM.

[5/11/2008 3:04:19 PM]: Completed with 1 warnings.

[5/11/2008 3:04:19 PM]: Completed with 1 errors.

Any clue why this is happening?? For the time being I did import without security until I solve the master page problem.

Regards,

Hamzeh Ayesh

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Mon, 12 May 2008 18:36:27 GMT

Hi Hamzeh,

please open a support case so that your specific problem can be analyzed in more details.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Franco — Thu, 15 May 2008 18:26:25 GMT

Stefan

Is there a "best practice" for deleting list items or other pages when it comes to content deployment? If list times are deleted on the source server will content deployment delete that same item on the destination server? My experience working with MCMS and Site manager 2002 showed me that it was better to "expire" postings rather than delete them as our replication process could not delete postings or channels on the destination server.

Thanks

Franco

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Thu, 15 May 2008 19:05:35 GMT

Hi Franco,

incremental deployment will take care of deleted items. Full deployment will not take care.

With MCMS it was the same. Incremental deployment reliably deleted items on the destination.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Franco — Tue, 20 May 2008 06:33:19 GMT

Hi Stefan

Thanks for your previous response.

I read through items 3,4,5,6 and 7 of part 6. I created a blank site using stsadm, ran a full content deployment successfully and scheduled incremental deployment. However, a number of features on the destination server are still not activated despite being activated on the source server.

Is there a way I can activate them without having to re-create the site collection and run a full content deployment? This did not seem to work this first time.

Thanks

Franco

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Tue, 20 May 2008 09:15:14 GMT

Hi Franco,

are these standard features coming with WSS/MOSS or custom features?

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Franco — Tue, 20 May 2008 15:24:16 GMT

Stefan

These are custom features developed by the vendor.

Thanks

Franco

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Tue, 20 May 2008 15:31:06 GMT

Hi Franco,

it is hard to tell what's going on here without seeing a repro. I would suggest to open a support case to get this problem analyzed in more detail.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Mark — Fri, 23 May 2008 01:16:21 GMT

Hi Stefan

Great articles

In our system we have an authoring and staging site collection on the same box (different web app).

The first time we run a full deployment from auth to stage the files are OK, however then next time many files (css, master pages) are unghosted and have been reverted to a previous version of the files - as if they are pulled from some cache somewhere.

Any advice on how to sort this out?

Thanks

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Fri, 23 May 2008 09:20:58 GMT

Hi Mark,

a couple of days two hotfixes have been released which address a similar problem.

Please open a support call with Microsoft and request the followig two hotfixes:

952698, 952704

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Ajay — Tue, 27 May 2008 12:01:37 GMT

Hi Stefan,

This is " Ensure that content deployment jobs do not run in parallel".

I have a custom migration job which runs every 15 mins and exports a package with data from few lists.

Sharepoint content deployment also has a quick deployment feature, if my custom job is running and at the same point someone uses quick deploy on the same server,, will these 2 kill each other.

They will be on the same server but different sites.

Thanks

Ajay

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Tue, 27 May 2008 12:07:33 GMT

Hi Ajay,

that means they can run in parallel. Meanwhile two hotfixes have been released to support this:

952698, 952704

Cheers,

Stefan

Pimp My Content Deployment Job

Stefan Goßner — Thu, 29 May 2008 16:51:56 GMT

As a follow up to my article series about the content deployment and migration API here are some tips

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

RajeshV — Thu, 03 Jul 2008 12:49:26 GMT

Hi Stefan,

I am facing the following issue with respect to Incremental deployment.

The incremental deployment fails with following error.

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

Sometimes it gets rectified on its own while I never stop the incremental run.

Other wise I always have to do a FULL to resolve the issue. I have MOSS with SP1 and content deployment post SP1 installed both in source and destination.

Greatly appreciate your quick response

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Thu, 03 Jul 2008 13:56:33 GMT

Hi Rajesh,

I assume this happens during import. Can happen if you have updated content in the destination database. You should ensure that content is only updated on source - not on destination.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Franco — Fri, 01 Aug 2008 00:44:21 GMT

Stefan

Is it possible for me to do a sts adm back up from my 32 bit MOSS 2007 machine and restore it to my 64 bit machine?

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Fri, 01 Aug 2008 10:04:25 GMT

Hi Franco,

if you have the publishing feature enabled you are not allowed to use backup between farms.

Only export and import is allowed.

See here for details:

http://blogs.technet.com/stefan_gossner/archive/2008/03/12/common-error-situation-with-when-using-backup-restore-to-transfer-a-database-to-a-new-farm-on-moss-2007.aspx

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Sanjaya — Mon, 04 Aug 2008 23:29:00 GMT

Hi Stefan,

Great Article.

I have been using stsadm backup/restore to move my site between farms. It was a document workspace, didn't require publishing features, and have not faced any problems so far. Having gone through your series of articles, i am now trying the same with Import/Export for testing. Import has been successful. For export, I first created a Document workspace in the destination site and then ran Import. Import failed. The error says "Could not find a feature". Now, i 've come to know that the features on the source site must be first deployed on the destination site. However, i have a doubt here: there are lots of custom features installed in my development site but some of them only are activated. Now in the destination farm, should i deploy all the features (activated and non-activated) or only those currently active on my development site before running Import again?

Thanks!

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Sanjaya — Mon, 04 Aug 2008 23:34:08 GMT

There has been a typo mismatch in my last comment.

My export was successful and facing issue for Import. Sorry about that.

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Tue, 05 Aug 2008 09:32:24 GMT

Hi Sanjaya,

you have to install all features on the target. Feature activation should happen when performing the import.

Are you exporting/importing the whole site collection or only a subsite?

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Sanjaya — Tue, 05 Aug 2008 16:08:02 GMT

Thanks Stefan.Its a site collection but has a root web only at this time.

Sanjaya

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Tue, 05 Aug 2008 16:12:49 GMT

Hi Sanjaya,

then you only have to install and not activate.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Sanjaya — Tue, 05 Aug 2008 21:06:08 GMT

Stefan,

The 'could not find feature' error on Import is gone, but i'm now getting this error attached below.

8/5/2008 1:28:11 PM :Started import to URL {}

8/5/2008 1:37:45 PM :Configuration values are not defined in web.config file

8/5/2008 1:37:45 PM : at Microsoft.SharePoint.Library.SPRequest.ApplyTheme(String bstrUrl, String pVal)

at Microsoft.SharePoint.SPWeb.ApplyTheme(String strNewTheme)

at Microsoft.SharePoint.Deployment.WebSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)

at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)

at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)

at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)

at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)

at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)

at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()

at Microsoft.SharePoint.Deployment.SPImport.Run()

at sa.SharePoint.Sites.ImportExport.Form1.Import(String siteURL, String fileToImport)

at sa.SharePoint.Sites.ImportExport.Form1.Import()

I've ensured that all the conifguration values used by the application are added to web.config also.Do you have any clue?

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Sanjaya — Tue, 05 Aug 2008 21:46:53 GMT

Stefan,

I figured out that the error i 've posted in the last comment comes from my event receiver.

I wonder why the event receiver is receiving itemupdating events while the import is running when the feature for the event receiver is only installed but not activated.

How do i prevent the event receiver from receiving any events?

fyi, i have some documents in the document libraries on the target site.

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Wed, 06 Aug 2008 00:46:14 GMT

Hi Sanjaya,

import automatically activates all features which are activated on the source site collection.

Regarding suppressing: if you are using After events you can suppress them using SPImportSettings.SuppressAfterEvents = true;

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

William — Fri, 24 Oct 2008 17:43:08 GMT

Hi Stefan.

I'm working in a MCMS migration to MOSS 2007, and I have some problems with the process.

The most important process is the follow:

I run a migration process. The firts time this one is good, but, when I tried to make a incremental migration the follow error appears:

The required attribute 'Title' is missing.

What do you think about this?

Regards.

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Fri, 24 Oct 2008 18:19:53 GMT

Hi William,

please open a support case to get this analyzed.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Marc — Wed, 26 Nov 2008 04:03:13 GMT

If you are having problems with doing an import after a successful export then you need to make sure that in the ExportSettings.xml which is created on export that the FileLocation attribute points to where your export actually is.

I was getting "Unhandled Exception: System.ArgumentException: Value does not fall within the expected range." because I moved my export from prod to my dev box under a different directory.

Great series of posts btw!

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Wed, 26 Nov 2008 17:05:35 GMT

Hi Marc,

I haven't seen this issue.

Can you provide more insights about when this happend?

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

John — Wed, 04 Feb 2009 09:28:37 GMT

Stefan,thanks for a great post.

I'm hoping you can help with a problem we have at present.

We have succesfully done both a Full deployment and an Incremental deployment from DEV to TEST environments. The issue is that all the SSRS reports lose their data source connection reference. This can be fixed by remapping the DS link for a report via Manage Data Sources. The report will then run OK. The problem is that this needs to be manually repeated for All reports...any ideas.

The problem seems to be that all the (Shared)Data Connections have no dependant items after they are deployed to the destination.

Hope you can point us in the right direction.

Thanks

John

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Wed, 04 Feb 2009 10:40:13 GMT

Hi John,

this has not yet been reported before. Please open a support case with Microsoft to allow us to repro and analyze the issue.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Ajay — Thu, 16 Apr 2009 12:38:44 GMT

Hi Stefan,

I got the following error during incremental content deployment ""The object has been updated by another user since it was last fetched"".

As per your post you said that this can happen if destination is updated.

Now destination is updated as I have contact us form on site which people fill and it writes to the list.

I have removed the site containing the list from the incremental content deployment job.. do you think this is the right approach.

If destination gets updated than will incremental deployment fail??

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Thu, 16 Apr 2009 14:00:24 GMT

Hi Ajay,

please try to restart incremental deployment and check if the same error reoccurs.

If yes, then it is most likely not caused by the fact that you have authors working on the system.

Because the update would need to happen while the import occurs to cause this problem.

What is more common is that you have some features which register custom event receivers which fire during import.

If these event receivers update the database when items are imported you can get such problems.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Rohit — Thu, 30 Apr 2009 12:01:17 GMT

Hi Stefan,

Great series! Very detailed.

I am currently trying to find out if we can add our own messages also to the log files that get created at "LogFilePath" specified.

I have some custom logic in the "ObjectImported", "Completed" and other events, and want to log the success/failure/information from this code into the same logs which MOSS creates at "LogFilePath" specified for settings.

Thanks,

Rohit

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Thu, 30 Apr 2009 12:12:21 GMT

Hi Rohit,

interesting question!

Honestly I haven't looked into this till now.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Mike — Thu, 30 Apr 2009 19:48:32 GMT

Hi Stefan,

All of your posts are a great help!!

I have one question though for an error that I haven't seen much input from anyone about.

Doing the content deployment, the site comes to be about 56 MB but it's breaking the CAB files up into 4 separate ones. When it goes to the destination server it can't find the ExportSettings.xml file then gives a SystemIO error saying the file is not found.

How can one get around this?

Thanks,

Mike

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Thu, 30 Apr 2009 21:47:13 GMT

Hi Mike,

with 56 MB it will usually split up the cab into 6 pieces as 10 MB is the configured maximum.

It will only exceed this size if there are single files which cannot be compressed below 10 MB.

The error you mentioned indicates that not all the cab files are available on the import server.

Are you using regular content deployment or a custom solution?

If it is regular content deployment please check the status codes for DeployUpload.aspx in the IIS logs. This is used to upload the files.

If something went wrong you should see a status code different from 200.

Cheers,

Stefan

Bitácora de una migración SharePoint 2007

Manolo Herrera — Sat, 30 May 2009 07:40:15 GMT

SharePoint tiene un API para migrar contenido efectivo y poderoso.  Dentro del ensamblado Microsoft

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Sheetal — Thu, 09 Jul 2009 13:12:51 GMT

Hi Stefan,

Really a great post on Content Migration!!!

I have a problem here...I need to take a sub-site backup along with the content from one server and deploy it into other server...and the sub-site along with content is coming upto 25GB and when i run export command with cabsize 1024MB (as given in one site that this is the max limit we can give), its generating around 23 cab files. Now the problem is how do i run the import command with these 23 cab files...

The name i have given while exporting is -filename Export.cab

and its creating 23 cab files with name Export1.cab, Export2.cab,.....

Now which one do i need to give in the import command -filename

How do i deal with this problem??

Thanks,

Sheetal.

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Thu, 09 Jul 2009 13:30:17 GMT

Hi Sheetal,

ensure that all the files are in the same directory and then import the first file (Export.cab). It will also import the other files.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

steel — Wed, 26 Aug 2009 05:52:46 GMT

Hi Stefan,

Recently i used import/export API write a copy content web tool. When import a publishing web to other site collection which don't have exported publishing web, in my code in access the newly that publishing web and it throw NullReferenceException? but i try to sleep threed a few minutes and access again then it worked fine ? How can i access it without sleep?

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Wed, 26 Aug 2009 09:35:22 GMT

Hi Steel,

sounds to me as if the date/time in the different servers of your farms are not in sync.

I would recommend to use a timeserver to ensure that the servers are in sync.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

GillouX — Thu, 26 Nov 2009 19:28:47 GMT

Hi Stephan, I found your article really interesting and I would like to ask you a question.

I have the following requirement : I need to be able to copy a document to another site and still keeps the versions and metadata (from a administration custom page)

I see that using Sharepoint.Deployment I could do that but do you think that it's viable solution ? It's not too "heavy" ? or it's really not designed for this purpose ?

thx in advance

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Thu, 26 Nov 2009 19:46:39 GMT

Hi GillouX,

this API is designed to handle this scenario.

Cheers,

Stefan

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

GillouX — Tue, 08 Dec 2009 11:14:05 GMT

Hello Stepan,

I would like to know if it's possible to move a document to another site (SPWeb) while keeping its UniqueID?

this another site does not have the same structure as the source but the Document Library is created using the same list definition.

I've tried to set RetainObjectIdentity at true in the import settings but it does not seem to be so easy :D

thx in advance

re: Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

Stefan_Gossner — Tue, 08 Dec 2009 11:23:50 GMT

Hi GillouX,

no this is not possible.

Cheers,

Stefan