Usage Note 12519: Running SAS® Stored Processes that reside on a network drive
When you are running the SAS® Stored Process Server and executing SAS a
Stored Processes (with SAS code that resides on a network drive, the
server must be running under a user account that has access to the
network drive.
For example, if the SAS Stored Process Server is running on a user
account called HOSTAsassrv, this account might not be able to access
files on another network (for example, NETWORKB). If this is the case,
then you receive the following error message when you try to execute SAS
Stored Processes that reside on the NETWORKB network drive:
Stored Process Error
Error returned from stored process.
STP: The requested stored process \your
etworkpathpgmname.sas
does not exist.
By default, the SAS Stored Process server runs under an account called
sassrv on the local machine on which it was installed. If it is running
on a machine called HOSTA, then, by default, it would run under the
HOSTAsassrv user account. If this account does not have access to a
network drive where the SAS Stored Processesreside, HOSTB, the SAS
Stored Process server will need to run under another account that has
access to the HOSTB network drive.
To run SAS the Stored Process server under another user account, follow
these steps:
1. In your SAS® Management Console, go to User Manager > SAS General
Servers. Right-click and select Properties.
2. Select the Logins tab. Add a new Login user ID. Select New and
then define the new user ID. Click OK to save the settings.
3. In the SAS Management Console under Server Manager, go to the
lowest level node for your SAS Stored Process Server.
4. Right-click on the Stored Process Server and select Properties.
5. Select Options > Advanced Options. For Login, select the new
user ID that you defined in Step 2 above. Click OK to save the
settings.
6. Restart your object spawner to refresh its settings.
Note: To determine if a user account has access to a network drive,
log on to the machine using that user account. Then, try to
access the network drive from that user account.
Following is another approach to determine if the user account has
access to the network drive on Windows:
1. Bring up a DOS shell.
2. Issue the following command (where you substitute your
account name in place of sassrv):
> runas /user:sassrv cmd
You are prompted to enter the account password.
3. A new window will pop up that is running under the account
that you specified in the runas command.
In the newly-opened window, specify a command that is similar
to the following (where j is the drive that you are mapping
and \your.network.machinefolder is the network location):
> net use J: \your.network.machinefolder
If your J drive is already mapped, specify another drive.
If your net use command was successful, then your SAS Stored
Process Server should also be able to access your network
drive, provided that the Stored Process Server is running
under the account that you specified in the runas command.
Operating System and Release Information
| SAS System | SAS Integration Technologies | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M2 | |
| Microsoft Windows NT Workstation | 9.1 TS1M2 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M2 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M2 | |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M2 | |
| Microsoft Windows 2000 Server | 9.1 TS1M2 | |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M2 | |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M2 | |
| Microsoft Windows XP Professional | 9.1 TS1M2 | |
| Microsoft Windows 2000 Professional | 9.1 TS1M2 | |
*
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: | Usage Note |
| Priority: | |
| Topic: | System Administration ==> Servers ==> Integration Technologies
|
| Date Modified: | 2007-10-24 15:16:33 |
| Date Created: | 2004-06-04 14:34:09 |