The SAS Workspace Server or SAS Pooled Workspace Server do not start successfully if either the SAS Trusted User account or the SAS General Servers logon account is an unrestricted user. When this problem occurs, error messages appear in the SAS Object Spawner log file.

If you are validating the workspace server, the following errors appear in the log:

If you are validating the pooled workspace server, these errors appear in the log:

If you use SAS Management Console to run the Validate test for your SAS Workspace Server, you receive the following error message:

If you use SAS Management Console to run the Validate test for your SAS Pooled Workspace Server, you receive the following error message:

If you encounter these error messages, use SAS Management Console to verify the members of the SAS Administrator group, as follows:

1. Under the User Manager plug–in, select the SAS Adminstrator group.
2. Click the Members tab to show the members of this group. The SAS Trusted User and SAS General Servers groups should not be members of the SAS Administrator group.
3. If necessary, remove the SAS Trusted User and SAS General Servers groups from the SAS Administrator group.
4. Restart the SAS Object Spawner for these changes to take place.

You can also use the following methods to detect whether the SAS Trusted User account or the SAS General Servers logon account are unrestricted users:

• Log on to SAS Management Console with the sassrv user account. Then, check the message at the bottom of the window. If the message says sassrv as Unrestricted User, then the sassrv account is an unrestricted-user account.
• Log on to SAS Management Console with the sastrust@saspw user account. Then, check the message at the bottom of the window. If the message says sastrust@saspw as Unrestricted User, then the sastrust@saspw account is an unrestricted-user account.
• Under User Manager in SAS Management Console, check the Metadata Server: Unrestricted role. Verify that neither the SAS General Servers group (which uses the sassrv user logon account) nor the SAS Trusted User is a member of the role. Also, make sure that neither is a member of a group that is a member of this role.
• Check the adminUsers.txt file for the SAS^® Metadata Server to verify that neither sastrust@saspw nor sassrv is listed in this file.
• Under User Manager in SAS Management Console, check the Metadata Server: User Administration role. Verify that neither the SAS General Servers group (which uses the sassrv user logon account) nor the SAS Trusted User is a member of the role. Also, verify that neither is a member of a group that is a member of this role.

If your SAS Workspace Server or SAS Pooled Workspace Server still do not start successfully, then it should be helpful to turn on additional logging for your object spawner. For details, see SAS Note 34893, "Turning on additional logging for the SAS Object Spawner."

Note: The problem and solutions described in this note also apply to the SAS^® Stored Process Server, as explained in SAS Note 36244, "The SAS^® Stored Process Server fails to authenticate if the sastrust or sassrv account is an Unrestricted User account."

Operating System and Release Information