EngageOne looking for a User that does not exist with Deliver Document Web Service calls

Product Feature: API (Web Service, SDI, etc.)



When submitting via Deliver Document Web Service to EngageOne® 4.4 SP3 an old/original user appears to be cached/stuck /referenced somewhere and the admin-services.log gets errors looking for it, (as it doesn’t exist) but no idea where it is being picked up from. The Webservice call still makes it through but the warnings/ errors in the logs will be picked up by the client so need to understand how to stop them occurring. 

Error in core\logs\admin-services.log:

[2018-01-08 13:43:33,824 | INFO | org.lsc.AbstractSynchronize] All entries: 7403, to modify entries: 0, successfully modified entries: 0, errors: 0

[2018-01-08 13:46:48,526 | WARN |] GET request for (EngageOne server details) resulted in 404 (Not Found); invoking error handler

[2018-01-08 13:46:48,558 | ERROR |] unable to process JSON com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize instance of java.lang.String out of NOT_AVAILABLE token at [Source: N/A; line: -1, column: -1]


User information appears to be cached in the jcr (Java Content Repository) when a template is created.


UPDATED: July 23, 2018
Either restart the EngageOne® server, or re-save the list of administrators in the UI (Admin page -> System Administrators), which refreshes the jcr cache.