Usage Note 60671: SAS/CONNECT® SIGNON through metadata fails with "ERROR: No logins found"
When issuing a SAS/CONNECT SIGNON to a SAS/CONNECT Application Server defined in the SAS metadata from a SAS session that cannot prompt, the SIGNON fails with the following errors if the metadata credentials are incorrect or missing:
SIGNON SERVER="SASApp - Connect Server";
ERROR: ERROR: No logins found.
ERROR: Retrieving login information based on AuthenticationDomain from the
SAS Metadata Server failed.
ERROR: Unable to retrieve the SAS/CONNECT server definition "SASAPP - CONNECT SERVER".
ERROR: Remote signon to SASAPP - CONNECT SERVER canceled.
If credentials are incorrect or missing in the metadata, the SIGNON does the following:
- fails with the above errors from a batch SAS session or a SAS server (SAS Workspace Server), which cannot prompt for SAS/CONNECT SIGNON
- prompts for valid credentials from a SAS session that can handle prompting such as a SAS interactive Display Manager session
If you receive the above errors, complete these steps to work around the issue:
- Run the following code to verify that the SAS/CONNECT application server exists by listing all the SAS/CONNECT servers defined in the metadata and their associated AUTHDOMAIN:
SIGNON SERVERV=_ALL_;
- Verify the value for the METAUSER= SAS option by executing the following code:
PROC OPTIONS GROUP=META;
RUN;
- Use SAS® Management Console to verify that the user ID specified for the METAUSER= contains the following:
- a metadata identity
- an external account for the same AUTHDOMAIN as the SAS/CONNECT server
- a valid user ID and password specified for the external account
Operating System and Release Information
SAS System | SAS/CONNECT | z/OS | 9.3 | | 9.3 TS1M0 | |
z/OS 64-bit | 9.3 | | 9.3 TS1M0 | |
Microsoft® Windows® for x64 | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 Standard Edition | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 for x64 | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows Server 2008 | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows Server 2008 R2 | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows Server 2008 for x64 | 9.3 | | 9.3 TS1M0 | |
Microsoft Windows XP Professional | 9.3 | | 9.3 TS1M0 | |
Windows 7 Enterprise 32 bit | 9.3 | | 9.3 TS1M0 | |
Windows 7 Enterprise x64 | 9.3 | | 9.3 TS1M0 | |
Windows 7 Home Premium 32 bit | 9.3 | | 9.3 TS1M0 | |
Windows 7 Home Premium x64 | 9.3 | | 9.3 TS1M0 | |
Windows 7 Professional 32 bit | 9.3 | | 9.3 TS1M0 | |
Windows 7 Professional x64 | 9.3 | | 9.3 TS1M0 | |
Windows 7 Ultimate 32 bit | 9.3 | | 9.3 TS1M0 | |
Windows 7 Ultimate x64 | 9.3 | | 9.3 TS1M0 | |
Windows Vista | 9.3 | | 9.3 TS1M0 | |
Windows Vista for x64 | 9.3 | | 9.3 TS1M0 | |
64-bit Enabled AIX | 9.3 | | 9.3 TS1M0 | |
64-bit Enabled HP-UX | 9.3 | | 9.3 TS1M0 | |
64-bit Enabled Solaris | 9.3 | | 9.3 TS1M0 | |
HP-UX IPF | 9.3 | | 9.3 TS1M0 | |
Linux | 9.3 | | 9.3 TS1M0 | |
Linux for x64 | 9.3 | | 9.3 TS1M0 | |
Solaris for x64 | 9.3 | | 9.3 TS1M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Date Modified: | 2017-07-21 13:28:37 |
Date Created: | 2017-06-21 16:11:25 |