The Schedule Manager plug-in does not send the SAS Workspace Server name to the SAS Object Spawner when you browse SAS^® programs that you want to deploy. This problem occurs when multiple SAS Workspace Servers are used, and it causes a possible authentication error message.

The problem happens under the following circumstances:

1. You have multiple application-server contexts for which users have different authorization access.
2. When a user attempts to deploy a DATA step batch job, they specify the DATA step batch server for the application-server context to which they have permissions.
3. Then, the user clicks the Browse button to choose the program that they want to schedule. This action initiates a request for the workspace server.

Because the workspace server name is not sent in the request, the objects spawner checks the authorization for the first workspace server that it selects. As a result, the authorization might fail.

A workaround is available for releases before the second maintenance release for SAS^® 9.3 (TS1M2). The workaround is to define individual port numbers for each of the SAS Workspace Servers that are defined in the environment.

Currently, there is no workaround or solution for releases later than SAS 9.3 TS1M2.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Management Console 9.3_M2 is available at:

A fix for this issue for SAS Middle Tier 9.3_M2 is available at: