Usage Note 63738: Your SASPy session fails with the error "SAS Connection failed. No connection established. Double check your settings in sascfg_personal.py file"
When you install and configure the SASPy interface for a local connection on a Microsoft Windows operating system, the following error can appear after you try to launch a SAS® session:
We failed in getConnection
The native implementation module for the security package could not be found in the path.
SAS process has terminated unexpectedly. RC from wait was: xxxxxxxxxx
SAS Connection failed. No connection established. Double check your settings in sascfg_personal.py file.
. . .
Be sure the path to sspiauth.dll is in your System PATH
This error occurs because the sspiauth.dll file, included in your SAS installation, is not included in your system PATH environment variables. Follow the instructions below to add the sspiauth.dll file to your system PATH variable. You need administrative privileges to perform these steps.
- Navigate to the SASHOME\SASFoundation\9.4\core\sasext directory.
- Search for the sspiauth.dll file to verify that it is included in your installation. If it is not present, contact SAS Technical Support.
- After you verify that the sspiauth.dll file is present, record its full directory path. Here is an example:
C:\Program Files\SASHOME\SASFoundation\9.4\core\sasext
- Navigate to Control Panel ► System and Security ► System ► Advanced system settings.
- Select Environment Variables.
- When the Environment Variables window appears, click the Path user variable to select it and click Edit.
- The Edit environment variable window should appear.
- In this window, select New and paste in the directory path that you recorded in Step 3.
- Click OK until you return to the main System window.
- Launch the command prompt to start a new SAS session using SASPy.
If the steps above did not resolve your issue, do the following:
- Take a screenshot of the window, with the new directory path that you inserted, from Step 8.
- Send the screenshot, as well as your sascfg_personal.py file, to SAS Technical Support.
Operating System and Release Information
| SAS System | Base SAS | Microsoft Windows 8.1 Enterprise 32-bit | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8.1 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8.1 Pro 32-bit | 9.4 | | 9.4 TS1M0 | |
| Windows 7 Professional x64 | 9.4 | | 9.4 TS1M0 | |
| Windows 7 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 Std | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 R2 Std | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 R2 Datacenter | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2012 Datacenter | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2008 for x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows Server 2008 R2 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 10 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8.1 Pro x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8 Pro x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft Windows 8 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
| Microsoft® Windows® for x64 | 9.4 | | 9.4 TS1M0 | |
*
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.
This SAS Note describes how to install and configure the SASPy interface on a Microsoft Windows operating system after you see an error regarding the sspiauth.dll file.
| Date Modified: | 2019-03-12 15:28:56 |
| Date Created: | 2019-02-25 19:46:37 |