Old Forums
Search:
Portal Engine Questions on portal engine and web parts.
Version 6.x > Portal Engine > SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first." View modes: 
User avatar
Member
Member
simon - 9/25/2012 3:28:39 AM
   
SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
"Dependent task 'Create document How it works' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."

There is no create document task in my sync list - how do I make it without deleting the node and re-doing it ?!?

'sync current subtree' does nothing. I cannot sync the entire subtree as there are tasks that we do not want pushed across yet.

Now i've just checked on the live site and its duplicated some content, not published others, others are so out of date. I want to just remove it all and re sync, but im sure im going to run into issues doing this.

When trying to sync the ones that are duplicated, I get the following message : "Cannot insert duplicate key row in object 'dbo.CMS_Tree' with unique index 'IX_CMS_Tree_NodeSiteID_NodeGUID'. The duplicate key value is (2, 3417c439-2fe7-4d87-a254-3aab2bfc10d9). "

If i delete one of the duplicate nodes, BOTH nodes are deleted.

considering the system makes a log of everything and then runs it in order im mystified as to why this is happening.

is there any way i can manually "sync", or is there some way i can rebuild the sync history to include the create option ???

this is ridiculous, any help is greatly appreciated.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 9/25/2012 3:40:58 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

What if you synchronize the parent document? Are all the parent documents in the path present on the target? The easiest way is deleting the node and re-syncrhonize it again since for some reason some inconsistence is in the DB. The same applies for the duplicate records in CMS_Tree table.

Do you remember what was done before this problems occurred? We are so far unable to reproduce these errors and other customers do not remember or have not replied to this question - it would be great to know the steps or changes made before this started to happen so we can find the cause.

Best regards,
Juraj Ondrus

User avatar
Member
Member
simon - 9/25/2012 4:37:08 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

Thanks for the quick response!

This has happened to us before, always when we duplicate content by copying it. These pages have been copied 2 times, so we can put versions with slightly different text on different urls. After copying and making the changes I went to staging module and synched the page templates/css/layouts etc ( all fine, no problems ), then went to the content tree and clicked "sync current subtree". it failed immediately, complaining about needing the create task synched first.

I've deleted the content on the live server and managed to get one of the copies across ( I just kept clicking "sync current sub tree" or "sync all" and eventually it worked ) , but the other two refuse to sync stating that i need to sync the create event first. Even a "sync current sub tree" fails!

At least I have one copy on live, at worse i can duplicate it and make the changes needed on the live server... but i'd rather not ;)

when you say "The easiest way is deleting the node and re-syncrhonize it again" how do i resync when the logs are gone ? is it "sync current sub tree" ??

if there is any more info or logs you need just ask, this is very damn frustrating and it would be good to get this fixed.

thanks for your help.

User avatar
Member
Member
simon - 9/26/2012 8:19:03 PM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
do you need any more information from me?

User avatar
Member
Member
simon - 10/2/2012 6:18:52 PM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
*bump*


would appreciate any help on this as i'm now manually updating both staging and live with many changes - as you can imagine this situation is not ideal

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 10/3/2012 1:20:49 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

I am sorry for the delay. We are working on this issue and it should be fixed soon. However, our replies on forums are not guaranteed and even though we try hard, there is not always time to reply on forums since answering tickets for paying customers has higher priority - you can use our support e-mail address to and we are answering the tickets within one business day.

Best regards,
Juraj Ondrus

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 10/4/2012 3:51:33 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

I just got reply from our dev team. They have made many tests according to your description and various combinations but they were unable to reproduce the issue. So, it is hard to find the cause. They have reviewed the staging code twice and they couldn't see anything what would cause it.

If you could observe some exact steps how to reproduce the issue, that would be much appreciated.

Best regards,
Juraj Ondrus

User avatar
Member
Member
jheavner-ce - 10/8/2012 3:35:32 PM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
My organization has had many of the same errors that the OP mentioned. We contacted support and never really got anywhere with an answer. We basically got to the point where we would delete content from the target and sync the parent node and then the subtree. This because a very painful solution when there are many documents under the item in question.

User avatar
Member
Member
simon - 10/9/2012 12:54:05 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

Thanks for the reply. I'll send this to support, so no need to reply here, but posting here for people reading along. I'll update the thread when i get a reply as I know other people have had this issue.

We managed to get around it by recreating the content on the server, but now one of my colleges has the same problem, on the same server. His steps were very similar:

create a document ( lets call it DOC ) in the root.
create a folder (FOLDER ) in the root
move DOC into FOLDER
edit DOC
create another folder inside FOLDER
put more documents in this folder.
go to staging module
select FOLDER
sync all

it will fail, but partially sync FOLDER.

going to the live server shows FOLDER is in 'edit' mode ( red/orange dot ). if FOLDER contained an image clicking on the image gives a server error that "attachment with GUID does not exist". Deleting FOLDER from the live server will refresh the page, remove the contents, but FOLDER will still exist. Deleting FOLDER again removes it.

This has only happened on moved or copied documents, and only on this install of kentico, which makes me think that perhaps something else is interfering in the sync. One thing ( which may not be related ) is that this server is the only server using MVT .

User avatar
Member
Member
simon - 10/9/2012 7:11:55 PM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
here's the response I got from support, I will be implementing one of them when we have time, and will report back on if this fixed the issue. hopefully this will help someone else suffering from this elusive problem

----------------------------------------------------------------

Hi,

Have you tried to delete the duplicates on the target server, make sure thate are no records with given GUID in the CMS_Tree table in the target DB and then re-synchronize them? This helpes all other customers - and they didn't report this issue again.

I tried to follow your steps described - three times and I also tried various other combinations and I am still unable to reproduce the issue. It seems that your DBs are not consistent. So, I would recommend doing what I mentioned above or create a backup of the source DB and restore it on the target to ensure the DBs are the same.
User avatar
Member
Member
scott_hancock-urmc.rochester - 10/22/2012 1:21:52 PM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
I've been getting this error also, when my users move files. The users publish a file, move it and then edit it. The synchronization fails on the publish step and then all the other steps fail. I just deleted the publish task and then it works fine. We only sync once a day so I thought maybe that was contributing to it.
Task type: PublishDocument
Task time: 10/18/2012 10:17:49 AM
NodeAliasPath: /childrens-hospital/giving/donors/miracle-makers/2010/howie
DocumentNamePath: /Golisano Children's Hospital/Giving to Golisano Children's Hospital/Meet Our Donors/Miracle Makers/2010/2010 Howie Jacobson

Task type: MoveDocument
Task time: 10/18/2012 10:24:01 AM
NodeAliasPath: /childrens-hospital/giving/donors/miracle-makers/howie
DocumentNamePath: /Golisano Children's Hospital/Giving to Golisano Children's Hospital/Meet Our Donors/Miracle Makers/2010 Howie Jacobson
AliasURLPath: NA

Task type: UpdateDocument
Task time: 10/18/2012 4:24:06 PM
NodeAliasPath: /childrens-hospital/giving/donors/miracle-makers/howie
DocumentNamePath: /Golisano Children's Hospital/Giving to Golisano Children's Hospital/Meet Our Donors/Miracle Makers/2010 Howie Jacobson
AliasURLPath: /childrens-hospital/giving/donors/miracle-makers/2010/howie
User avatar
Kentico Support
Kentico Support
kentico_jurajo - 10/24/2012 3:43:18 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

What is the exact version of the CMS you are using? I tried those steps on the v7 and I am not getting any errors. The tasks were created in the same order (except it was newly created document - so there was also the create task).

Is the workflow set for the destination too?
What are the tasks data and are there any other tasks for given document?

Best regards,
Juraj Ondrus

User avatar
Member
Member
scott_hancock-urmc.rochester - 10/25/2012 7:52:38 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
What is the exact version of the CMS you are using?
v.6.0.46

Is the workflow set for the destination too?
Yes

What are the tasks data and are there any other tasks for given document?
Not sure what task data you want. The only tasks are the ones I mentioned in my earlier post.

Thanks,
Scott

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 10/30/2012 3:07:48 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

I meant the task data if you will click on the icon to view task data before synchronizing the task - are there all the updates you have made? Are the IDs/GUIDs matching the target?

Best regards,
Juraj Ondrus

User avatar
Member
Member
scott_hancock-urmc.rochester - 10/31/2012 1:14:21 PM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

The data looks fine. I just got some more of these errors this morning. On 2 different files there were 2 moves and and update. The 2 moves failed because it couldn't find the parent and the update didn't work because the moves had failed. When I looked at the target server though, the files had been moved. So I just deleted the move tasks and the update task ran successfully.
Task type: MoveDocument
Task time: 10/30/2012 9:49:56 AM
NodeAliasPath: /highland/quality-of-healthcare/Orthopaedic-Surgery/knee-replacement
DocumentNamePath: /Highland/DEV Quality of Healthcare/Orthopaedic Surgery/Knee Replacement
AliasURLPath: NA

Task type: MoveDocument
Task time: 10/30/2012 9:50:22 AM
NodeAliasPath: /highland/quality-of-healthcare/knee-replacement
DocumentNamePath: /Highland/DEV Quality of Care/Knee Replacement
AliasURLPath: NA

Task type: UpdateDocument
Task time: 10/30/2012 9:52:17 AM
NodeAliasPath: /highland/quality-of-healthcare/knee-replacement
DocumentNamePath: /Highland/DEV Quality of Care/Knee Replacement
AliasURLPath:
/highland/quality-of-healthcare/Hospital-Ratings/knee-replacement 10/28/2012 5:10:06 PM
/highland/quality-of-healthcare/Orthopaedic-Surgery/knee-replacement 10/25/2012 1:35:08 PM
/highland/quality-of-healthcare/Orthopaedic-Surgery/hip-replacement/knee-replacement 10/22/2012 7:24:42 PM
/highland/quality-of-healthcare/knee-replacement 10/22/2012 7:24:30 PM

-------------------------------------------------------
Task type: MoveDocument
Task time: 10/30/2012 9:50:03 AM
NodeAliasPath: /highland/quality-of-healthcare/Orthopaedic-Surgery/hip-replacement
DocumentNamePath: /Highland/DEV Quality of Healthcare/Orthopaedic Surgery/Hip Replacement
AliasURLPath:

Task type: MoveDocument
Task time: 10/30/2012 9:50:29 AM
NodeAliasPath: /highland/quality-of-healthcare/hip-replacement
DocumentNamePath: /Highland/DEV Quality of Care/Hip Replacement
AliasURLPath:

Task type: UpdateDocument
Task time: 10/30/2012 9:52:17 AM
NodeAliasPath: /highland/quality-of-healthcare/hip-replacement
DocumentNamePath: /Highland/DEV Quality of Care/Hip Replacement
AliasURLPath:
/highland/quality-of-healthcare/Hospital-Ratings/hip-replacement 10/28/2012 5:10:18 PM
/highland/quality-of-healthcare/Orthopaedic-Surgery/hip-replacement 10/25/2012 1:34:51 PM
/highland/quality-of-healthcare/hip-replacement 10/22/2012 7:24:24 PM
User avatar
Kentico Support
Kentico Support
kentico_jurajo - 11/1/2012 6:14:44 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
hi,

I am still unable to reproduce the issue - following your description. what is the sequence of synchronizing the tasks?

It seems to me that there is some inconsistence in the target DB.

Best regards,
Juraj Ondrus

User avatar
Member
Member
scott_hancock-urmc.rochester - 11/1/2012 10:08:25 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
I just recreated the issue using my dev machine and a different server. Here are the steps I followed.

Using v6.0.54 on both servers with no versioning or workflow and with no staging tasks pending.

1. Create /Sync Test
2. Create /Sync Test/Page1
3. Create /Sync Test/Page2
4. Create /Sync Test/Page3
5. Create /Sync Test/Page3/PageA
6. Create /Sync Test/Page3/PageB
7. Create /Sync Test/Page3/PageC
8. Create /Sync Target
9. Add some text to all of the pages.
10. Click and Drag /Sync Test/Page3 (and all it's children) to /Sync Target.
11. Click and Drag /Sync Test/Page 1 to /.
12. Click and Drag /Sync Test/Page2 to /Sync Target.
13. Delete /Sync Test.
14. Go to CMSDesk -> Tools -> Staging and choose synchronize all.

The only tasks that succeed are:
Create /Sync Test
Create /Sync Target
Delete /Sync Test.

On my target server, only /Sync Target is created. I don't know if the other create and delete tasks actually worked, they just aren't listed in the
pending tasks anymore.

This is the partial output of the Synchronization log.
Synchronizing 'Move document Page2' task
Dependent task 'Create document Page1' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Move document Page1' task
Dependent task 'Create document Page3' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Move document Page3' task
Dependent task 'Create document PageB' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Update document PageB' task
Dependent task 'Create document PageA' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Update document PageA' task
Dependent task 'Create document Page3' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Update document Page3' task
Dependent task 'Create document Page1' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Update document Page1' task
Dependent task 'Create document Page2' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Update document Page2' task
Dependent task 'Create document PageC' failed:Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Update document PageC' task
Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Create document PageC' task
Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Create document PageB' task
Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Create document PageA' task
Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Create document Page3' task
Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Create document Page2' task
Synchronization server error: Exception occurred: SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first.
Synchronizing 'Create document Page1' task
Synchronizing the tasks ...

Thanks,
Scott

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 11/6/2012 4:13:18 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi Scott,

Thank you for the information, much appreciated. I think I have found the scenario based on this information.

I have submitted it to our developers to fix it. I hope it will be fixed in this week's hotfix.

I am sorry for this inconvenience.

Best regards,
Juraj Ondrus

User avatar
Member
Member
scott_hancock-urmc.rochester - 11/26/2012 1:33:06 PM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

I noticed that they fixed this for version 7.0.7, a couple of weeks ago, do you have any idea when they will fix it in v6.

Thanks,
Scott

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 11/28/2012 1:14:24 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

I am sorry for this inconvenience but the bugs are being fixed for latest released version only. You will need to upgrade to v7 in order to fix this issue.

Best regards,
Juraj Ondrus

User avatar
Member
Member
scott_hancock-urmc.rochester - 11/28/2012 8:32:10 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
While I understand the need to focus resources on the latest version, this is a serious bug that affects us now. Like most institutions, we can't just upgrade the minute a new version comes out. We wait for the inevitable initial flood of bugs in a new version to be fixed. In that time we regression test our code in the new system. So again, like most large institutions we will have to wait at least 6 months before will perform an upgrade. On top of that, we are in the middle of a staged migration of our website (11,000+ pages) into Kentico that will take several more months so we don't have time to deal with an upgrade.

Scott

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 11/28/2012 8:57:47 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

I understand - however applying hotfix is basically the same process and in case of customizations you need to merge the changes anyway. In upgrade there might be more files that needs to be changed, but the process is still the same.

Best regards,
Juraj Ondrus

User avatar
Member
Member
scott_hancock-urmc.rochester - 11/28/2012 9:11:03 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
It may be easy to do the upgrade, but as I said before, there are other factors that keep us from upgrading immediately. Including seeing if we have to update our training classes and materials and inform all of our current editors (50 now and increasing) of the changes.

In the meantime, I have to spend this morning dealing with the issues this bug causes instead of doing productive work.

Scott

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 11/28/2012 10:02:11 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Hi,

I understand. you have some red tape and we have some red tape too. We have this policy for several years now too. However, imagine that there were no hotfixes at all and you would have to wait e.g. a year until a new version is released?

This gives you the option to apply the hotfix just with one condition - have the actual version.

Best regards,
Juraj Ondrus

User avatar
Member
Member
scott_hancock-urmc.rochester - 11/29/2012 8:28:12 AM
   
RE:SyncHelper.ServerError: Parent node does not exist, please synchronize parent node first."
Ok,

What is the policy exactly? I wasn't aware of it and I'll need to communicate this to our management team.

Scott

1 2
Top