Troubleshooting Connection Errors
Lightweight Directory Access Protocol (LDAP) connection errors can appear in the Mirth® Connect by NextGen Healthcare server log. They can also appear when you test the connection in the LDAP Authorization settings panel.
In some cases, you can gain additional information about an error condition by enabling debug logging for LDAP activity.
- LDAP Connection Error: "Admin User DN or Admin Password is invalid"
The Lightweight Directory Access Protocol (LDAP) connection error "Admin User DN or Admin Password is invalid" includes a data number that indicates why the credentials were rejected. - 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. - 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. - LDAP Connection Error: "An error occurred while attempting to establish a secure connection"
The LDAP connection error "An error occurred while attempting to establish a secure connection" can result from an incorrect port number, an untrusted server certificate, or a missing server certificate. - 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. - 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. - LDAP Connection Error: "Failed to decrypt the stored admin user password"
The LDAP connection error "Failed to decrypt the stored admin user password" 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. - LDAP Connection Error: "java.net.ConnectException: Connection refused"
The LDAP connection error "java.net.ConnectException: Connection refused" indicates that the remote host responded, but no LDAP service was found at the specified port number. - 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 - LDAP Connection Error: "java.net.UnknownHostException"
The LDAP connection error "java.net.UnknownHostException" can indicate an incorrect host name or a network connection problem. - LDAP Connection Error: "LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 701, v1db0"
The LDAP connection error "LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 701, v1db0" indicates that authentication failed because the account has expired. - LDAP Connection Error: "No user accounts were found"
The LDAP connection error "No user accounts were found" can occur if the LDAP connection has an incorrect base DN, search contexts, or username attribute mapping. - 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.
Related concepts