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 Utilize Authentication Manager SDK 8.0 in non-weblogic environment 174Number of Views Using RSA SecurID Software Token 5.0 for Windows with Citrix non-persistent Xenapp virtual desktops 206Number of Views Web Page not found when using HTTPS in URL in RSA Identity Management and Governance 58Number of Views RSA Authentication Manager Web Tier software fails to install due to third-party software on the host server 48Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA MFA Agent 2.4.3 for Microsoft Windows Group Policy Object Template Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.4.3 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?