SAS® Management Console requires an application server in order to perform the Update Metadata step. SAS® 9.2, SAS® 9.3, and SAS® 9.4 use the default application server that is set in the connection profile that you use to connect to the SAS® Metadata Server.
When you use SAS Management Console to update table metadata, a dialog box with the following message might be produced:
Error accessing metadata:No servers associated with the
library "Test-Library-Name" are
configured for SAS/Connect. Use SAS Management
Console to add the SAS/Connect Server component.
The message occurs when the library is invalid on the default server or when the user does not have access to the default server. The message is common when the default server is SASMeta.
The default application server is defined by the object-ID value of the server context, which is set in the AppServer.Default= property in the connection profile.
The connection profile is defined by an SWA file in the user's Application Data directory that resides in locations similar to the following:
For Windows operating environments:
C:\Documents and Settings\Windows-logon-ID\Application Data\SAS\MetadataServerProfiles\profile-name.swa
For Windows Vista or later operating environments:
C:\Users\Windows-logon-ID\AppData\Roaming\SAS\MetadataServerProfiles\profile-name.swa
For UNIX operating environments:
/home/UNIX-logon-ID/.SASAppData/MetadataServerProfiles/profile-name.swa
Sample contents of an SWA file:
#Properties file updated on: Wed Nov 09 16:03:50 EST 2013 !!!!! DO NOT EDIT !!!!!!!
#Wed Nov 09 16:03:50 EST 2013
ServicePrincipalName=
SingleSignOn=false
AllowLocalPasswords=true
AppServer.Default=A53DVWWM.AR000001
port=8561
SelectedReps=A0000001.A53DVWWM
InternalAccount=false
Name=SAS - Local Administrator
userid=sasbi\sas
authenticationdomain=DefaultAuth
password={sas002}1D57933958C580064BD3DCA81A33DFB2
host=sasbi.demo.sas.com
SecurityPackageList=Negotiate,NTLM
SecurityPackage=Negotiate
In the sample SWA file above, AppServer.Default=A53DVWWM.AR000001 refers to the object ID for the SASMeta server context on this server.
Follow one of the following circumventions to update table metadata:
- Edit the SWA file and remove the AppServer.Default= value so that no default server is named. The next time a server is needed (for example, for updating table metadata), you will be prompted to select a server. Select the server that is appropriate for the library (for example, SASApp).
- Submit a METALIB procedure step from within a SAS job or from an interactive session such as in SAS®®, running on the appropriate compute server for the library. The PROC METALIB step should look like the following code sample:
proc metalib;
omr (library="SAS-demo-library"
server="sasbi.demo.sas.com"
port="8561"
user="sasadm@saspw"
password="Orion123"
repname="Foundation"
protocol=BRIDGE);
folder="/Shared Data/SAS-demo-data";
select ("CLASS");
report;
run;
In this code:
- The value for SERVER= (in this case, sasbi.demo.sas.com) names the metadata server.
- The value for LIBRARY= (SAS-demo-library) specifies the name of the library that you see in SAS Management Console.
- The value for FOLDER= (/Shared Data/SAS-demo-data) specifies the metadata location for the table.
- The SELECT statement specifies the names the table or tables to update.
This scenario does not use the default server that is defined in the server profile.
Operating System and Release Information
SAS System | SAS Management Console | Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS1M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS1M0 | |
Microsoft Windows Server 2003 Standard Edition | 9.2 TS1M0 | |
Microsoft Windows XP Professional | 9.2 TS1M0 | |
Windows Vista | 9.2 TS1M0 | |
Windows Vista for x64 | 9.2 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.