Revision as of 16:43, April 3, 2015 by Pmcknigh (talk | contribs)
Jump to: navigation, search

Known Issues and Recommendations

Local Control Agent

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Local Control Agent. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.



You can specify only one Trusted Certificate Authority (Trusted CA) when prompted during installation of LCA and Genesys Deployment Agent.

Workaround: Specify one Trusted CA during installation. Then open the appropriate configuration file (lca.cfg for LCA or gda.cfg for Genesys Deployment Agent), and in the [security] section, manually set the trusted-ca option to a comma-delimited list of the Trusted CAs.

ID: MFWK-15846 Found In: 8.5.000.11 Fixed In: 

When running on the AIX platform, LCA is sometimes unable to start an application and generates a core file if the enable-thread option is set to true in the [log] section of the LCA configuration file lca.cfg.

Workaround: To avoid this problem, set the enable-thread option to false.

ID: MFWK-15833 Found In: 8.5.000.09 Fixed In: 

On the Windows platform, LCA sometimes does not start an application when requested, either not at all, or only when it receives another request. This appears to be because of corrupted performance counter data.

Workaround: Rebuild the performance counter by issuing the following command on the system:

    c:\Windows\system32\lodctr /r
ID: MFWK-15696 Found In: 8.5.000.09 Fixed In: 

If Local Control Agent tries to start, as a service, an application that does not have a matching application object created in Configuration Server, for example in the -app command parameter, it might log an error indicating that the stop timeout for the application has expired. Ignore this warning.

Workaround: To avoid this error message altogether, correct the command line configured in the service.

ID: MFWK-15693 Found In: 8.5.000.09 Fixed In: 

An application that supports hangup detection and for which the feature is configured may be incorrectly detected as unresponsive if there are alarm conditions for third-party applications configured on the same host, or if there are CPU- or memory-based alarm conditions configured for the host.

ID: MFWK-12220 Found In: 8.0.300.04 Fixed In: 



Internationalization Issues

Information in this section is included for international customers.


There are no internationalization issues for this product.


Comments or questions about this documentation? Contact us for support!