LDAP Connection Error: "An error occurred while attempting to establish a secure connection"

LDAP Authorization User Guide

LDAP Connection Error: "An error occurred"

The Lightweight Directory Access Protocol (LDAP) connection error "An error occurred" indicates an error that Mirth® Connect by NextGen Healthcare does not recognize. An error occurred that Mirth® Connect by NextGen Healthcare does not recognize. Check to see if an error message was returned by the Lightweight Directory Access Protocol (LDAP) server. If so, the errors looks something like this: LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 701, v1db0 Make a note of the number specified in data <number>. In the preceding example, the number is 701, which is referred to as an LDAP result code. You can view definitions of LDAP result codes at the LDAP Result Code Reference page on ldap.com. If an LDAP error message is not shown, enable debug logging so that additional information can be collected the next time the error occurs. Parent topic: Troubleshooting Connection Errors Related concepts Enable Debug Logging for LDAP Activity

LDAP Authorization User Guide

LDAP Connection Error: "javax.net.ssl.SSLHandshakeException"

The LDAP connection error "javax.net.ssl.SSLHandshakeException" can occur if you have enabled SSL or STARTTLS and have no yet imported the Lightweight Directory Access Protocol (LDAP) server certificate This error can occur if you have enabled SSL or STARTTLS but have not yet imported the Lightweight Directory Access Protocol (LDAP) server certificate using the SSL Manager plug-in for Mirth® Connect by NextGen Healthcare. Parent topic: Troubleshooting Connection Errors Related tasks Import the LDAP Server Public SSL Certificate

LDAP Authorization User Guide

LDAP Connection Error: "Timed out while attempting to connect to host <name> on port <number>"

The LDAP connection error "Timed out while attempting to connect to host <name> on port <number>" occurs if the LDAP server host name or port number is incorrect, or if network problems are preventing Mirth® Connect from accessing the LDAP server. Mirth® Connect by NextGen Healthcare attempted to connect to a Lightweight Directory Access Protocol (LDAP) server at the given host and port number, but did not receive a response. Usually this error means that the host name or the port is incorrect, but it could also mean that network problems are preventing Mirth® Connect from accessing the LDAP server. Parent topic: Troubleshooting Connection Errors

LDAP Authorization User Guide

LDAP Connection Error: "An error occurred / No route to host"

The Lightweight Directory Access Protocol (LDAP) connection error "An error occurred / No route to host" can indicate an incorrect host name or a network connection problem. The address entered in the Host field may be incorrect, or Mirth® Connect by NextGen Healthcare is unable to access address on its network. The connection is being tested between the server and the LDAP server. If you are able to access the LDAP server at a given host name from your local machine, it is possible that Mirth® Connect by NextGen Healthcare does not recognize that host name. Parent topic: Troubleshooting Connection Errors

LDAP Authorization User Guide

LDAP Connection Error: "com.mirth.connect.plugins.ldap.shared.Cryptor$<Encryption or Decryption>FailedException"

The LDAP connection error "com.mirth.connect.plugins.ldap.shared.Cryptor$<Encryption or Decryption>FailedException" can occur if the encryption key changed, if there are mismatched Java versions, or if Java Cryptography Extension (JCE) is not installed on your workstation. This Lightweight Directory Access Protocol (LDAP) connection error message ends with either EncryptionFailedException or DecryptionFailedException. This error can result from any of the following conditions: The Mirth® Connect by NextGen Healthcare encryption key changed or the encryption settings defined in /conf/mirth.properties have changed. The password for the admin user DN is stored by Mirth® Connect and is encrypted for security. Mirth® Connect uses an internal encryption key to encrypt the password. This internal encryption key is located in the file pointed to by the "keystore.path" setting in the mirth.properties file (the default location is /appdata/keystore.jks). If this file is changed or replaced or if

LDAP Authorization User Guide

LDAP Connection Error: "Failed to connect to host <host name> on port <number>"

The Lightweight Directory Access Protocol (LDAP) connection error "Failed to connect to host <host name> on port <number>" indicates that the remote host responded, but no LDAP service was found at the specified port number. The server at the given host responded, but no Lightweight Directory Access Protocol (LDAP) service is found at the given port number. Possibly the remote server is not running an LDAP service or the port number is incorrect. Parent topic: Troubleshooting Connection Errors

LDAP Connection Error: "An error occurred while attempting to establish a secure connection"

Recommendations

LDAP Connection Error: "An error occurred"

LDAP Connection Error: "javax.net.ssl.SSLHandshakeException"

LDAP Connection Error: "Timed out while attempting to connect to host <name> on port <number>"

LDAP Connection Error: "An error occurred / No route to host"

LDAP Connection Error: "com.mirth.connect.plugins.ldap.shared.Cryptor$<Encryption or Decryption>FailedException"

LDAP Connection Error: "Failed to connect to host <host name> on port <number>"

LDAP Connection Error: "An error occurred"

LDAP Connection Error: "javax.net.ssl.SSLHandshakeException"

LDAP Connection Error: "Timed out while attempting to connect to host <name> on port <number>"

LDAP Connection Error: "An error occurred / No route to host"

LDAP Connection Error: "com.mirth.connect.plugins.ldap.shared.Cryptor$<Encryption or Decryption>FailedException"

LDAP Connection Error: "Failed to connect to host <host name> on port <number>"