Installation instructions for hot fix W67007 on Windows for x64

Installation Instructions for Hot Fix W67007

Windows for x64

Hot fix W67007 addresses the issue(s) in LASR Analytic Server 2.7 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/W67.html#W67007

W67007 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

W65002 updates Advanced Programming for SAS LASR Analytic Server 2.6
V48008 updates SAS Threaded Kernel Extensions for LASR Analytic Server 2.7
Y34002 updates SAS LASR Analytic Server Access Tools 2.7
A7L001 updates SAS LASR Analytic Server 2.7

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, W67007x6.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save W67007x6.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of W67007x6.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.
CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.

INSTALLATION

Hot Fix W67007 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of LASR Analytic Server 2.7 require updating on the machine. See SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager. By default, the SAS Deployment Manager will search in the <SASHOME>\InstallMisc\HotFixes\New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading W67007x6.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.

The hot fix installation process generates the log file

<!SASHOME>\InstallMisc\InstallLogs\IT_date-and-time-stamp.log

for example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the 'member' hot fix id in the name of the file and are also written to the <!SASHOME>\InstallMisc\InstallLogs directory. There is one postexec log for each 'member' hot fix applied (member hot fixes are listed at the top of these instructions).

The content of this hot fix is listed in the hot fix manifest.

POST-INSTALLATION INSTRUCTIONS

Required only for distributed deployments:
As part of the client install, the hot fix installs an executable file called lasr.so that must also be manually copied to the computing appliance. On Linux for x64, this file is installed in <SASHome>/SASFoundation/9.4/sasexe/lasr.so. This file should be copied under the TKGrid install location on the computing appliance; for example, /opt/TKGrid/lib. When copying the file, make sure the proper mode of 755 is set.

If your computing appliance uses a shared install, you need to copy lasr.so only to the shared location. However, if your computing appliance uses a replicated install, you must copy lasr.so to every node.

Additionally, if the TKGrid installation script to enable sashdat file encryption (TKGrid_SEC_x86_64.sh) has been run on the computing appliance, then you will need to remove the copy of lasr.so from the TKGrid/lib2 location. The TKGrid/lib2/lasr.so executable file would need to be removed from all nodes in a replicated install.