SAS/EIS Software: Administrator's Guide

Troubleshooting

Occasionally, after you set up the access control environment, some users might encounter problems when they try to access SAS/EIS software or run their applications. This section describes some techniques that you can use to determine the cause(s) and suggests possible solutions for correcting the following problems:

The access control system does not initialize.
Users are not able to log in.
The access control system does not initialize and you need to find out the current access control settings.
The defined access control restrictions are not being applied to a particular user.

What If the Access Control System Does Not Initialize?

When a user attempts to start an EIS application by using either the EIS or the RUNEIS command, one of the following error messages is displayed:

```
"The Access Control subsystem cannot be started
at this time. You will not be able to run the application. Please contact
your system administrator." 
```
The following are possible reasons that the user encountered a problem:
- The SASHELP.AC catalog does not exist.
- One or all of the access control data sets (PASSWD, GROUPS, ACL, and, optionally, LOG) cannot be accessed for any of the following reasons:
  - files deleted
  - files damaged
  - files open by another process or user
  - no file or directory authorization
  - different password on the files than the current access control key
  - remote session not active
  - any of the AF classes necessary to start access control are not available
  - you have specified an incorrect value for the EIS or RUNEIS command options, USER= or PASSWD=. Force an interactive login by removing the command options or by setting USER=' '.
```
"The Access Control subsystem is not active at
this time. Please start the system using the correct login procedure, or contact
your system administrator."
```
A possible reason that this message was issued is that the user has just activated access control and is trying to run an application without completely leaving the EIS session and all active EIS applications.

"Your Access Control account information cannot
be retrieved at this time. Please try again or contact your system administrator."

A possible reason that this message was issued is that the PASSWD data set in the ACL Root Path is not readable.

```
"Your Access Control account information is incomplete.
You will not be able to run the application. Please contact your system administrator."
```
A possible reason that this message was issued is that the group information for the user is missing from the PASSWD file. Make sure that the user is assigned to at least one group.

What If Users Are Not Able to Log In?

When users try to log in by typing their ID and password, they receive the following message repeatedly, although the values in the Userid and Password fields are correct:

"Invalid Userid/Password Pair. Try again."

A possible solution is to change the pw_encrypt option. See Querying ACL Setup Values and Password for more information.

When the Access Control System Does Not Initialize, How Can You Find Out the Current Access Control Settings?

Typically, you will enter and update the access control settings by using the windows provided with the access control feature. However, if the system does not initialize and you need to find out the current settings of some of the parameters, you a can get this information programmatically by using the access control utility programs. See Querying ACL Setup Values and Password for more information.

What If the Access Control Restrictions Are Not Being Applied for a Particular User?

If access control restrictions are not being a applied for a user, first check to see if the user belongs to more than one group. For users who belong to more than one group, the access control system applies only those restrictions that are defined for all groups to which the user belongs.

Chapter Contents
Previous
Next
Top of Page