Version

Argent Extended Technology — All versions

Date

2 Sep 2010

Summary

Daughter Engines deployed at a remote site may encounter communication issues when downloading control information from the Mother Engine.

Sample error message found in the Supervising Engine Log from the Daughter Engine:

10 Aug 2010 14:38:42.641 ABC XYZ COMMUNICATION ERROR. Failed to read reply from Argent Guardian motherhost.domain.com. TCP error: No error (0) (FILE:

PullMotherData.cpp LINE: 722)

10 Aug 2010 14:38:42.641 ABC XYZ NOT CHANGED mother control information

10 Aug 2010 14:39:27.859 ABC XYZ Performance data and relator trace logs are to be uploaded to mother scheduling engine (Total size 0.24 KB).

10 Aug 2010 14:39:37.546 ABC XYZ No control information has been downloaded from mother scheduling engine. Wait 60 seconds…

10 Aug 2010 14:40:37.545 ABC XYZ No control information has been downloaded from mother scheduling engine. Wait 60 seconds…

Similar error messages appear in the Supervising Engine log file of all Argent Extended Technology products from the Daughter Engine.

Technical Background

This is your standard run-of-the-mill communication issue.

Either the ports are blocked, the server is down, or this may simply be an issue of being unable to resolve the hostname.

In general, when creating a Remote Daughter Engine package, avoid using the fully-qualified domain name to specify the Main Engine, and use the NETBIOS name or IP address.

Resolution

Ensure connectivity from the Daughter Engine to the main engine via a PING, or a telnet to the Main Engine on the corresponding port.

See Also:

What TCP Ports Does Argent Use?

If the name used to specify the Main Engine was at fault, reinstall the Daughter Engine specifying either NETBIOS name, or the IP address of the Mother Engine.