Incremental Deployment fail - cannot import because parent /site does not exist.

Question

Hi guys,

The below issue refers to a MOSS 2007 environment with an Authoring and Production Web Application

I have a content deployment issue where by I get the following error.

Content deployment job 'Remote import job for job with sourceID = <id>' failed.The exception thrown was 'Microsoft.SharePoint.SPException' : 'The file Pages/Forms/Page Layout cannot be imported because its parent web /site does not exist.'

This error occurred when I deleted the Production site and tried to redeploy from the Authoring site. The site deletion was neccessary because Production had the site displaying incorrectly, while Authoring is displaying correctly.

Anyone can provide any insight to this error?

Mark Huynh

Answer 1

An incremental deployment will only deploy content that has changed since the last deployment job. If you have deleted the Production site, the entire site needs to be redeployed, since there is no longer any content to compare against. You should run a full deployment job, not an incremental job. See Plan content deployment for more information.

-Cern McAtee

Technical Writer, IT Pro
Microsoft Office SharePoint Server

Answer 2

Thanks Cern for your reply.

What you said makes sense. However, I prefer not to run a full deployment job if I can. Consider the following below:

Configuring content deployment

Configure content deployment between two server farms by using the following steps:

1. On the destination server farm, create an empty site collection based on the Blank Site template to receive the initial deployment job.

Will it be possible to recreate the deleted site on production as a blank site and then perform an incremental deploy?


Mark Huynh

Answer 3

Hi Mark,

Content Deployment Jobs andd Paths will be successful only if the content deployment is one way i.e from the Authoring to the Production.

Here, you have deleted a site in Production. Authoring farm doesn't know about this.

Incase of incremental deployment: MOSS content deployment maintains a timestamp value and deploys the contents modified in the AUTHORING farm that got changed after the last deployment. As the AUTHORING farm has no clue oin the changes that you have done in the Production farm, you will not get what you expect.

I feel a full deployment would be required.

Hope this helps you

---

Raghavan

Answer 4

Hi,

You will need to create a blank site where the site was when you deleted it and then run a full content deployment for that site collection.  You can't run an incremental deployment as that is only items which have changed, it will be expecting lists etc to already exist.

Hope this helps

Dave

---

My SharePoint Blog - http://www.davehunter.co.uk/blog