SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 31021: The Renew SAS® Software utility runs in quiet mode in SAS® 9.4, SAS® 9.3, SAS® 9.2, and SAS® 9.1

DetailsAboutRate It

Quiet/Silent mode enables you to renew your SAS software license without user input or the display of dialog boxes.

For SAS® 9.4 (TS1M3) and newer SAS® 9.4 versions

Use SAS® Deployment Manager (sasdm.exe) for SAS 9.4 (TS1M3) and higher.  Refer to page 3, "Renew SAS Software in Quiet Mode," in SAS Software License Renewal Instructions: SAS® 9.4 Foundation for Microsoft Windows and Windows for x64 Basic Deployment

For SAS® 9.4 (TS1M4) and earlier SAS® versions

To renew your SAS software in quiet mode, first locate the sasrenew.exe utility file on your hard drive. The default directory is one of the following:

  • !sasroot\core\sasinst\sasrenew
  • !sasroot\SASRenewalUtility\9.x\

Note: In the above, !sasroot is the location in which you installed SAS, and 9.x is the version of SAS installed, such as 9.2, 9.3, or 9.4.

The user ID logged on to the machine must have administrator rights, and the files and folders in the !sasroot directory cannot be set to "Read only."

If the system is a Windows 7 operating system, review the Windows 7 information below. Then, run one of the following commands (for your version of SAS) from a command prompt window.

 

Example for SAS® 9.4 (TS1M4) and earlier SAS® 9.4 versions

"C:\Program Files\SASHOME\SASRenewalUtility\9.4\SASRenew.exe" -s "datafile:c:\SAS94_order-number_site-number_host-platform.txt"

For 32-bit SAS on a 64-bit operating system:

"C:\Program Files\SASHOME\x86\SASRenewalUtility\9.4\SASRenew.exe" -s "datafile:c:\SAS94_order-number_site-number_host-platform.txt"

Note: The spacing must match exactly as shown above. There is one space before the -s.

 

Example for SAS® 9.3 

"C:\Program Files\SASHOME\SASRenewalUtility\9.3\SASRenew.exe" -s "datafile:c:\SAS93_order-number_site-number_host-platform.txt"

For 32-bit SAS on a 64-bit operating system:

"C:\Program Files\SASHOME\x86\SASRenewalUtility\9.3\SASRenew.exe" -s "datafile:c:\SAS93_order-number_site-number_host-platform.txt"

Note: The spacing must match exactly as shown above. There is one space before the -s.

 

Example for SAS® 9.2 

"C:\Program Files\SAS\SASFoundation\9.2\core\sasinst\sasrenew\sasrenew.exe" -s "datafile:c:\SAS92_order-number_site-number_host-platform.txt"

For 32-bit SAS on a 64-bit operating system:

"C:\Program Files\SAS\SASFoundation\9.2(32-bit)\core\sasinst\sasrenew\sasrenew.exe" -s "datafile:c:\SAS92_order-number_site-number_host-platform.txt"

Note: The spacing must match exactly as shown above. There is one space before the -s.

 

Example for SAS® 9.1

"C:\Program Files\SAS\SAS 9.1\core\sasinst\sasrenew\sasrenew.exe" -s "datafile:c:\SAS91_order-number.txt"
Note: The spacing must match exactly as shown above. There is one space before the -s.
 

Was the SID File Applied Successfully?

One way to determine whether the SAS installation data file was applied successfully is to search the setinit.log file for the text "Siteinfo data have been updated" and the new expiration date. Here are the default directories for the setinit.log file:

  • The default directory for the setinit.log file for SAS 9.1 is c:\Program Files\SAS\SAS 9.1\.

  • The default directory for the setinit.log file for SAS 9.2 is c:\Program Files\SAS\SASFoundation\9.2 or for 32-bit SAS on 64-bit operating system c:\Program Files\SAS\SASFoundation\9.2(32-bit).

  • The default directory for the setinit.log file for SAS 9.3 is c:\Program Files\SASHOME\SASFoundation\9.3 or for 32-bit SAS on 64-bit operating system c:\Program Files\SASHOME\x86\SASFoundation\9.3.

  • The default directory for the setinit.log file for SAS 9.4 is c:\Program Files\SASHOME\SASFoundation\9.4 or for 32-bit SAS on 64-bit operating system c:\Program Files\SASHOME\x86\SASFoundation\9.4.

If an interactive error window appears, or if the setinit.log file is not updated, see SAS Note 34916, "Software updates might fail and no error messages are displayed when you run the Renew SAS® Software utility in quiet mode."

 

Windows 7

If you are automating the license renewal process, be aware that provisioning software such as SMS, SCCM 2007, and others use the SYSTEM account when deploying software across an enterprise. For SAS 9.2 and SAS 9.3, the CSIDL_PERSONAL variable is defined by default for the SASUSER library, and during the renewal process depends on the user's My Documents path. However, on Windows 7, the SYSTEM account Documents folder does not exist. So, it is necessary to add it before you run the Renew SAS Software utility. Here is one approach to creating the documents folder beneath the systemprofile folder:

  • The SYSTEM account default path is %windir%\system32\config\systemprofile.
  • Administrators can package a pre-installation command such as this:

    cmd.exe /c "mkdir %windir%\system32\config\systemprofile\Documents\"

For SAS 9.4, the ?CSIDL_PERSONAL value is not used. Therefore, the SYSTEM account Documents folder is not necessary. Instead, the temporary files are written to SASHOME\InstallMisc folder during the renewal process.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemN/AMicrosoft Windows Server 2003 Datacenter Edition9.1 TS1M3 SP4
Microsoft Windows NT Workstation9.1 TS1M3 SP4
Microsoft Windows 2000 Professional9.1 TS1M3 SP4
Microsoft Windows 2000 Server9.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server9.1 TS1M3 SP4
Microsoft Windows 2000 Advanced Server9.1 TS1M3 SP4
Microsoft® Windows® for x649.1 TS1M3 SP4
Microsoft Windows XP 64-bit Edition9.1 TS1M3 SP4
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.1 TS1M3 SP4
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M3 SP4
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M3 SP4
Microsoft Windows Server 2003 Standard Edition9.1 TS1M3 SP4
Microsoft Windows XP Professional9.1 TS1M3 SP4
Windows Vista9.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.