Search Engine: Elastic

Article ID: 115456, created on Jan 28, 2013, last review on Jul 14, 2018

  • Applies to:
  • Odin Business Automation Standard 4.5


After terminating a Container Subscription the task Process event #125 fails with an error.

The error in problem report is similar to the following:

[2012/10/06 16:33:24] [ERROR] [22303] [HSPC::Taskman::Comm::backend_execute_task] Task #283963 caused error code: 3604488-ZXJyb3I=:-aG9zdG5hbWU=:Q1QxMTY=


Event #125 is "Subscription has been put in the termination queue".

By default this event has an action assigned – Stop Container for the Container Subscription. You can verify this by going to:

OBAS Provider CP > Configuration Director > Event Manager > Events > #125 Subscription has been put in the termination queue > Actions > Container Subscription > Action on container.

If container is in Stopped status and subscription associated with this container is put into Termination Queue, event #125 is trying to stop an already stopped container and as a result the task fails with an error.

The actual error can be deciphered with base64 decode (for example : by parts (separated by colon):

3604488 - Error code. It means "VE hostname is not running";

ZXJyb3I - error;

-aG9zdG5hbWU= - hostname;

Q1QxMTY= - CT116 (may be different - depending on the actual hostname of the container).


The overall impact is not significant, error occurs when OBAS tries to stop container that is already stopped.

The issue has been reported to OBAS Maintenance team as software issue with id #PBAS-23405 and the fix will be considered for the inclusion in a future product versions. It is not recommended to delete the assigned action (Stop Container) from #125 event. In this case containers will remain Running after subscription is put into Termination Queue if they were not stopped explicitly.

Please consider watching Odin public sources for information about updates in our products:

Public roadmaps for partners

Marketing news and important announces

Knowledge base, each product update comes with a corresponding KB article.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF