Usage Note 43907: Resolving invalid credentials and access denied errors in conjunction with the AUTHDOMAIN option in a LIBNAME statement
When the Use runtime credentials in library statements option is active in SAS® Data Integration Studio, library login credentials are retrieved from the metadata at job execution time. This is accomplished by using the AUTHDOMAIN option in place of the USERID and PASSWORD options on LIBNAME statements.
If this happens, runtime retrieval of credentials fails with the following errors:
ERROR: Libname libref is not assigned.
ERROR: Error in the LIBNAME statement.
ERROR 52-121: Invalid credentials
ERROR: Access denied.
Any of the following issues can cause this problem to occur:
- The user that is executing the job does not have access to valid credentials for the authentication domain that is referenced in the AUTHDOMAIN option in the LIBNAME statement.
The AUTHDOMAIN option retrieves credentials based on the authentication domain. If the user does not have access to credentials for the authentication domain, or the credentials that are retrieved are not valid, the library allocation will fail.
In this situation, perform the following check within SAS Data Integration Studio to determine whether credentials are being retrieved:
-
Select Tools ► Options from the SAS Data Integration Studio menu.
- Deselect the Use runtime credentials in library statements on the General tab and click OK.
-
Highlight the library that is experiencing issues, and then right-click View Libname.
The LIBNAME statement should contain USERID and PASSWORD options, and it should execute without errors.
-
The AUTHDOMAIN option is unable to retrieve credentials because the setting for the Metaserver system option in the SAS Workspace Server session differs from the Metaserver system option set within the SAS® Metadata Server.
You can check this by performing the following:
-
Select File ► Connection Profile... from the SAS Data Integration Studio menu.
- Select Yes in the Disconnect from Server dialog box.
-
Click Edit..., and then click Next to get to the Connection Information panel.
-
Note the value for the Machine option. This is the value SAS Data Integration Studio uses when setting the Metaserver system option.
-
Go to the Metadata Server machine and retrieve the Metaserver option setting from the Metaparms.sas file. The default location for this file is Lev1/SASMeta/MetadataServer. Compare the value for the Metaserver option to the Machine option from the Connection Profile.
If the Machine value from the Connection Profile is not the same as the value for the Metaserver option from Metaparms.sas, change the Machine option so that it matches the value in Metaparms.sas.
If you need further assistance in resolving your problem, contact SAS Technical Support.
Operating System and Release Information
SAS System | SAS Data Integration Studio | Microsoft Windows XP Professional | 4.21 | | | |
Microsoft Windows Server 2008 for x64 | 4.21 | | | |
Microsoft Windows Server 2008 | 4.21 | | | |
Microsoft Windows Server 2003 for x64 | 4.21 | | | |
Microsoft Windows Server 2003 Standard Edition | 4.21 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 4.21 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 4.21 | | | |
Microsoft Windows NT Workstation | 4.21 | | | |
Microsoft Windows 2000 Professional | 4.21 | | | |
Microsoft Windows 2000 Server | 4.21 | | | |
Microsoft Windows 2000 Datacenter Server | 4.21 | | | |
Microsoft Windows 2000 Advanced Server | 4.21 | | | |
Microsoft Windows 95/98 | 4.21 | | | |
Microsoft® Windows® for x64 | 4.21 | | | |
Windows 7 Enterprise 32 bit | 4.21 | | | |
Windows 7 Enterprise x64 | 4.21 | | | |
Windows 7 Home Premium 32 bit | 4.21 | | | |
Windows 7 Home Premium x64 | 4.21 | | | |
Windows 7 Professional 32 bit | 4.21 | | | |
Windows 7 Professional x64 | 4.21 | | | |
Windows 7 Ultimate 32 bit | 4.21 | | | |
Windows 7 Ultimate x64 | 4.21 | | | |
Windows Millennium Edition (Me) | 4.21 | | | |
Windows Vista | 4.21 | | | |
Windows Vista for x64 | 4.21 | | | |
*
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: | 2012-08-13 13:59:27 |
Date Created: | 2011-08-03 14:02:56 |