E0302014f: The parent version of the item web.xml has another child on the trunk: Synchronization problem.
Article ID: 48769
Updated On:
Products
Issue/Introduction
During the Concurrent Merge process on a package in the Development state, the error message appears:
- E0302014f: The parent version of the item web.xml has another child on the trunk: Synchronization problem.
Checking the file, we found that there is a branch number like 22.2.1 listed in the package, but the history diagram does not show the previous version 22.1.1
Environment
Harvest Software Change Manager all versions
Resolution
A few users have checked-out and checked-in the same files several times in the Merge state. One of the users demoted the package from the Merge state to the Development state. But the Merge and Development states have different underlying data views, the Merge data view for the Merge state, and the Production data view for the Development state. If you click on the History Diagram, the later versions of these files are not visible in the Development state because they were checked-in in the Merge state. When the package was demoted to the Development state, this does not allow the later versions of these files to become "visible" in the Development state. You can prevent this problem by enabling dependency checking during the demote process.
A workaround for the problem is to "promote" the package from the Merge state to the Development state. By doing this, a copy of the correct version of the file is placed in the Development state, and subsequent attempts to check out or merge this file can be successful.
Additional Information
This situation will happen if you have a later trunk version that never "passed through" the state where you are doing the Concurrent Merge. For example, here is one scenario that can reproduce this error:
- In the Development state, check out a file (for example, README.TXT) for Concurrent Update into a package (for example, "MR- 000002"), make a change and check it in on the branch as version 0.1.1.
- Promote this package ("MR- 000002") to the Merge state and perform the Concurrent Merge on the package in that state, creating version 1 of the file (README.TXT).
- Back in the Development state, check out again the same file (README.TXT) for Concurrent Update into a second package (for example, "MR- 000003"), make a change and check it in on a new branch as version 0.2.1.
- While still in the Development state, perform the Concurrent Merge on the new package ("MR- 000003"). This produces the error message.
The "other child on the trunk" in this case is version 1 of the file in question (README.TXT) which never "passed through" the Development state where we were trying to do the second Concurrent Merge.
There might be other scenarios that would produce this, but what you're looking for is a later trunk version that's not visible in the data view of the state where you're trying to do the Concurrent Merge. The "Find Version" tool in Workbench can help you to locate all versions of an item to try and track it down.
Feedback
