SAS Tips

Creating global SAS Data Library may run into issues where registered tables do not appear.  It is often a tedious task to determine where the issue lies; CLI, Driver, Permission, or something else.  A tracing/debug log often points to the root cause much faster than chasing different what if scenarios.  Following are two options that produce trace logging for SAS Management Console.

Modify the sasmc.ini file to add the -metalibdebug option. The sasmc.ini is typically located in : C:\Program Files\SASHome\SASManagementConsole\9.4. Add the option to the end of the MainClass assignment. It will look similar to this:

MainClass=com.sas.console.visuals.MainConsole -metalibdebug

1. Create a backup of the sasmc.ini file
2. Add the option at the end of the MainClass string as shown in lab sample below
3. Save and close sasmc.ini. Open a NEW instance of SAS Management Console. Register a table to reproduce the CLI error.

 The Register Tables Wizard will produce a log that you can view which contains trace level information for METALIB.  The details captured is useful to send to your SAS Tech support or for in-house troubleshooting.

1. In addition, you may also add options -debug -serverlog (See below).  Open a SAS Management Console session and re-create the issue. Then, immediately close the SAS Management Console session.  A log with default name SASMCErrorLog.txt which enables debug-level logging in your C:\Users\your-user-ID\AppData\Roaming\SAS\SASManagementConsole\9.x\ folder.

Log Location

Happy troubleshooting!