Usage Note 34597: Attempts to sign on with the MP CONNECT facility in SAS/CONNECT® software might fail if spaces appear in the directory path
If you use SAS/CONNECT software's MP CONNECT facility to sign on and you have a directory path that contains spaces, the following error might occur:
NOTE: Remote signon to FOO commencing (SAS Release
9.01.01M3P020206).
ERROR: A communication subsystem partner link setup
request failure has occurred.
ERROR: SAS did not start properly. Please insure that
your sascmd value does not attempt to run SAS in the background.
ERROR: Remote signon to FOO cancelled.
First you should verify that the problem does not occur as a result of the issue described in SAS Note 2729,
'ERROR: SAS did not start properly. Please ensure that your sascmd value does not attempt to run SAS in the background." If this is not the problem and you can start the SAS® System locally on the server with the command in question, the problem might be a result of the fact that DOS short names are disabled.
For servers in Windows environments, whether short names are enabled or disabled is controlled by the NtfsDisable8dot3NameCreation registry key, which is found in HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Control\FileSystem.
In the registry key, a setting of 1 causes this problem. A setting of 0 enables short names, but it also requires you to uninstall and re-install SAS.
To solve this problem, follow these steps:
- From a command prompt, change directories to drive-name:\program files and submit this command:
fsutil file setshortname “Program Files” progra~1
- Then change directories to drive-name:\program files\sas 9.1 and run the following command:
fsutil file setshortname “SAS 9.1” sas9~1.1
Operating System and Release Information
| SAS System | SAS/CONNECT | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft® Windows® for x64 | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | |
| Windows Vista | 9.1 TS1M3 SP4 | |
*
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.
| Date Modified: | 2009-03-23 11:25:47 |
| Date Created: | 2009-01-26 12:31:02 |