Overview

SAS Enterprise Guide includes a built-in scheduler. When you schedule a SAS Enterprise Guide project via the SAS Enterprise Guide scheduler, a Visual Basic script is created. This script is executed in accordance with the parameters that are supplied to the Windows Scheduler plug-in. If both the SAS execution server and the SAS Enterprise Guide client reside on a single machine, scheduling a project is straightforward. However, if SAS Enterprise Guide is configured to execute SAS processes on a remote server and the Workspace Server is configured to prompt, additional setup is required to enable the authentication process to complete. If logon credentials for the SAS Metadata Server are not cached on the client side, scheduling of SAS Enterprise Guide projects is not possible.

Configuring SAS Enterprise Guide for Passing Credentials to a Remote Server

This section explains how to configure SAS Enterprise Guide so that it passes your credentials to the remote server when you are not interactively logged on to your client machine.

1. Create the credentials.xml file

   Open a Windows Notepad session to create the credentials.xml file. This file stores your server logon credentials that are required for authentication when you run SAS Enterprise Guide in batch mode. The contents of your Notepad file should look similar to the following example.

   <xml FileVersion=”4.1”> <credentials> <server name=”SASMain” userid=”your-user-id” password=”your-password”/> <server name=”second-server” userid=”second-id” password=”second-password”/> <server name=”third-server” userid=”third-id” password=”third-password”/> </credentials> </xml>
   Notes:
   
   • Do not copy and paste this example to create your file. You must create your own, individual file.
   • The previous example is used for an environment with multiple application servers. However, you might have only one server, so your file would contain just one <server> line.
   • With SAS Enterprise Guide 4.2, 4.3, and 5.1, the first line of the Credentials.xml file reads as <xml FileVersion="4.2">, <xml FileVersion="4.3"> or <xml FileVersion="5.1">
   To avoid placing your plain-text password in the XML file, use the PWENCODE procedure to encode your password, as shown here:
   proc pwencode in='my-password'; run;
   After you encode your password in SAS, add the encoded password to the PASSWORD= paramenter in the XML file. Below is an example of the syntax for proc PWENCODE.
   

   Save your SAS Enterprise Guide 4.1 credentials.xml file to %appdata%\SAS\Enterprise Guide\4.

   Save your SAS Enterprise Guide 4.2 credentials.xml file to %appdata%\SAS\EnterpriseGuide\4.2\credentials.xml.

   Save your SAS Enterprise Guide 4.3 credentials.xml file to %appdata%\SAS\EnterpriseGuide\4.3\credentials.xml.

   Save your SAS Enterprise Guide 5.1 credentials.xml file to %allusersprofile%\SAS\SharedSettings\5.1\credentials.xml.

2. Schedule a project in SAS Enterprise Guide

After you complete Steps 1 and 2, your scheduled projects should run successfully. No additional configuration is required. For information about scheduling projects in SAS Enterprise Guide, see the Help and other documentation that is available within SAS Enterprise Guide.

Note: Should your scheduled project fail to execute as a result of an authentication error, a file called credentials.failed.xml is created in the same location as the credentials.xml file. This file maintains a list of all credentials or server IDs that have already failed. This list must be maintained so that SAS Enterprise Guide does not attempt to use the same credentials repeatedly to access a server. With SAS Enterprise Guide 4.2, 4.3, and 5.1, the credentials.failed.xml file must be deleted before a connection can successfully be made to the server on which the login failed.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Enterprise Guide	Microsoft Windows 2000 Advanced Server	4.1		9.1 TS1M3 SP4
		Microsoft Windows 2000 Datacenter Server	4.1		9.1 TS1M3 SP4
		Microsoft Windows 2000 Server	4.1		9.1 TS1M3 SP4
		Microsoft Windows 2000 Professional	4.1		9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter Edition	4.1		9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition	4.1		9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Standard Edition	4.1		9.1 TS1M3 SP4
		Microsoft Windows XP Professional	4.1		9.1 TS1M3 SP4
		Microsoft® Windows® for x64	4.2
		Microsoft Windows Server 2003 for x64	4.2
		Microsoft Windows Server 2008	4.2
		Microsoft Windows Server 2008 R2	4.2
		Microsoft Windows Server 2008 for x64	4.2
		Microsoft Windows Server 2012 R2 Std	4.2
		Microsoft Windows Server 2012 Std	4.2
		Windows 7 Enterprise 32 bit	4.2
		Windows 7 Enterprise x64	4.2
		Windows 7 Home Premium 32 bit	4.2
		Windows 7 Home Premium x64	4.2
		Windows 7 Professional 32 bit	4.2
		Windows 7 Professional x64	4.2
		Windows 7 Ultimate 32 bit	4.2
		Windows 7 Ultimate x64	4.2
		Windows Vista	4.2
		Windows Vista for x64	4.2
		Microsoft Windows 8 Enterprise 32-bit	5.1
		Microsoft Windows 8 Enterprise x64	5.1
		Microsoft Windows 8 Pro 32-bit	5.1
		Microsoft Windows 8 Pro x64	5.1
		Microsoft Windows 8.1 Enterprise 32-bit	5.1
		Microsoft Windows 8.1 Enterprise x64	5.1
		Microsoft Windows 8.1 Pro	5.1
		Microsoft Windows 8.1 Pro 32-bit	5.1

* 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 note explains how to configure SAS Enterprise Guide so that it passes your credentials to the remote server when you are not interactively logged on to your client machine.

Type:	Usage Note
Priority:

Date Modified:	2013-11-13 15:48:23
Date Created:	2008-01-11 16:24:12