Version History | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Ok - I see - you are wondering why this log message appears in the log when you install a package. 

After searching - this error suggest that there is something in your package that is causing AEM to throw this error- its very hard to tell what the issue is without having access to the package.

It may be trying to reference a JCR node's prop that does not exist or something. 

Open a ticket and give the support people access to your package. This is about the only way to get to the bottom of this issue. 

8 replies

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

Check the logs - what does it state.

Here is a good community artilce on working wiht version history in AEM:

http://www.wemblog.com/2012/08/how-to-work-with-version-in-cq.html

Try following the instructions listed in this community article. 

narayanank84409
narayanank84409Author
Level 4
October 16, 2015

Thank you for the reply.

I will read it.

narayanank84409
narayanank84409Author
Level 4
October 16, 2015

16.05.2015 12:51:46.463 *WARN* [10.146.229.133 [1431795091288] POST /crx/packmgr/service.jsp HTTP/1.1] com.day.jcr.vault.fs.impl.io.DocViewSAXImporter error while checkout node (ignored) javax.jcr.ReferentialIntegrityException: Target node 36a0dc54-c432-459c-bc7e-c353c25baca3 of REFERENCE property does not exist

 

I checked the log, we got the error.

we checked , but that's version is not there in repository.

How we can fix this.

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

Are you using DAM assets and version data:

https://docs.adobe.com/docs/en/cq/5-6-1/dam/cq5_dam_version_management.html

If you are not talking about DAM assets - what nodes (and versions of nodes) are you referring to? I am trying to duplicate your issue. 

narayanank84409
narayanank84409Author
Level 4
October 16, 2015

Yes, we missed this node(36a0dc54-c432-459c-bc7e-c353c25baca3) in jcr:version storage 

But how it missed that we are trying to find root cause for this problem.

Any suggestion , how it may miss that node.

We will open support ticket too.

narayanank84409
narayanank84409Author
Level 4
October 16, 2015

We are not using any DAM assets.

We installed the package in QA environment and we seen this error. Package we have taken from our Int environment.

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

Ok - I see - you are wondering why this log message appears in the log when you install a package. 

After searching - this error suggest that there is something in your package that is causing AEM to throw this error- its very hard to tell what the issue is without having access to the package.

It may be trying to reference a JCR node's prop that does not exist or something. 

Open a ticket and give the support people access to your package. This is about the only way to get to the bottom of this issue. 

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

You ahve custom run modes right (seeing your other thread). THat may play a role. Yeah - open a ticket, give the support ppl that package, and tell them what the run modes are. They will need all of that to get to the bottom of this issue. 

Terms & ConditionsAccessibility statement

Loading footer...