SAP connector fails with hostname not found when using a non-default port in RSA Identity Governance & Lifecycle
Originally Published: 2019-09-20
Article Number
Applies To
RSA Version/Condition: All
Issue
GetHostByName: '10.100.99.99:3301' not found SYSTEM CALL getaddrinfo
The Connection Details used in this example are:
A test connection using the default SAP port of 3300 is successful:
Cause
In the example above, RSA Identity Governance & Lifecycle is converting the entire string 10.100.99.99:3301 as a Hostname to an IP address.
Resolution
/H/hostname/S/port
For example,
Related Articles
Unable to save a Workflow Approval Email Template that contains non-Latin characters in RSA Identity Governance & Lifecycle 51Number of Views Using RSA SecurID Software Token 5.0 for Windows with Citrix non-persistent Xenapp virtual desktops 206Number of Views Utilize Authentication Manager SDK 8.0 in non-weblogic environment 174Number of Views java: command not found when installing L&G v7.0.0 10Number of Views How to make the sender address field non-editable when clicking on send email button while performing the review in RSA Id… 24Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?