Syncronization failure

Stephen Herz asked on September 28, 2016 18:41

Using Kentico v9

We have redesigned our site and are trying to export specific content from the old site to the new one. They are on the same version of Kentico. I could not figure out how to export only some content blocks so decided to use syncronization. Most of the content came over successfully but one page subtree throws an error when I try to sync it. The error is:

SyncServer.ServerError: Exception occurred: [SyncManager.PublishDocument]: Page node not found, please synchronize the page node first.

I can find no documentation on this error. I see many articled on the Parent node not found but the solutions do not fix my issue. Any help?

synchronization error

Recent Answers

Trevor Fayas answered on September 28, 2016 18:50

The error pretty much says "You can't publish something that doesn't exist." You may want to do a synchronize on the page itself (This will make a CREATE PAGE, then an PUBLISH DOCUMENT).

To do this use the Staging Module, then select the document and hit "Synchronize Current Page", or select a parent and "Synchronize Current SubTree". That should solve it!

1 votesVote for this answer Mark as a Correct answer

Stephen Herz answered on September 28, 2016 20:33

I selected a page and hit "Synchronize Current Page" but that's what gave me the error. I also tried to select the parent of this page and do "Synchronize Current SubTree." That synced all of the folders and content inside the parent except for the one node that is throwing the error. The page I am trying to sync is a regular Page (menu item) but it has child nodes that are of type Blog. Could that be the issue?

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on September 29, 2016 09:38

Hi,
Could you please check the DocumentID, DocumentGUID (CMS_Document table) and NodeID and NodeGUID (CMS_Tree) of the page in question as well as the parent node? IT looks like they do not match so the system cannot find the right parent for this node. This usually happens if there are changes made on the target server as well without the bi-directional staging setup.

0 votesVote for this answer Mark as a Correct answer

Stephen Herz answered on September 30, 2016 15:58

I was trying to use synchronization to copy content from one site to another, with each site having a totally different folder structure. I was trying to accomplish this as a way of exporting and importing content during a site redesign. I don't think sync is the proper way to accomplish this since the sites are so different. Thanks for your help.

0 votesVote for this answer Mark as a Correct answer

Jay McCormack answered on June 15, 2017 09:57 (last edited on June 15, 2017 09:58)

@juraj - I'm having this problem with a one way staging synch. It seems to be affecting many documents.

For one example document, in the dev environment the details are:
Node ID: 10393
Page ID: 10374
Node GUID: 03f5f36e-6b17-4934-8340-0681fd8e6ced
Page GUID: f4a5e798-60e7-4ebb-a1cc-5238cca7947d

and for the same document in test, the details are:
Node ID: 10414
Page ID: 10400
Node GUID: 03f5f36e-6b17-4934-8340-0681fd8e6ced
Page GUID: f4a5e798-60e7-4ebb-a1cc-5238cca7947d

Should I expect that the Node ID and Page ID are the same between both instances? Or does staging use the GUID to identify the items?

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on June 15, 2017 12:28

Hi,

The ID can be different - there is ID translation in place. So, the GUID is significant in this case and then also the position in the tree - the path. (and also the site is checked).

This issue can be caused if the page was moved to a different location on target or, if it is unpublished. Basically, there is some inconsistency between the DBs.

0 votesVote for this answer Mark as a Correct answer