Unable to Retrieve Database Properties from Manager: COAPI Returned:209410

Document ID : KB000021025
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

In TRC_CMENGINE_*.log (R11.2) or in TRC_<enginename>_*.log (R12.x) the following error occurs for custom created engine instances:

Unable to Retrieve Database Properties from Manager:<manager_address>. COAPI Returned:209410

This error appears at startup time of caf for the custom created engine instances. It does not appear for the default SystemEngine.

Environment: 

CA Client Automation - All Versions 

 

Resolution:

When caf is started, the custom created engines are started at the beginning just after smserver, ccnfagent and cfnotsrvd plugins.

But, they are started before cmobjectmanager (Common Object Manager).

This can cause a problem because the engine sends a CAM message to cmobjectmanager (queue U-COAPI) in order to retrieve some database properties and the error 209410 occurs as CAM queue U-COAPI is not connected (cmobjectmanager is not yet started).

The SystemEngine does not have this problem because it is started later in the caf starting process after cmobjectmanager.

In order to avoid this error, add cmobjectmanager as a dependency for the first engine started by caf.

  1. Run caf start and check which engine is the first to start in the installation (in this example CustomEngine3). ______________________________________________________________
    C:\> caf start
    Starting caf service...
    Waiting for service to confirm startup...
    Connecting to caf process...
    CA DSM r11 Common Application Framework 11.2.4000.06
    Starting all DSM services...
    Session messaging server (smserver)...ok
    Connecting to session messaging server...ok
    Configuration agent (ccnfagent)...ok
    Notification Server (cfnotsrvd)...ok
    Engine (CustomEngine3)...ok
    Engine (CustomEngine2)...ok
    Engine (CustomEngine1)...ok
    Common Server (cserver)...ok
    Asset Management server (amrss)...ok
    ...
    Common object manager (cmobjectmanager)...ok
    ...
    Asset Management manager (ammanager)...ok
    Engine (SystemEngine)...ok
    Event notification plugin (cfnotify)...ok
    ...
    ______________________________________________________________
    The file TRC_CMENGINE_n.log (R11.2) or the file TRC_CustomEngine3_n.log shows the following line corresponding to the engine startup:
    ...
    2010-04-22 10:30:33 Engine Starting...
    2010-04-22 10:30:38 Unable to Retrieve Database Properties from Manager:<DSMManagerAddress>. COAPI Returned:209410
    2010-04-22 10:30:49 cAmoDomain::InitializeNotification, Notification system succesfully initialized [<DSMManagerAddress >:CustomEngine3]
    2010-04-22 10:30:52 Engine Started
    ...
  2. Execute the following command for the first engine:

    caf setprop CustomEngine3 dependencies "ccnfagent cfnotsrvd cmobjectmanager"

    The expected output is:

    C:\>caf setprop CustomEngine3 dependencies "ccnfagent cfnotsrvd cmobjectmanager"
    Property CustomEngine3/dependencies is currently "ccnfagent cfnotsrvd"
    Property CustomEngine3/dependencies is now "ccnfagent cfnotsrvd cmobjectmanager"

  3. The next time caf is started, cmobjectmanager will be started before CustomEngine3 and all the other engines: ______________________________________________________________
    C:\>caf start
    Starting caf service...
    Waiting for service to confirm startup...
    Connecting to caf process...
    CA DSM r11 Common Application Framework 11.2.4000.06
    Starting all DSM services...
    Session messaging server (smserver)...ok
    Connecting to session messaging server...ok
    Configuration agent (ccnfagent)...ok
    Notification Server (cfnotsrvd)...ok
    Common object manager (cmobjectmanager)...ok
    Engine (CustomEngine3)...ok
    Engine (CustomEngine2)...ok
    Engine (CustomEngine1)...ok
    Common Server (cserver)...ok
    Asset Management server (amrss)...ok
    ...
    ______________________________________________________________

    The file TRC_CMENGINE_n.log (in R11.2) or the file TRC_CustomEngine3_n.log should now show the following lines corresponding to the engine startup:
    ...
    2010-04-22 10:41:07 Engine Starting...
    2010-04-22 10:41:23 cAmoDomain::InitializeNotification, Notification system succesfully initialized [<DSMManagerAddress >:CustomEngine3]
    2010-04-22 10:41:24 Engine Started
    ...