Search Engine: Elastic

Article ID: 129676, created on Oct 24, 2016, last review on Feb 2, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0


Periodic task Clean up expired HTTP Messenger messages fails with one of the following outputs:

The remote server is down, details:
system exception, ID ''
OMG minor code (2), described as 'Failed to create or locate Object Adapter.', completed = NO


Named function 'taskCleanupExpiredMessages' is not registered.


In Operations Automation 7.0 some service controllers have been moved from pem service to the pau service.

However, periodic task Clean up expired HTTP Messenger messages tries to call service controller HTTPMessenger, belongs to pem and fails to find it.

This behavior has been reported as software-related issue #POA-107130: "7.1: "Clean up expired HTTP Messenger messages" periodic task still try to use "HTTPMessenger" in OA 7.0".


Please, contact your Technical Account Manager or Pooled Technical Associate Team ( in order to trace the status of the issue.

As a temporary solution the task Clean up expired HTTP Messenger messages may be cancelled. To cancel the task perform the following steps:

  1. Go to OA > Operations > Tasks > Periodic
  2. Click the task Clean up expired HTTP Messenger messages
  3. Click Cancel Task and confirm.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF