Expand my Community achievements bar.

SOLVED

Unable to install workflow package from 6.0 to 6.1

Avatar

Level 4

Hi,

We are trying to migrate workflow packages from 6.0 to 6.1 and getting the following error while installing

Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakConstraint0030: Uniqueness constraint violated at path [/] for one of the property in [jcr:uuid] having value 3ed8a5c9-e095-4e9b-aeb0-98e9uss7

We were not able to find the above uuid in the target system?

Any help or pointers would be highly appreciated.

Thanks,

Anil

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

All this exception means is that this jcr:uuid already exists in the CRX.

Have a look here[1] 

Quote:

There was one workflow model xml in the package which was having hardcoded jcr:uuid value. I removed that jcr:uuid manually from the XML and reinstalled the package successfully. The uuid value in the XML was conflicting with one of the existing node IDs in the CRX. 

[1] http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

Regards,

Peter

View solution in original post

3 Replies

Avatar

Community Advisor

The exception means that you are trying to create two child nodes with exactly same node jcr:uuid under one parent.

Check the data you are trying to import may be it contains duplicate node definition somewhere(most likely .content.xml)

Regards,

Peter

Avatar

Level 4

PuzanovsP wrote...

The exception means that you are trying to create two child nodes with exactly same node jcr:uuid under one parent.

Check the data you are trying to import may be it contains duplicate node definition somewhere(most likely .content.xml)

Regards,

Peter

 

Thanks PuzanovsP,

Would that mean that what we are trying to import already exists? If that is the case then why don't we see the workflows in 6.1 as it is an inplace upgraded environment.

Regards,

Anil

Avatar

Correct answer by
Community Advisor

All this exception means is that this jcr:uuid already exists in the CRX.

Have a look here[1] 

Quote:

There was one workflow model xml in the package which was having hardcoded jcr:uuid value. I removed that jcr:uuid manually from the XML and reinstalled the package successfully. The uuid value in the XML was conflicting with one of the existing node IDs in the CRX. 

[1] http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

Regards,

Peter