SAS Platform Admin Blog

In this article you will get to know where Metadata repository is stored physically and in Metadata level. I have already posted article about three different types of Metadata repositories and their uses. You can locate any type of repositories using SAS Management Console. Metadata Manager plug in shows repository location Expand Metadata manager plug in, under Active Sever you will find all the repositories configured in you SAS environment. By expanding Active Server you can see the Foundation repository. All the Metadata contents will be stored under this. There should be exactly one foundation repository. Physical location In Metadata manager plug in, expand active server and click on the foundation. You will get repository id, repository type and repository path. Repository path shows the physical location. It only show you the relative path. In above figure, I have merged snapshot of SAS Management Console and snapshot of physical location. You

Issue While logging in SAS Enterprise Guide 6.1 I got following error. Unable to Connect to the metadata server A connection could not be established to a metadata server running on port 8562 on host xxx. Retrieving the COM class factory for component with CLSID {868CEB5F-4D78-43FC-96B4-F5B6C0341151} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: Ox80040154 (REGDAB_E_ CLASSNOTREG)) Screenshot of the Error message  Solution No proper access in OS level This error message usually occurs if the user doesn't have access to host machine. He/she should have home directory, a login shell (bash or Ksh), and appropriate permission to the home directory in the OS level. If the user is assigned to /bin/nologin or /bin/false shell, SAS EG will throw this error. Not properly installed. If the SAS EG is not installed properly, say if you have older version of EG your system this error might occur. All you need to do

Issue: We are recently migrated from SAS Enterprise Guide 4.1 to SAS EG 7.1. 1. Below error is shown when I copy paste large amount of content in EG. OpenClipboard failed (Exception from HRESULT:0x800401D0 CLIPBRD_E_CANT_OPEN )) Screenshot of the error: Solution: Only way around is to restart the system. This can happen when the content is locked by some other user. It is also a Windows OS problem. Currently there is no fix from SAS Tech support. Few technical forums users said that this issue occurs commonly in remote desktop client.

Issue While trying to login from SAS Enterprise Guide you may get following errors Unable to connect to metadata server Unable to parse the name value "APPLICATIONAME=SAS%20Enterprise%20Guide". The name is not recognized option. Solution: Entering wrong host name This error arise if you enter the wrong machine name. In SAS Enterprise Guide, check whether you have given correct hostname and port number. Check for spelling mistakes and leading spaces after the host name. If you are not sure what the host name is, you can get the details from your SAS Admin. User not member in OS level This error will also occurs if you doesn't belong to OS level. You should be a member of atleast one group to the host you are connecting. Using EG 6.1 to connect SAS 9.2 or below environment If the user has SAS Enterprise Guide 6.1 and trying to access SAS 9.2 environment this issue occurs. However, in SAS support it is told that SAS EG 6.1 is compatible with SAS 9.2 but I was

Issue: Error message pops up during the export function. Local SAS is required for this operation Screenshot: Instructions to fix the issue In SAS Enterprise Guide, in the menu bar click view servers. Check whether the Local server is desplayed. If not, go to Tools -> SAS Enterprise Guide Explorer. In the window, click File  -> Manage Profiles A new window opens, in the left coloumn click on Server and tick the Automatically add local SAS server (if installed) to server list box. Workaround: If your aim is to store SAS dataset  in your local PC, you can alternatively use following method to download. Go to Tasks -> Data -> Download Data Files to PC . This will download directly from the workspace server which will be faster than export. 

Issue:   SAS script has been failing on connection between SAS and Oracle. A driver update was performed to fix French accents, but created other issues. When accessing a Oracle view, I’m getting the error : Error fetching from cursor. ORACLE error is ORA-01843: not a valid month. Solution: Check for SAS KB article - 20734 : An error occurs when data that has any date format is loaded to Oracle in a non-English environment It seems, this error occurs if you load data with date format to Oracle in French environment (non-English). There is hot-fix available for this issue. The error won't pops-up if hotfix is installed.

This article helps you to understand what happens during metadata server start up and how to resolve Metadata Server 1 is not up issue. Configuration files read by Metadata server during start up The first step to diagnose Metadata server start up problem is to check any changes are made to config files. Metadata server start-up pattern 1. Meta data server first read the omaconfig.xml file. This file gives direction to the repository manager. 2. Repository manager will have the list of metadata repository. 3. Finally metadata server connects to the registered metadata repository. Check for changes in omaconfig.xml file If any modification were made to omaconfig.xml file there are very good chances Metadata server won't start. Check sas.servers script To bring up SAS Metadata Server we will use sas.servers script. If any changes are made to this script then it won't bring up  the server. Below is the script that we run in our environment.

Issue: When a user try to login in SAS Enterprise Guide, a error pops up like You are not defined as a user in metadata and are connecting as public. It appears that the current authourizations will not allow the connection to continue. Please contact your administrator. Screenshot of Error SAS Enterprise Guide Login Error Solution The user is not added in Metadata level. You need to add the user using SAS Management Console. Once the user is added and given appropriate permission, the user will be able to access SAS EG. Since the user doesn't have any identity in Metadata it will be considered as PUBLIC user. The PUBLIC user doesn't have access by default.

Many users reported that while installing SAS Enterprise Guide 6.1, the installation gets hangs while installing SAS Intergration Technologies Client. It doesn't progress to next step even though if we wait for 1 hour. Below is the screenshot. In above figure, SAS deployment wizard used to install SAS EG client software. It freezes while installing SAS Intergration technologies client step for almost an hour. Errors: Install failed and rollback was not successful, exiting with error code 4 Solution: To avoid this, close all the background application. There should not be any background application running during installation. Applications like Outlook, Communicator, web browser ect should be closed. While re-installing, first un-install any components related to SAS 9.4. Go to control panel, Add/Remove program and un-install anything related to SAS. After un-installation is done, go to C drive -> program files and delete SASHome directory. After completing above

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi

In this article, you will get details about creating a new library using SAS Management Console. Here, I have provided the procedure for creating library for Oracle database. However, the steps will be same for other databases like SQL server, Teradata etc.     Creating connection to Oracle database: To create library, you must first create a connection to Oracle database in your host machine. Host machine is the physical location where your SAS platform is installed. Details like Oracle database hostname/IP address and DSN/SID name is needed. Those details should be entered in tsnnames.ora file. For more details check this article Creating library in SAS Management Console: The steps for creating library for Oracle using SAS Management Console (SMC) can used for other database like SQL Server, My SQL etc. New library wizard: Expand Data Library Manager plug-in, right click on the Libraries and click New Library to start library wizard.  You will be asked

In this article you can get information about OMACONIFG.xml file and how to set email alert using the option available in OMACONFIG.xml file. File location : SAS-configuration-directory/Lev1/SASMeta/MetadataServer Restart required : Yes, if changes are made to this file Metadata Server should be restarted for the change to take effect.  During metadata server start-up, omaconfig.xml file is read. Metadata server reads omaconfig.xml file to get the path of repository manager. It also have information like journaling options, library used by repository manager, internal users password policy and email alert emails. There are several other options that can be defined in OMACONFIG xml file, however, following tasks will be done frequently in OMACONFIG xml file. Frequent task in OMACONFIG xml file done by SAS Admin Provide ability to store credentials in a connection profile Connection profile is used by SAS desktop application like SAS Enterprise Guide to store user ID and p

Here you will get information about several option available in SAS that is used to manage repository. Metadata Manager Plug-in - Create, Register, Unregister, Delete Repository In SAS Management Console, you will be using Metadata Manager Plug-in to create and manage repositories. With Metadata Manager Plug-in you can create, register, delete and unregister a repository. Let's see what this four operations do and how it differs from each other. Create With this option you can create a new repository . It will create initial repository content and all the metadata content that defines the repository. Register It creates the metadata that defines the repository and points to existing repository content. Delete It deletes the all the metadata that defines the repository and repository content. Unregister It removes the the metadata that defines the repository but not repository content. Here you need focus on two things Metadata content repository content

In my project, our client widely use Oracle database for their data. I hope Oracle is widely used database. So here I will explain making connection from SAS to Oracle database, my routine activity . Also, you will find the common issues and how to rectify them. Exploring tnsnames.ora To make connection to Oracle database, we should make an entry in tnsnames.ora. The tnsnames.ora file will be inside Oracle DB client installation drive. By default installation directory and tnsnames.ora file will be in /base-directory/ oracle/product/11.2.0/client_1/network/admin/tnsnames.ora Base-directory = Can be any directory. What will be inside tnsnames.ora file? The tnsnames.ora file is a configuration file for Oracle client which holds information about the server. To make it simple, your machine needs to contact another machine and this entry holds the address of another machine. So what does the address will look like? The below image is the sample tns entry. TNS entry wi