Skip to main content
Skip table of contents

Unexpected Scenarios

Unexpected Scenarios


Possible Cause(s)



Logout Request Failed

When the system tries to logout agent forcefully following force logout policy, agent logout doesn’t happen and EF Connector logs an error message with a bad request. However, if we try to logout agent on Finesse directly, it works fine.

EF Connector uses a default logout reason when logging out agents forcefully. If this reason code is not defined in Cisco Finesse as a logout reason, the system does not log agent out.

  • If there’s no logout reason created in Cisco Finesse, create one.

  • Specify the value for DEFAULT_LOGOUT_REASON property to match the logout reason code ID defined in Cisco Finesse.


No Active Consumer on Destination Connector1

EF Connector is running but there’s no active consumer on the queue Connector1 in ActiveMQ.

When EF Connector can’t establish connection to Cisco Finesse, it goes out of service and closes its subscription from ActiveMQ. It reopens subscription only when it can reestablish connectivity with any of the configured Cisco Finesse instances. 

In Generic Connector log file, you’ll see a message like following:

"Primary-Finesse[, Secondary-Finesse[, ConnectedTo [0]"

Check connectivity with Cisco Finesse. You can verify following:

  • Are the necessary ports open between EF Connector and Cisco Finesse?

  • Verify that the DNS settings are accurate in EF Connector.

If you found “Exception in System Info: PKIX path building failed: unable to find valid certification” in ef_connector logs, this issue is caused by SSL certificate.  You need to perform following steps:

  • You need to add the certificate for finesse to the keystore file of the used JVM located at "%JAVA_HOME%\lib\security\cacerts"

  • First you can check if your certificate is already in the keystore by running the following command: keytool -list -keystore "%JAVA_HOME%/jre/lib/security/cacerts" (default password:  changeit)

  • If your certificate is missing you can get it by downloading it with your browser and add it to the keystore with the following command: "keytool -import -noprompt -trustcacerts -alias <AliasName> -file   <certificate_path> -keystore <KeystoreFile (%JAVA_HOME%/jre/lib/security/cacerts)> -storepass <Password>"

  • After import you can run the first command again to check if your certificate was added.

  • Restart GC to take effect.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.