Staging failure

Louise O'Hara asked on December 18, 2015 16:49

I have recently restructed documents within the content tree (moved, added linked documents, edited). This has been completed on the acceptance server and now needs deployed to production. Staging has been set up between the two sites however when I synchronize the changes only some of the documents transfer to the production environment.

The errors are a mix of the following:

Dependent task 'Create linked document Target Discovery & Validation' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Original node for linked document does not exist, please synchronize the original node first.

Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.

I have tried to sync the parent node using 'synchonize current document' and in most cases they sync successfully however when I then sync the child document I get the same failure message "parent node does not exist".

Could you advise a resolution to this or another method of transferring a section of the content tree from acceptance to production.

The site is on Kentico v7

Regards Louise

Recent Answers

Roman Hutnyk answered on December 18, 2015 17:01 (last edited on December 18, 2015 17:02)

I've seen that issue many times, especially, when you move thing around.

I usually delete all those staging tasks, that failed, navigate appropriate pages under the Documents tab and sync them manually either one by one, if they are in different locations, or all at once, if they are stored under the same parent.

1 votesVote for this answer Mark as a Correct answer

Louise O'Hara answered on December 18, 2015 17:33

Hi Roman

I have tried that but no joy I still get the parent node does not exist error

Louise

0 votesVote for this answer Mark as a Correct answer

Roman Hutnyk answered on December 18, 2015 17:53

Just want to double check: have you removed all failed staging task? - This is the key.

1 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on December 21, 2015 09:30

Hi,
I believe you have already seen the troubleshooting staging documentation.

Could you please check the GUIDs in CMS_Node and CMS_Document tables in both databases and check that the records are the same for the node in the failed task as well as for all its parents?

0 votesVote for this answer Mark as a Correct answer