topic Re: No login information for authdomain ERROR with connection to MS SQL in Administration and Deployment

No login information for authdomain ERROR with connection to MS SQL

PhiSlogan — Tue, 09 Jul 2019 07:55:52 GMT

Hello please help.

I get this error when trying to register a table or extracting from a table i get this Warning and Error log:

1 LIBNAME qsxxxxx SQLSVR Datasrc=XXXXX SCHEMA=dbo AUTHDOMAIN="SQLServerAuth_NK" ;
WARNING: No login information was available for authdomain SQLServerAuth_NK.
ERROR: CLI error trying to establish connection: [SAS][ODBC 20101 driver][20101]Login failed for user ''.
ERROR: Error in the LIBNAME statement.
2

Earlier on i was getting an error that would show my user name like this...

Line 146: ERROR: CLI error trying to establish connection: [SAS][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'username'

I tried as best as i could troubleshooting with this guide:

https://documentation.sas.com/?docsetId=bidsag&docsetTarget=p0dgsb8tpoljfkn1ixkyjjlbbi50.htm&docsetVersion=9.4&locale=en

Re: No login information for authdomain ERROR with connection to MS SQL

jag_SAS — Wed, 10 Jul 2019 17:04:45 GMT

Hi. Please post the results of completing step 5 in the documentation you mention:

Log on with the user account to the host where the SAS server is running, and use the native database client to connect to the database. If this fails, confirm the user account has file system privileges to the database client binaries and libraries.

This step will remove SAS from the picture and enable to verify all of the MS SQL information is correct.

Next I would run the SAS code directly without involving any metadata stored credentials. Once these two are working I then define the library in metadata and would use the auth domain and metadata-stored user id and password to validate the library.

Re: No login information for authdomain ERROR with connection to MS SQL

RogerHed — Tue, 19 Jan 2021 15:15:07 GMT

Still this error occurs if the running user account don't have access to the Authdomain to the Library.
Solution is to put all users as member to the Group containing the Authdomain Account.