SUPPORT

Select Your Region

Visit the Cary, NC, US corporate headquarters site

Americas

Europe

Middle East & Africa

Asia Pacific

View our worldwide contacts list for help finding your region

Americas

Europe

Middle East & Africa

Asia Pacific

Sign In

Get access to My SAS, trials, communities and more.

Sign Out

Get access to My SAS, trials, communities and more.

SAS Sites

sas.com
Support
Blogs
Communities
Developer
Curiosity
Videos

Documentation

Learn
Brand
PartnerNet
Merchandise
SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 65712: The "Register Tables" or "Update Metadata" function can fail with the error message "Invalid connection options. Lack USER option."

DetailsHotfixAboutRate It

The Register Tables and Update Metadata functions in SAS® Management Console and SAS® Data Integration Studio can fail with the following error for the METALIB procedure:

ERROR: Invalid connection options. Lack USER option.

This error occurs when the following conditions are true:

  • You attempt to perform the Register Tables or Update Metadata function for tables within a database or library, which requires authorization or credentials.
  • You log in to the SAS Management Console or SAS Data Integration Studio client with a user ID that has access to metadata-stored credentials for that library or database.  
  • Your user ID that launches the SAS® Application Server session is not the same user ID that you use to log in to the client.
  • Your user ID that launches the SAS Application Server session does not have access to metadata-stored credentials for that library or database. 

These conditions result in a situation where the client verifies that you have access to metadata-stored credentials for the library or database (so that it does not then prompt for database credentials). Then the client submits PROC METALIB without any embedded credentials because it expects the same credentials will be available at the time of code execution.  If you launch a SAS Application Server session where code is executing and your user ID for that session does not have the same access to metadata-stored credentials, the process fails. 

The workaround for this issue is to ensure that you use the same user ID with relevant credentials both to connect to the client and to launch the SAS Application Server session.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Data Integration StudioMicrosoft® Windows® for x644.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8 Enterprise 32-bit4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8 Enterprise x644.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8 Pro 32-bit4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8 Pro x644.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Enterprise 32-bit4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Enterprise x644.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Pro 32-bit4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Pro x644.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows 104.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 Datacenter4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 R2 Datacenter4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 R2 Std4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 Std4.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows Server 20164.9044.9059.4 TS1M69.4 TS1M7
Microsoft Windows Server 20194.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Enterprise 32 bit4.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Enterprise x644.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Home Premium 32 bit4.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Home Premium x644.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Professional 32 bit4.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Professional x644.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Ultimate 32 bit4.9044.9059.4 TS1M69.4 TS1M7
Windows 7 Ultimate x644.9044.9059.4 TS1M69.4 TS1M7
SAS SystemSAS Management ConsoleMicrosoft® Windows® for x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8 Enterprise 32-bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8 Enterprise x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8 Pro 32-bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8 Pro x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Enterprise 32-bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Enterprise x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Pro 32-bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 8.1 Pro x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows 109.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 Datacenter9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 R2 Datacenter9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 R2 Std9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows Server 2012 Std9.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows Server 20169.4_M69.4_M79.4 TS1M69.4 TS1M7
Microsoft Windows Server 20199.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Enterprise 32 bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Enterprise x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Home Premium 32 bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Home Premium x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Professional 32 bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Professional x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Ultimate 32 bit9.4_M69.4_M79.4 TS1M69.4 TS1M7
Windows 7 Ultimate x649.4_M69.4_M79.4 TS1M69.4 TS1M7
64-bit Enabled AIX9.4_M69.4_M79.4 TS1M69.4 TS1M7
64-bit Enabled Solaris9.4_M69.4_M79.4 TS1M69.4 TS1M7
HP-UX IPF9.4_M69.4_M79.4 TS1M69.4 TS1M7
Linux for x649.4_M69.4_M79.4 TS1M69.4 TS1M7
Solaris for x649.4_M69.4_M79.4 TS1M69.4 TS1M7
* 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.