Problem Note 13013: Attempting a SAS/CONNECT SIGNON to a remote Windows Server using SSPI
authentication may fail
When attempting a SAS/CONNECT SIGNON to a remote Windows 2003 or XP
Server running SAS 9.1.3 and using SSPI for authentication, the SIGNON
may fail with the following error:
Cannot start remote process.
ERROR: Script file interpretation terminated due to error.
NOTE: End of script file trace.
ERROR: A communication subsystem partner link setup request failure
has occurred.
ERROR: recv call failed, lost connection with client.
If installing the Spawner with the -z option, the following will be seen
in the spawner.dat file:
[84181651]found place for new variable.
[84181651]freeing old environment block.
[84181651]Add2Env: returning.
[84181651]AddEnvVars: exit.
[84181651]ERROR: Unable to start SAS session (OS error: 87).
message is: The parameter is incorrect.
[84181651]startjob: calling termuser...
It has been determined that this problem should only occur when using
Windows 2003 or Windows XP with terminal services.
A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:
http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#013013
For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#013013
Operating System and Release Information
SAS System | SAS/CONNECT | Microsoft Windows XP Professional | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Topic: | Software Components ==> Connect Spawner
|
Date Modified: | 2005-04-27 14:43:57 |
Date Created: | 2004-08-09 11:10:56 |