LDAP Connection Error: "An error occurred"

LDAP Authorization User Guide

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. A Connection Error in the Test Connection Window 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

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: "java.net.UnknownHostException"

The LDAP connection error "java.net.UnknownHostException" 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 this address on its network. The connection is being tested between the Mirth® Connect server and the Lightweight Directory Access Protocol (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 does not recognize that host name. Parent topic: Troubleshooting Connection Errors

LDAP Authorization User Guide

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. Ensure that the port number is correct. Lightweight Directory Access Protocol (LDAP) servers typically use port 389 for unencrypted communication or the STARTTLS mode and port 636 for the SSL mode. Ensure that you have imported the LDAP server certificate. This error can occur if you have enabled SSL or STARTTLS but have not yet imported the LDAP server certificate using the SSL Manager plug-in for Mirth® Connect by NextGen Healthcare. Ensure that the LDAP server certificate is trusted. Parent topic: Troubleshooting Connection Errors Related tasks Enable Encryption

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: "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. The Lightweight Directory Access Protocol (LDAP) server rejected the Admin user DN and password. This error can happen for a number of reasons. To determine the specific reason, look at the error codes shown in the message returned by the LDAP server. Error code 49 means that authentication failed. The phrase data 701 indicates why authentication failed. The 701 value means that the account has expired. You can view a list of other authentication failure codes on the LDAP Error Code 49 page at confluence.atlassian.com. Parent topic: Troubleshooting Connection Errors

LDAP Connection Error: "An error occurred"

Recommendations

Troubleshooting Connection Errors

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

LDAP Connection Error: "java.net.UnknownHostException"

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

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

LDAP Connection Error: "LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 701, v1db0"

LDAP Connection Error: "An error occurred"

Troubleshooting Connection Errors

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

LDAP Connection Error: "java.net.UnknownHostException"

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

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

LDAP Connection Error: "LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 701, v1db0"