Skip to main content
chetanvajre2014
Level 4
Mar 19, 2016 3:21 PM UTC
Solved

DeviceIdentification property errror

We are getting this error in our logs causing the page to load slowly

Could not find a jcr:content/cq:deviceIdentificationMode property for page /content/imf/en after scanning all parents. Giving up.

 

Does this mean we need to have this for partent node somewhere?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
kautuk_sahni
kautuk_sahniAccepted solution
Level 9
Mar 21, 2016 4:43 AM UTC

Hi

Please have a look at this forum post :- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__iqaa-hi_friends_iamn.html

Here also one of the user faced this problem (can look into the comments).

//You could re-check replication agent if it is pointing to your expected publish server. Also, verify if all replication stuff are stuck in replication queue.

 

I hope this could be some help to you.

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
View in thread

3 replies

smacdonald2008
smacdonald2008
Level 10
Mar 19, 2016 3:42 PM UTC

What are you doing when you get this error. Happening on pub?

Translate
chetanvajre2014Author
Level 4
Mar 21, 2016 12:07 AM UTC

Happens only on publisher. If I add that node of type string, it starts breaking other parts of code.

Translate
kautuk_sahni
kautuk_sahniAccepted solution
Level 9
Mar 21, 2016 4:43 AM UTC

Hi

Please have a look at this forum post :- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__iqaa-hi_friends_iamn.html

Here also one of the user faced this problem (can look into the comments).

//You could re-check replication agent if it is pointing to your expected publish server. Also, verify if all replication stuff are stuck in replication queue.

 

I hope this could be some help to you.

Thanks and Regards

Kautuk Sahni

Translate
Kautuk Sahni
Terms & ConditionsAccessibility statement

Loading footer...