Problem Note 56110: Creating a new project gives a "Specified SAS Server Directory does not exist" error when the workspace server is in a lockdown state
When you attempt to create a new SAS® Enterprise Miner ™ project, the following error might be displayed. You are not able to create the project.
Specified SAS Server Directory does not exist.
The error is displayed when these two conditions are true:
- the workspace server is in a lockdown state.
- you attempt to create a project in a folder where the PARENT folder is not in the whitelist.
With the lockdown feature enabled, the error is generated based on whether the PARENT directory of the current path is in the whitelist. To resolve the error, you can perform either of the following workarounds:
- Add the PARENT directory to the whitelist.
- Create an additional directory to the PATH and then specify that PARENT in the whitelist.
Example: The projects folder is C:\EMProjects. A members list is retrieved for C:\ when testing for the existence of C:\EMProjects. If C:\ is not in the whitelist, then the members list cannot be retrieved, and the above error is displayed. To avoid this error, C:\ needs to be listed in the whitelist
Suppose that you want all projects to be confined to C:\EMProjects but do not want to open up the parent C:\ in the whitelist. Add another level for the storage location. Example: C:\EMProjects\projects.
Then add the parent, C:\EMProjects, in the whitelist and specify C:\EMProjects\projects for the project path.
The lockdown feature became available in SAS® 9.4M1. For further information about lockdown and whitelist, see Locked-Down Servers in this document: SAS(R) 9.4 Intelligence Platform: Security Administration Guide.
Operating System and Release Information
SAS System | SAS Enterprise Miner | Microsoft® Windows® for x64 | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows 8 Enterprise x64 | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows 8 Pro x64 | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Enterprise 32-bit | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Enterprise x64 | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Pro | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Pro 32-bit | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows Server 2008 R2 | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows Server 2008 for x64 | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 Datacenter | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 R2 Datacenter | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 R2 Std | 13.2 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 Std | 13.2 | | 9.4 TS1M0 | |
Windows 7 Enterprise x64 | 13.2 | | 9.4 TS1M0 | |
Windows 7 Professional x64 | 13.2 | | 9.4 TS1M0 | |
64-bit Enabled AIX | 13.2 | | 9.4 TS1M0 | |
64-bit Enabled Solaris | 13.2 | | 9.4 TS1M0 | |
HP-UX IPF | 13.2 | | 9.4 TS1M0 | |
Linux for x64 | 13.2 | | 9.4 TS1M0 | |
Solaris for x64 | 13.2 | | 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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2015-07-17 09:49:17 |
Date Created: | 2015-07-02 15:58:32 |