The default ACT of a SAS^® 9.2 configuration denies all metadata access to the PUBLIC group. This is a major change from the SAS^® 9.1.3 default configuration. Due to this stricter security, you might encounter validation error messages during your deployment if you make any mistakes in defining a required external user (for example, SAS Demo User or SAS Server User).

When validating the workspace server, you might see this error message:

Details:

[1/14/10 1:50 PM] INFO: Starting simple validation for Workspace server (level 1) - ping
[1/14/10 1:50 PM] INFO: Ping successful!
[1/14/10 1:50 PM] INFO: Starting extended validation for Workspace server (level 1) - Making a connection
[1/14/10 1:50 PM] SEVERE: Client sasdemo@VISTA64-2010 does not have permission to use server SASApp - Workspace Server (A5Q5XTFX.AV000009).
[1/14/10 1:50 PM] SEVERE: The application could not log on to the server "vista64-2010.xx.xxx.com:8591".
[1/14/10 1:50 PM] SEVERE: The user "SAS Administrator" could not log on to the server "SASApp - Logical Workspace Server".

The error of interest is that the user does not have permission. If the account that you specified for validation does not match a defined Metadata Identity in User Manager, that account is considered PUBLIC and is indeed denied access to the server.

To correct the problem, define the SAS Demo User (or user of your choosing) in User Manager, or verify that one that was previously defined has a valid logon ID. You should also refresh your Object Spawner, because authentication decisions are now retained and are checked only once. Alternatively, restart the Object Spawner service.

To restart the Object Spawner, perform these steps:

1. Open SAS^® Management Console.
2. Go to the Server Manager plug-in and select SASMain - Spawner.
3. Expand to the lowest level of the spawner (for example, Vista-2010.xx.xxx.com)and locate the host entry.
4. Right-click and select Connect.
5. Right-click and select Refresh Spawner (not just Refresh, but Refresh Spawner).

Note:  When you click Refresh Spawner, you should see the following pop-up window:

Note:  You might see the following lines in your SAS 9.2 Object Spawner log:

Client xxxxxxx does not have permission to use server SASApp - Workspace Server (_id_).
Client connection nn for user xxxxxx has been stopped.

SAS Object Spawner Daemon III received non-break terminate exception (0).
START Perf.ARM.IOM.ObjectSpawner.ServerAdministration.StopServer 0 0
Processor has been stopped.
Orphaning server SASApp - Stored Process Server in process nnnnn.
Processor has been destroyed.

Operating System and Release Information