Background of problem
We are developing an extranet. It's primary purpose is to share pdf's and xls files with external customers. After content deployment, everything works as expected, except the pdf's and xls documents fail to import. I will respond as quickly as possible to any additional requests for background on the behavior.
Topology
We have an internal authoring environment and an external content deployment target outside the firewall. We set up content deployment between the two environments. The source site is based upon the team site site collection template.
Due Diligence
- I have confirmed that both the source and the target are at the same patch level for SharePoint and SQL 2008
- The target site was created leaving the site collection as "Choose template later"
- Our 2 custom solutions that provision the lists and styling were deployed to the target, but their features were not activated.
- The lists do not require content approval.
What works
When we run content deployment, the following work as expected:
- Custom features are activated
- Master pages, images, css are deployed
- Custom lists are created.
Issue
Everything behaves as expected, except none of the "meat" of the site (the actual document library items) is created.
Log
Below is the log section for both a master page and an example pdf. Note that they are nearly exactly the same (Names changed to protect the innocent).
Good:
[3/2/2011 9:24:08 AM] [ListItem] [Foo.Default.Master] Progress: Importing
[3/2/2011 9:24:08 AM] [ListItem] [Foo.Default.Master] Verbose: List URL: /_catalogs/masterpage
[3/2/2011 9:24:08 AM] [ListItem] [Foo.Default.Master] Progress: Importing Links
[3/2/2011 9:24:08 AM] [ListItem] [Foo.Default.Master] Verbose: Import 1 server-relative links.
Bad
[3/2/2011 9:24:08 AM] [ListItem] [ExampleDocument.pdf] Progress: Importing
[3/2/2011 9:24:08 AM] [ListItem] [ExampleDocument.pdf] Verbose: List URL: /Customer Reports
[3/2/2011 9:24:08 AM] [ListItem] [ExampleDocument.pdf] Progress: Importing Links
[3/2/2011 9:24:08 AM] [ListItem] [ExampleDocument.pdf] Verbose: Import 1 server-relative links.
We also received ~100 of these exceptions on the first run of content deployment, but the amount of errors do not correspond to the number of imported documents (~5000). Googling around a bit hints that this might not be the reason for our problems, but I'm putting it out there in case I'm wrong.
[3/2/2011 9:26:01 AM] Debug: at Microsoft.SharePoint.Deployment.ImportObjectManager.FixBrokenMvlInListItem(ListItemMvl brokenField)
at Microsoft.SharePoint.Deployment.ImportObjectManager.FixBrokenLookup(DeploymentLookupField brokenField)
...Peter