Usage Note 15096: Import Tables fail when multiple database logins are defined in the
metadata
When trying to use Import Tables in SAS Management Console, the
following errors may be encountered when the tables are stored in a
database such as Oracle or SQL Server.
In Oracle, the following error messages will appear:
ERROR: ORACLE connection error: ORA-01004: default username feature
not supported; logon denied.
ERROR: Error in the LIBNAME statement.
In SQL Server, the following error messages will appear:
ERROR: CLI error trying to establish connection: [Microsoft][ODBC
SQL Server Driver][SQL Server]Login failed for user '(null)'.
Reason: Not associated with a trusted SQL Server connection.
ERROR: Error in the LIBNAME statement.
In addition, the userid and password will be missing when the LIBNAME is
displayed in SAS Management Console.
This problem has been encountered when a user identity in the metadata
has a database login and the user identity also belongs to a group that
has a group database login. The Metadata Server cannot resolve the login
conflict.
Only one login per authentication domain should be available for an
identity. To correct the problem, either remove the user from the group
or remove the login from the user identity.
Operating System and Release Information
SAS System | SAS Management Console | Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M0 | |
Microsoft Windows NT Workstation | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M0 | |
Microsoft Windows 2000 Server | 9.1 TS1M0 | |
Microsoft Windows 2000 Professional | 9.1 TS1M0 | |
64-bit Enabled Solaris | 9.1 TS1M0 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M0 | |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M0 | |
Microsoft Windows XP Professional | 9.1 TS1M0 | |
HP-UX IPF | 9.1 TS1M0 | |
64-bit Enabled AIX | 9.1 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: | 2005-04-28 12:37:21 |
Date Created: | 2005-04-25 15:37:45 |