Base SAS 9.4_M2 Hot Fix Downloads

NOTE: If you install this hot fix and have SAS/ACCESS Interface to ODBC 9.4M2 installed, you must also install hot fix V58001 for SAS/ACCESS Interface to ODBC 9.4M2.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Microsoft SQL Server 9.4M2 installed, you must also install hot fix V62001 for SAS/ACCESS Interface to Microsoft SQL Server 9.4M2.

Released: October 23, 2015

Documentation: R19040wn.html

Download: R19040wn.zip

Top ^

R19041 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

53287

Using the $VARYING. format in a LINE statement in PROC REPORT might generate more output than you expect in the LISTING destination

R19004

54932

GROUP or ORDER variable values might be blank or incorrect when written out via a LINE statement in a COMPUTE BEFORE _PAGE_ block in PROC REPORT

R19028

56398

Background colors might not be applied correctly to headings in PROC REPORT output

R19041

Released: September 29, 2015

Documentation: R19041wn.html

Download: R19041wn.zip

Top ^

R19042 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

56585

A segmentation violation might occur when you use the WEBDAV access method in a FILENAME statement to call a macro

R19042

Released: September 18, 2015

Documentation: R19042wn.html

Download: R19042wn.zip

Top ^

R19043 was replaced by R19076

R19044 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

56238

The EURO and EUROX formats do not display the Euro symbol with EBCDIC1145 encoding

R19044

Released: October 08, 2015

Documentation: R19044wn.html

Download: R19044wn.zip

Top ^

R19045 was replaced by R19059

R19046 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

56753

Refreshed SAS® OLAP cubes with updated dimension formats might return the error "Member name not found in cube"

R19046

Released: October 16, 2015

Documentation: R19046wn.html

Download: R19046wn.zip

Top ^

R19047 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54321

Enabling the DBIDIRECTEXEC LIBNAME option with the SAS/ACCESS® Interface to Impala

R19008

56478

An error occurs when you use the CAST=YES LIBNAME option with an ORDER BY clause or a SELECT DISTINCT clause in SAS/ACCESS® Interface to Teradata

R19047

NOTE: If you install this hot fix, you must also install hot fix R19059 for Base SAS 9.4M2.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Impala 9.41 installed, you must also install hot fix R80002 for SAS/ACCESS Interface to Impala.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Hadoop 9.4_M2 installed, you must also install hot fix S64002 for SAS/ACCESS Interface to Hadoop.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.4_M2 installed, you must also install hot fix W07002 for SAS/ACCESS Interface to Teradata.

Released: October 28, 2015

Documentation: R19047wn.html

Download: R19047wn.zip

Top ^

R19048 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

56915

The ODS PDF statement writes an empty PDF file to disk even when no output is generated

R19048

Released: November 16, 2015

Documentation: R19048wn.html

Download: R19048wn.zip

Top ^

R19050 was replaced by R19073

R19051 was replaced by R19059

R19052 was replaced by R19058

R19054 was replaced by R19076

R19055 was replaced by R19073

R19056 was replaced by R19059

R19058 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

56944

The PROC SORT NOUNIQUEKEY option is not honored when the host sort interface is used

R19052

57881

When you use PROC SORT to sort encrypted data stored in a metadata-bound library, you receive "ERROR: Missing ENCRYPTKEY option on member..."

R19058

Released: April 13, 2016

Documentation: R19058wn.html

Download: R19058wn.zip

Top ^

R19059 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54321

Enabling the DBIDIRECTEXEC LIBNAME option with the SAS/ACCESS® Interface to Impala

R19007

54127

An ambiguous reference error might occur when you join SAS® Scalable Performance Data Server tables using implicit pass-through

R19021

54658

When you submit a query with a WHERE clause, you might get unexpected results

R19021

54708

ALERT - Incorrect results might occur when you use the SQL procedure with a DBMS table

R19021

54915

An abend might occur when you are accessing a SAS® Scalable Performance Data Server table on a Linux x64 system

R19021

56978

A Read access violation error might occur when you are running an SQL procedure query

R19021

56256

Querying a relational DBMS table using the IN clause operator might return unexpected results

R19034

56478

An error occurs when you use the CAST=YES LIBNAME option with an ORDER BY clause or a SELECT DISTINCT clause in SAS/ACCESS® Interface to Teradata

R19045

50790

An SQLPLAN error might occur when you query a database management system (DBMS) table and the query includes a LENGTH= modifier

R19051

50801

Implicit pass-through processing might be disabled, resulting in performance issues

R19051

56977

An incorrect query might be passed to a database when a CASE expression is used in a WHERE clause

R19051

56979

A segmentation violation or Read access violation might occur when you are accessing a DBMS table via the SQL procedure

R19051

56981

A simple join might not be not passed to the database, resulting in poor performance

R19051

57014

Using a PUT function with SAS/ACCESS® Interface to ODBC might cause a segmentation violation in Base SAS®

R19051

57043

Macro variables SYSRC, SYSERR, and SQLRC are not being set when "Error on server LIBNAME socket" occurs on the SAS® Scalable Performance Data Server

R19056

57936

ALERT - When used with a single argument, the COALESCE() function is not passed down to the relational database management system (RDBMS)

R19056

57042

An ORDER BY clause in a PROC SQL statement is ignored in rare cases

R19059

NOTE: This hot fix is available for PC and UNIX platforms. Customers running on z/OS must install hot fix R19056 instead.
NOTE: If you install this hot fix, you must also install hot fix R19047 for Base SAS 9.4M2.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Impala 9.41 installed, you must also install hot fix R80002 for SAS/ACCESS Interface to Impala.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.4_M2 installed, you must also install hot fix W07002.

Released: May 16, 2016

Documentation: R19059wn.html

Download: R19059wn.zip

Top ^

R19060 was replaced by R19073

R19061 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54246

The error "sas.exe has stopped working" occurs when you are working in an interactive SAS® session

R19009

54940

In SAS® 9.4 on UNIX, a fatal error occurs when using the FILENAME PIPE engine to ftp a file with RECFM=S370VB

R19026

55256

In a UNIX environment, if you use a FILENAME statement to assign a fileref to a named pipe, the SAS® process might become unresponsive

R19030

58671

ALERT - In Linux environments, a SYSTASK statement might fail with a segmentation violation error

R19061

NOTE: Customers running on WX6 and WIN must install hot fix R86003.

Released: July 26, 2016

Documentation: R19061wn.html ^D

Download: R19061wn.zip

^D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.

Top ^

R19063 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54662

A LIBNAME statement that uses the META engine to Netezza creates too many connections to the database

R19022

54761

The message "Error during in-database processing" is generated when you assign the META LIBNAME engine to a Netezza library

R19022

56354

The error "Invalid option name. . ." occurs when you use the METALIB procedure

R19038

56563

Running a PROC SQL query against a database table might result in a Segmentation Violation

R19038

58625

Error and warning messages are generated when you use the METALIB procedure to register or update metadata for a Hadoop table

R19063

Released: August 23, 2016

Documentation: R19063wn.html

Download: R19063wn.zip

Top ^

R19071 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

59697

Under z/OS, your job fails and returns "ERROR: A bug in SAS has been encountered...zprldx: invalid prlstr"

R19071

Released: March 22, 2017

Documentation: R19071wn.html

Download: R19071wn.zip

Top ^

R19073 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

53966

A "Segmentation violation" error might be generated when referencing a macro variable in a %DO loop

R19001

54549

A SAS® program that uses PROC PRINTTO with a FILENAME that uses the EMAIL engine fails with a system 0C4 in SAS® 9.4

R19018

54551

"WARNING: The data for boxes is incomplete or invalid. Some boxes will not be drawn." might be issued when you create box plots with ODS Graphics

R19018

54723

Large user-defined formats might cause an insufficient memory message and a message about insufficient contiguous storage

R19029

55062

The INTNX function sets the DATA step variable _ERROR_ to 1 if a missing value is used as an argument in SAS® 9.4

R19029

54989

An error occurs when you use PROC COPY to copy a metadata-bound data set with a recorded encryption key to a non-bound library

R19031

55332

When you export data to Teradata from a product such as SAS® Enterprise Guide®, date and datetime values do not appear in the proper format

R19031

57105

The PLM procedure might end abnormally when the item store includes model variables with associated formats

R19050

57692

PROC REPORT data might be missing when it is replayed with PROC DOCUMENT

R19055

52698

A user 1319 abend occurs in a SAS/SHARE® server

R19060

61157

When you try to access tables in a metadata-bound library using SAS/SHARE®, the tables incorrectly require an ENCRYPTKEY to open

R19073

NOTE: If you install this hot fix and need the fix documented in SAS Note 55345, you must also install Base SAS hot fix R31004.

Released: October 13, 2017

Documentation: R19073wn.html

Download: R19073wn.zip

Top ^

R19074 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

61196

Output sent to the body of an SMTP email might not be displayed correctly if the email includes an attachment

R19074

Released: October 10, 2017

Documentation: R19074wn.html

Download: R19074wn.zip

Top ^

R19075 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

61764

Base SAS® 9.4 crashes after after you select Help ► SAS Help and Documentation

R19075

Released: March 07, 2018

Documentation: R19075wn.html

Download: R19075wn.zip

Top ^

R19076 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54456

A sign-on with MP CONNECT can fail in Microsoft Windows operating environments where 8.3 filename support is disabled

R19015

56619

MP CONNECT sessions fail to start properly and return the error "Remote signon to RHOST canceled"

R19043

57392

The client becomes unresponsive when you use a simple Remote Library Services LIBNAME statement, which causes a crash in the SAS/CONNECT® server

R19054

62319

Connections might become disconnected and return "ERROR: Conversations terminated..." when you use SAS/CONNECT® software

R19076

63215

A segmentation violation occurs in a SAS/CONNECT® client session when you use the CONNECTKEEPALIVE environment variable

R19076

Released: March 20, 2019

Documentation: R19076wn.html

Download: R19076wn.zip

Top ^

R78002 for Windows

SAS/GRAPH ActiveX Control 9.42 hot fix for Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54364

GUI issues such as missing options and large dialog boxes occur when you use the Traditional Chinese edition of 32-bit SAS® 9.4

R78002

NOTE: This hot fix is applicable to systems with the following language installed: Chinese Traditional (Taiwan)

NOTE: If you install this hot fix, you must also install hot fixes R19002 and R95001.

Released: October 20, 2014

Documentation: R78002wn.html

Download: R78002wn.zip

Top ^

R84001 was replaced by R84017

R84002 was replaced by R84017

R84003 was replaced by R84009

R84004 was replaced by R84017

R84005 was replaced by R84017

R84006 was replaced by R84017

R84007 was replaced by R84010

R84008 was replaced by R84017

R84009 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54201

SAS® LASR™ Analytic Server queries that use IN statements with 10 or more elements might perform poorly

R84001

55335

PROC DS2 code that uses a custom PROC FCMP function might produce errors when it is run on a remote server

R84003

56980

PROC FCMP step fails with "ERROR: File LIBREF.DATASET.DATA does not exist."

R84009

Released: November 04, 2015

Documentation: R84009wn.html ^D

Download: R84009wn.zip

^D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.

Top ^

R84010 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

56197

You cannot reset the return code condition for a SAS® Stored Process in SAS® 9.4

R84007

45482

The SAS® Stored Process Server might stop functioning if a SAS® Stored Process does not clear a SAS/SHARE® engine libref

R84010

Released: December 08, 2015

Documentation: R84010wn.html

Download: R84010wn.zip

Top ^

R84011 was replaced by R84017

R84012 was replaced by R84017

R84013 was replaced by R84017

R84014 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

57593

Leaving a metadata-bound table open when you exit a client like SAS® Studio might cause the client to hang when restarting

R84014

Released: April 13, 2016

Documentation: R84014wn.html

Download: R84014wn.zip

Top ^

R84015 was replaced by R84017

R84016 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

59167

A 403 error occurs when you load segments into SAS® Customer Intelligence 360 from SAS® Customer Intelligence

R84016

Released: October 21, 2016

Documentation: R84016wn.html

Download: R84016wn.zip

Top ^

R84017 for Windows

Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

55199

An upgrade of SAS® 9.4 software might fail or an out-of-memory condition might occur and result in the corruption of metadata

R84001

53770

An orphaned gridrun.exe process occurs when users close a SAS® Enterprise Guide® session that is running in a SAS® grid environment

R84002

53765

The load balancer might fail when it tries to reuse a grid-launched, pooled workspace server

R84002

53944

A SAS® Workspace Server connection failure can occur in SAS® Studio when you use SAS® token authentication

R84002

54629

SAS® Grid option sets do not work as expected

R84002

54819

High job submission rates might result in grid-launched workspace servers failing to start

R84002

55021

Clustered SAS® Metadata Servers lose their quorum status

R84002

55014

The SAS® import procedure fails and returns errors to the SAS® Metadata Server log file

R84002

55945

A SAS Metadata Server backup with the "Reorganize repositories" option enabled might damage the Foundation repository

R84004

56029

SAS® clients might receive a connection time-out message when you try to connect to a SAS® 9.4 Metadata Server cluster

R84005

56186

The object spawner might fail when you use load balancing with SAS® Cost and Profitability Management 8.1

R84006

56751

SAS® 9.4 Metadata Server cluster might become unresponsive after a user bulkload program is completed

R84008

57013

Load-balancing problems can occur if a SAS® Stored Process Server process fails to start

R84011

57224

Adding a new login containing a user ID that is already associated with an existing identity damages the Foundation repository

R84012

57367

A SAS® 9.4 metadata user bulk load can take many hours to complete when the SAS® Metadata Server is clustered

R84012

57428

In a SAS® Metadata Server cluster, the master node does not send redirection requests to a slave node that is a part of the quorum

R84013

58101

SAS® Metadata Server abnormally terminates with an "unhandled Exception" and the traceback indicates a failure in the KeepAliveThread

R84015

58452

All servers stop responding in a load-balanced cluster

R84015

55985

The error "Too many files are open" is logged when you have clustered SAS® Metadata Servers

R84017

59404

A vulnerability on authorizations to metadata table objects exists in SAS® Metadata Server

R84017

NOTE: You must also install hot fix R72003 for SAS Studio 3.2 to fully implement the fix for the issue described in 53944.

You must also install hot fix R33010 for SAS Threaded Kernel Grid to fully implement the fix for the issue described in 54819.

Released: February 23, 2017

Documentation: R84017wn.html

Download: R84017wn.zip

Top ^

R95001 for Windows

SAS Enhanced Editor 9.42 hot fix for Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

54364

GUI issues such as missing options and large dialog boxes occur when you use the Traditional Chinese edition of 32-bit SAS® 9.4

R95001

NOTE: This hot fix is applicable to systems with the following language installed: Chinese Traditional (Taiwan)

NOTE: If you install this hot fix, you must also install hot fixes R19002 and R78002.

Released: October 20, 2014

Documentation: R95001wn.html

Download: R95001wn.zip

Top ^

S28001 was replaced by S28008

S28002 was replaced by S28008

S28003 was replaced by S28008

S28004 was replaced by S28008

S28005 was replaced by S28008

S28006 was replaced by S28008

S28007 was replaced by S28008

S28008 for Windows

SAS/Secure SSL 9.4_M2 hot fix for Base SAS 9.4_M2

Issue(s) Addressed:

Introduced:

53953

Errors might occur when you connect to a server with SAS® clients and programs that use the Secure Sockets Layer (SSL) protocol

S28001

54374

ALERT - Secure Sockets Layer (SSL) capability in SAS® Foundation products is susceptible to the POODLE security vulnerability

S28001

54073

ALERT - OpenSSL security vulnerabilities (6 Aug 2014) exist in SAS/SECURE™ software

S28001

56161

Error messages appear in the SAS® log and the step terminates when you use the AUTHTLS option in the FILENAME FTP statement

S28002

55767

ALERT - OpenSSL security vulnerabilities (19 Mar 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products

S28003

56385

ALERT - OpenSSL security vulnerabilities (11 Jun 2015 and 9 Jul 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products

S28004

57686

OpenSSL security vulnerabilities (4 Dec 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products

S28005

58391

OpenSSL version 1.0.2h is available for SAS® 9.3 and 9.4 on UNIX and z/OS

S28006

58785

ALERT - The HTTP procedure generates an exception error

S28006

59244

OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 26 September 2016)

S28007

61700

OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 02 November 2017)

S28008

Released: February 16, 2018

IMPORTANT: Please contact SAS Technical Support for information on accessing this hot fix and reference SAS Note 61700

^D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.

Top ^

PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.

You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). this Code is designed to either correct an error in the Software or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.

SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ^® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.