Problems with the SAS IT Resource Management Client

If the SAS IT Resource Management client does not start, there might be a problem with the Java Virtual Machine (JVM) that is being used, or with the settings in the sasitrm.ini initialization file.

The JVM is specified in the sassw.config file. (By default, this file is located in C:\Program Files\SASHome\sassw.config). Make sure that it satisfies the criteria that are listed under the Third-Party Software Reference. In addition, make sure that this JVM is correctly installed at the specified location.
If you made any post-installation changes to the sasitrm.ini initialization file, verify that the changes were correctly made. Typographical errors can prevent the client from initializing properly.

If the client fails to connect to the metadata server that is specified in the login profile, verify the following items:

The metadata server is operational.
The metadata server is at an appropriate software version level for the client that you are using.
The metadata server machine itself is accessible from the client on the network.
The user ID and password are correct and the user can be properly authenticated on that server.

Some client operations create log files on the client machine, based on the Windows APPDATA environment variable. To see the current setting of the APPDATA environment variable, issue the following command in a DOS command prompt window:

SET APPDATA

The SAS IT Resource Management client creates logs during the execution of these tasks of the Adapter Setup wizard:

adding new aggregation tables
maintaining staged tables
creating an IT data mart

These logs can be found in -%APPDATA%\SASITResourceManagement\version. (For example, the logs for SAS IT Resource Management 3.3 can be found at %APPDATA%\SASITResourceManagement\33.)

Problems with the SAS Metadata Server

The metadata server log can be used to diagnose failures that are related to metadata, including failure to connect to the metadata server. This log is available in the SAS configuration directories, under the MetadataServer subdirectory, in a Logs folder. By default, the logs are time-stamped. An examination of the relevant log can show problems in authenticating users, problems in the metadata server configuration, and other issues.

The logging level for the metadata server can be changed to increase the level of detail. For information about changing the logging level and many other useful topics, see the SAS 9.3 Intelligence Platform: System Administration Guide.

For information about security and authentication, see the SAS 9.3 Intelligence Platform: Security Administration Guide.

Problems with the Object Spawner and Workspace Server

If the SAS IT Resource Management client can successfully connect to the appropriate metadata server, but the user cannot start a workspace server session, verify that the object spawner is correctly started on the appropriate server machine.

Also verify that the user is correctly authorized to create workspace server sessions.

By default, the object spawner performs only limited logging . However, both the object spawner and, specifically, the workspace server can have the level of logging detail increased. All servers, such as the SAS Metadata Server, the object spawner, and the application and workspace servers, can be configured to have logs. These logs can be useful in diagnosing problems. For information about configuring logging for these servers, see “Administering Logging for SAS Servers” in the SAS 9.3 Intelligence Platform: System Administration Guide.

For information about configuring servers, including setting up users and groups, see the SAS 9.3 Intelligence Platform: Installation and Configuration Guide. This document also includes a troubleshooting appendix.

Client Logging Files

The IT Resource Management Client automatically keeps log files for certain operations such as the following:

creating an IT data mart
running the Adapter Setup wizard
adding staged tables

These log files can be useful to you or to Technical Support personnel, when investigating a problem.

On the client, these log files are located in a directory that is determined based on the APPDATA environment variable.

On Windows XP, this location is typically C:\Documents and Settings\userid\Application Data\SASHome\SASITResourceManagement\3.3.
On Windows 7, this location is typically C:\Users\userid\AppData\Roaming\SASHome\SASITResourceManagement\3.3.

Server Logging Files

All servers, such as the SAS Metadata Server, the object spawner, and the application and workspace servers, can be configured to have logs. These logs can be useful in diagnosing problems. For information about configuring logging for these servers, see “Administering Logging for SAS Servers” in the SAS Intelligence Platform: System Administration Guide.

Turning On Standard Execution-time Debugging (ETLS_DEBUG)

To turn on execution-time debugging in the generated code for SAS Data Integration Studio and SAS IT Resource Management transformations, add the following line to the generated code, before the transformation for which you would like additional debugging information: %LET ETLS_DEBUG=1;

Turning On Additional Execution-time Debugging (LOGGERLEVEL)

To turn on additional execution-time debugging information in the generated code for SAS IT Resource Management transformations, add or edit the following line to the generated code before the transformation for which you would like additional debugging information: %LET LOGGERLEVEL=[level];

This is the standard way of turning on debugging transformations in SAS IT Resource Management. (For SAS IT Resource Management 2.7 users, the LOGGERLEVEL flag replaces the CPDEBUG macro flag).

Legal values for [level] include: FATAL, ERROR, WARN, INFO, DEBUG, or TRACE. Users who want additional debugging information should set the level to DEBUG:

%LET LOGGERLEVEL=DEBUG;

Investigating Problems Using Java from SAS Foundation

Some features that use Java from SAS Foundation. These features include PROC INFOMAPS, the Information Map LIBNAME engine, and the migration of IT Resource Management 2.7 PDBs to IT data marts supported in SAS IT Resource Management 3.3 and later. For problems in running Java from SAS, use the following techniques to investigate whether SAS is configured correctly to use Java:

Verify that the Java JVM can be started, and that it is the correct version of the JVM. To do so, submit this SAS statement:
```
proc javainfo all; run; 
```
The results of this code will include JVM details and properties. This statement can be added to the SAS code of a deployed job, or submitted directly from the ToolsSource Editor menu item in SAS Data Integration Studio.
Check the JREOPTIONS settings to make sure that the Java options are correct, particularly in these elements:
- Memory options such as -Xmx are specified according to the installation and configuration documents.
- To see the current JREOPTIONS, submit this SAS statement:
  Proc options option=jreoptions; run;
  
  This statement can be added to the SAS code of a deployed job, or submitted directly from the ToolsSource Editor menu item in SAS Data Integration Studio.

Note: When running jobs in SAS Foundation, make sure that SAS is invoked using the appropriate configuration files because these files have been written specifically for use by SAS IT Resource Management.

Troubleshooting Error Messages in the SAS Log

Error message is displayed in the SAS log: “ERROR: Failed to insert filter” or “ERROR: Failed to insert data source.”

Make sure that the user who is running the job has the proper authorizations. To do so, open the SAS Management Console and perform the following steps:

Set the repository to Foundation.
In the User Manager component, select the user profile of the person who is running the job.
On the Logins tab, locate the entry for the authentication domain of the workspace server that was in use at the time of the error. (Each workspace server has an authentication domain.) The user ID and the password should be specified. The password cannot be left blank.

Note: Whenever the server is reset, the password might not have been saved. (A password field of asterisks does not necessarily contain your password.) In this case, you should manually update your password.

Debugging Problems in SAS IT Resource Management