LDAP Connection Error: "Admin User DN or Admin Password is invalid"

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 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 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: "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: "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. 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 Authorization User Guide

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. This error can result from any of the following flaws in the configuration of the Lightweight Directory Access Protocol (LDAP) connection: The Base DN is incorrect. The Search Contexts does contain valid usernames. The Username attribute mapping is not set to the appropriate value. Mirth® Connect by NextGen Healthcare identifies user accounts on the LDAP server by looking for objects that contain the Username attribute. For Active Directory, the typical Username attribute is sAMAccountName. For other LDAP servers such as OpenLDAP, a common Username attribute is uid. Username Attribute in LDAP Attribute Mapping These settings are all located on the LDAP Authorization tab. Parent topic: Troubleshooting Connection Errors Related tasks Set Up the LDAP Connection Filter User Accounts Map User Attributes

LDAP Connection Error: "Admin User DN or Admin Password is invalid"

Recommendations

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

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

LDAP Connection Error: "An error occurred"

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

LDAP Connection Error: "java.net.ConnectException: Connection refused"

LDAP Connection Error: "No user accounts were found"

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

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

LDAP Connection Error: "An error occurred"

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

LDAP Connection Error: "java.net.ConnectException: Connection refused"

LDAP Connection Error: "No user accounts were found"