SharePoint Content Deployment Wizard

New Post: Lookup field trouble after content deployment

ThomasLund — Fri, 15 Aug 2008 06:56:42 GMT

Hello all

I have a problem I have been trying to track down for a couple of days to no avail. I'm hoping any of you can help. It's a WSS site.
I am aware that this is probably an underlying problem in WSS and not Content Deployment Wizard, but this is probably the best place to find people who noticed this problem. Copy from here:
http://forums.technet.microsoft.com/en-US/sharepointgeneral/thread/8a276294-6fc6-46df-883d-e4cf792675d2 just in case the answer pops up there.

I am not yet a seasoned Sharepointer.

I have tried to do a content deployment of a simple site I have made. It was done entirely without code or CAML. I will give a simple example of what will fail.

If I make a site, a custom list named BlablaLookup, a site column named Lookuptest and then add the site column to a content type I can call CTtest. It inherits from "document".
Then I make a doclib and use that CT as the only one. I can then make a new word file using the "new" button and it works well. The Document Information Panel fills out the lookup list field.

I then export the content using "Content Deployment Wizard".

I make a new web application and create a blank site using stsadm -o createsite so that its truly empty.
I import using the retain object ID functionality.

Now if I try to make a new document it will fail miserably:

Error: "Document information panel contacted a data source but failed to receive data. The form will load without the requested data"

ErrorMessage:

The query cannot be run for the following DataObject: list_8ab94089-4d3f-4cbe-9df1-bc14dee5563f

Document Information Panel cannot run the specified query.

The SOAP response indicates that an error occurred on the server:

Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.

<detail><errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">The system cannot find the file specified. (Exception from HRESULT: 0x80070002)</errorstring></detail>

I am aware about object IDs being a problem with lookup lists, but using SharePoint Manager from CodePlex I can see that it actually uses the correct ListId, and WebId after the import.

What difference I saw on the lookup field before and after the import was the schemaXML for the field. Here it references the old webid in one place.

<Field Type="Lookup" DisplayName="Ekspedient" Required="TRUE" List="8ab94089-4d3f-4cbe-9df1-bc14dee5563f" WebId="936fac38-baed-4bc5-8525-178d5670413d" ShowField="Title" UnlimitedLengthInDocumentLibrary="FALSE" Group="BPT" ID="{9457722f-8c1b-48e1-be28-f4f1054dff9c}" SourceID="{6b19496b-1425-4afe-80af-bab477c39c19}" StaticName="Ekspedient" Name="Ekspedient" Version="1" Customization="" ColName="int1" RowOrdinal="0" />

Ignore the different names etc please :)
This is the old and incorrect webid:6b19496b-1425-4afe-80af-bab477c39c19

I dont know if this matters, but its the only difference I have seen.

I can try and make a new doclib on the imported site and use the "broken CT" and then I get another error:

Error:

The Document Information Panel was unable to load. The document will continue to open. For more information, contact your system administrator.

ErrorMessages:

Document Information Panel cannot create a new, blank form.

Document Information Panel cannot open the form. To fix this problem, contact your system administrator.

Form template: http://bptdev:11111/proppanel.xsn

The following DataObject either cannot be created or cannot be initialized: list_AF7999E1-9844-4751-9EE1-6B285B3E2588

Document Information Panel cannot add the following object to the DataObjects collection: list_AF7999E1-9844-4751-9EE1-6B285B3E2588

list_AF7999E1-9844-4751-9EE1-6B285B3E2588 could not be added to the DataObjects collection.

The following item already exists in the collection: list_AF7999E1-9844-4751-9EE1-6B285B3E2588

Sorry for the long question, but this problem is really hard for me to get rid of. This is probably a

Best Regards,
Thomas

Edit: Removed weird Word formatting from copy/paste

New Post: Great Tool! Thank you.

jxs0900 — Fri, 08 Aug 2008 20:11:20 GMT

I wish the source was available. I would love to learn how you go about all of this. If I only had a tool that could look into the exe. ;)

New Post: Export and Import 'rules'

CharlesW — Sat, 02 Aug 2008 17:32:27 GMT

I am trying to understand the Export and Import 'rules' for SharePoint using Document Checkin workflow.

For Export, it looks like the latest published file is exported. i.e. if you don't approve the latest file, it may be exporting the wrong desired file.
(It may help to identify in the list what version and/of date/time of the file is being exported.)

For Import, I am trying to import files that are in use. Do the files have to be checked out?
(I get an error saying that the file is in use and cannot be deleted - I used the Overwrite option.)

New Post: Win Form changes

CharlesW — Sat, 02 Aug 2008 17:28:07 GMT

Hi Chris - Great tool. Here are a couple of comments re: layout of the Win Form.
Select content for export step shows two GroupBoxes, Export Content and Selected Items
1. Suggest that you use a Splitter Panel on the Form. Put Export Content in top panel of splitter and Selected Items in bottom panel of splitter. Ensure that the controls are Docked as Fill.
- Why? I find it difficult to see what I am looking for in a list of 10 items in each control. By using a Splitter panel, each Group Box can be expanded in size to see more.
2. Suggest that the list of files in the Export Content folders be arranged aphabetically.
- Why? I am looking for a few files in a loooong list. It takes some time to realize where they are.

New Post: Is there a command line version?

Patrick44 — Thu, 24 Jul 2008 13:55:31 GMT

Need to script out moving many sites around and was wondering if there is a command line version of this floating around. If not all the features found here, one that will let me exclude subsites at the very least when I do a export/import.

Thanks,
Patrick

New Post: Duplicate Columns in Pages Library ->Content Type

sudhakarn — Sat, 19 Jul 2008 14:55:03 GMT

In the site collection ( Publishing portal), created a top level site (source1) based on Publishing Template. No new pages created except the default page, which got approved.

Ran the tool to export the web (source1) ( descendants=content, excludedependancy=true). No issues wsith this.

Imported the web to a target Top level site (target1) in the same site collection. Import goes through. However after import, if you go to target1 View All Site Content -> Pages-> Doc Lib Settings-> "Page" content type, you would notice that "Rollup Image" site columns appears in duplicate. This issue you could see even in Article page and WelCome Page content types ( sometimes different field such as Image Caption, SummaryLinks etc)

(Above said is env with WSS SP1, MOSS SP1 installed)

New Post: 64Bit Version

danny_zeegers — Fri, 11 Jul 2008 22:36:10 GMT

I downloaded the file and a run the executable.
I downloaded the version of 22/06/2008
Click right and choose run as administrator
at our site no problem
We run the program after unzip from the desktop
i took two minutes be4 it started

Danny

New Post: 64Bit Version

anava — Fri, 11 Jul 2008 15:19:07 GMT

When I try to install in my dev server, I got following error messages

"Windows Cannot access the specified device, path, or file.
You may not have the appropriate permission to access the item."

Eventhough, I am using administrator account ,I got this message. I am able to install in 32bit machine with out any issues.

Could you please let me know, how you installed in 64bit server?

New Post: 64Bit Version

danny_zeegers — Fri, 11 Jul 2008 14:01:16 GMT

It works on 64 bit but you need to wait a long time b4 it starts

Danny

Commented Issue: Error while importing the webapplication from Windows2003 32 bit server environment to Windows 2003 64bit environment

anava — Thu, 10 Jul 2008 18:32:49 GMT

hi,
I was sucessfully able to export the web application on the Windows 2003 32 bit environment using Sharepoint content deployment wizard but when i tried to import the .CMP file at the Windows 2003 64 bit server it gave error as Access Denied.Please help me on this issue.
Comments: ** Comment from web user: anava **

How did you install this application in 64bit environment?

New Post: 64Bit Version

anava — Thu, 10 Jul 2008 18:31:54 GMT

Do you have 64Bit Version of this application?

New Post: Error on content deployment

chrisobrien — Sun, 06 Jul 2008 16:25:10 GMT

Hi Pascal,

This is an error with the underlying SharePoint API which should resolve itself if you install the the post-SP1 Content Deployment hotfixes. Andrew Connell points to the description in this post:

KB's are now out for the two content migration/deployment QFE's recently released

HTH,

Chris.

Created Issue: Import Documents

dquilgars — Fri, 04 Jul 2008 14:31:57 GMT

I have a site template where I have only one library with a new content type by default.

When I export only the documents I have a problem to import them on a similar site template implements.

It imports : Importing Folder /sites/proto5/Shared Documents/Forms/Document.

But I didn't choose it, I choose only the documents in SHared Documents but I didn't choose the folder forms.
When it's importing I lost all the fields properties in the edit form but not in the columns.

When I retract this line in the manifest, I obtain all the informations correctly. So why did i obtain this line?
Have you an idea?

Thanks
Dominique

New Post: Error on content deployment

pascal_paradis — Mon, 30 Jun 2008 20:03:13 GMT

Hi,

I'm new using this tool and i'm giving it a quick tryout.

I have currently an error when importing my content into another empty sharepoint list.

Here is a revelant snippet of the import log :

[6/30/2008 3:55:08 PM]: Progress: De-Serializing Objects to Database.
[6/30/2008 3:55:08 PM]: Progress: Importing Folder /sites/content/Lists/Forum Direction.
[6/30/2008 3:55:08 PM]: FatalError: Value does not fall within the expected range.
   at Microsoft.SharePoint.SPWeb.GetWebRelativeUrlFromUrl(String strUrl, Boolean includeQueryString, Boolean canonicalizeUrl)
   at Microsoft.SharePoint.SPWeb.GetWebRelativeUrlFromUrl(String strUrl)
   at Microsoft.SharePoint.Deployment.FolderSerializer.GetFolderUrl(Guid folderId, String folderUrl, Guid folderParentId, Guid listId, SPWeb parentWeb, ImportObjectManager objectManager, Boolean checkTargetUrl)
   at Microsoft.SharePoint.Deployment.FolderSerializer.GetFolderUrl(Guid folderId, String folderUrl, Guid folderParentId, Guid listId, SPWeb parentWeb, ImportObjectManager objectManager)
   at Microsoft.SharePoint.Deployment.FolderSerializer.GetFolder(SerializationInfoHelper infoHelper, SPWeb parentWeb, ImportObjectManager objectManager)
   at Microsoft.SharePoint.Deployment.FolderSerializer.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()
[6/30/2008 3:55:08 PM]: Progress: Import Completed.
[6/30/2008 3:55:08 PM]: Finish Time: 6/30/2008 3:55:08 PM.
[6/30/2008 3:55:08 PM]: Completed with 0 warnings.
[6/30/2008 3:55:08 PM]: Completed with 1 errors.

Anyone with clues?

Thanks a lot!

Created Issue: Error while importing the webapplication from Windows2003 32 bit server environment to Windows 2003 64bit environment

shekhar_samle — Mon, 23 Jun 2008 09:37:26 GMT

Updated Wiki: Home

chrisobrien — Sun, 22 Jun 2008 19:39:23 GMT

Project Description

UPDATE: Release 1.0 version released 22 June 2008 - see Release 1.0 page for release notes

The SharePoint Content Deployment Wizard is a tool for SharePoint 2007 which provides the means to deploy the following content:

- site collections
- webs
- lists
- folders
- list items (including files)

Content is exported using the Content Migration API (PRIME) as a .cmp file (Content Migration Package) which can be copied to other servers for import. Unlike the out-of-the-box tools, the Wizard allows *granular* selection of content via a treeview.

The two screenshots which probably illustrate the concept of the tool best are:

Export selection screen:

Import settings screen:

N.B. The import operation overwrites your site data, always take a backup before importing.

More details (taken from readme)

Usage notes

The tool must be installed locally on the server which hosts the site
Site URL - enter using format http://source.test.dev
Import web URL - enter using format http://target.com/targetweb
See 'permissions' note lower down

Import/Export characteristics

Since the Content Migration API is used, imports/exports have the following characteristics:

dependencies of selected content (e.g. referenced CSS files, master pages) are automatically included in the export - check 'Exclude dependencies of selected objects' to disable this
all required content types, columns etc. are automatically included in the export
in contrast to STSADM export, it is possible to retain GUIDs during deployment (where objects are not being reparented) - check 'Retain object IDs and locations' to enable this
no filesystem files (assemblies, SharePoint Solutions/Features etc.) are deployed - these must already be present on the target for the import to succeed)
the following content does not get captured by the Content Migration API - alerts, audit trail, change log history, recycle-bin items, workflow tasks/state

Reparenting

Reparenting of objects such as webs and lists is possible with the following usage on the import:

- enter the URL for the target web in the 'Import web URL' textbox
- ensure 'Retain object IDs and locations' is not checked

Permissions

The Content Migration API (PRIME) is used to package the content as a .cmp file, which can be copied to another
server for import. The application MUST be run from the SharePoint server(s), and MUST be run under the context
of an account which has appropriate SharePoint permissions - currently the way to specify an alternative user
to the currently-logged on user is by using the 'Run as..' feature in Windows 2003 (right-click on the .exe and
select 'Run as..').

See my blog post 'Introducing the SharePoint Content Deployment Wizard' for more screenshots and information - http://www.sharepointnutsandbolts.com/2007/12/introducing-sharepoint-content.html

Chris O'Brien
http://feeds.feedburner.com/ChrisObrien

Updated Wiki: Home

chrisobrien — Sun, 22 Jun 2008 19:30:51 GMT

The tool must be installed locally on the server which hosts the site
Site URL - enter using format http://source.test.dev
Import web URL - enter using format http://target.com/targetweb
See 'permissions' note lower down

Import/Export characteristics

Since the Content Migration API is used, imports/exports have the following characteristics:

dependencies of selected content (e.g. referenced CSS files, master pages) are automatically included in the export - check 'Exclude dependencies of selected objects' to disable this
all required content types, columns etc. are automatically included in the export
in contrast to STSADM export, it is possible to retain GUIDs during deployment (where objects are not being reparented) - check 'Retain object IDs and locations' to enable this
no filesystem files (assemblies, SharePoint Solutions/Features etc.) are deployed - these must already be present on the target for the import to succeed)
the following content does not get captured by the Content Migration API - alerts, audit trail, change log history, recycle-bin items, workflow tasks/state

Reparenting

Reparenting of objects such as webs and lists is possible with the following usage on the import:

- enter the URL for the target web in the 'Import web URL' textbox
- ensure 'Retain object IDs and locations' is not checked

Permissions

The Content Migration API (PRIME) is used to package the content as a .cmp file, which can be copied to another
server for import. The application MUST be run from the SharePoint server(s), and MUST be run under the context
of an account which has appropriate SharePoint permissions - currently the way to specify an alternative user
to the currently-logged on user is by using the 'Run as..' feature in Windows 2003 (right-click on the .exe and
select 'Run as..').

See my blog post 'Introducing the SharePoint Content Deployment Wizard' for more screenshots and information - http://sharepointnutsandbolts.blogspot.com/2007/12/introducing-sharepoint-content.html

Chris O'Brien
http://feeds.feedburner.com/ChrisObrien

UPDATED RELEASE: Release 1.0 (Jun 22, 2008)

Sun, 22 Jun 2008 19:28:56 GMT

This release adds only minor changes to beta 2, since this codebase has now been proven to be stable. Additions:

ability to modify which lists are filtered out of the treeview. Generally only 'system'-type lists are hidden, but on occasion you may want to 'unhide' some lists e.g. 'Variation Labels' and 'Relationships List' lists if you are using variations. See readme.txt for details.
minor bug fixes e.g. .cmp file now correctly saved with extension if a period (.) is present in your chosen filename, validation to prevent child objects being added from treeview when parent site collection already added

RELEASED: Release 1.0 (Jun 22, 2008)

Sun, 22 Jun 2008 19:28:56 GMT

This release adds only minor changes to beta 2, since this codebase has now been proven to be stable. Additions:

ability to modify which lists are filtered out of the treeview. Generally only 'system'-type lists are hidden, but on occasion you may want to 'unhide' some lists e.g. 'Variation Labels' and 'Relationships List' lists if you are using variations. See readme.txt for details.
minor bug fixes e.g. .cmp file now correctly saved with extension if a period (.) is present in your chosen filename, validation to prevent child objects being added from treeview when parent site collection already added

CREATED RELEASE: Release 1.0 (Jun 22, 2008)

Sun, 22 Jun 2008 19:26:03 GMT

This release adds only minor changes to beta 2, since this codebase has now been proven to be stable. Additions:

ability to modify which lists exist on your site but are not shown in the treeview. Generally only 'system'-type lists

are hidden, but on occasion you may want to 'unhide' some lists e.g. 'Variation Labels' and 'Relationships List' lists if you are using
variations. To do this add an appSettings key in the application config file named 'ListsNotForExport' and specify a comma-separated
list of the lists you wish to hide. The default value (if no override found in config) to use as your starting point is:

Cache Profiles, Content and Structure Reports, Converted Forms, Long Running Operation Status, Notification List, Quick Deploy Items,
Relationships List, Reporting Metadata, Reporting Templates, User Information List, Variation Labels,Workflows, Workflow Tasks,
Workflow History, fpdatasources

minor bug fixes e.g. .cmp file now correctly saved with extension if a period (.) is present in your chosen filename, validation to

prevent child objects being added from treeview when parent site collection already added