Missing user mappings for experience fragment service, ERROR messages in log | Community
Skip to main content
New Participant
April 28, 2020
Solved

Missing user mappings for experience fragment service, ERROR messages in log

  • April 28, 2020
  • 1 reply
  • 4222 views

hi folks, I get hundreds of these error messages during authoring and I don't even use experience fragments!  I tried to get rid of them by adding the service user mapping for experience-fragments-service via the console configMgr, which worked fine. However my attempts to do it via a conf file failed.  The package deployed fine, but only some other pre-existing experience-fragments user mappings showed up in the system console, and the error messages resumed. Maybe it is because it is an internal feature that I can't add user mappings for it via the conf files ?   Anyone know how to get rid of the messages? thanks!

 

[EventAdminAsyncThread #10] com.adobe.cq.xf.impl.adobetarget.TargetVariationModificationListener Cannot derive user name for bundle com.adobe.cq.cq-experience-fragments [304] and sub service experience-fragments-service

 

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 akhoury

Somebody might have accidentally deleted the configuration for the service user by clicking delete in the /system/console/configMgr.  I would suggest you add the missing mappings manually again via /system/console/configMgr UI in the affected environment.

 

If the problem is affecting many environments then please contact our support team to debug the root cause.

1 reply

akhoury
akhouryAccepted solution
Employee
April 30, 2020

Somebody might have accidentally deleted the configuration for the service user by clicking delete in the /system/console/configMgr.  I would suggest you add the missing mappings manually again via /system/console/configMgr UI in the affected environment.

 

If the problem is affecting many environments then please contact our support team to debug the root cause.

New Participant
May 1, 2020
Thanks for the reply! The problem is that the customer doesn't allow manual use of the configMgr UI so I can't do that on the Prod servers. Also the manual updates are wiped out at every new code install. I will open a ticket. Thanks again!