SAS Institute. The Power to Know
 
 
 

Base SAS 9.21_M3

Hot Fix Downloads for Windows

* General Information about Hot Fixes

B25001 was replaced by B25256

B25002 was replaced by B25259

B25003 was replaced by B25249

B25004 was replaced by B25227

B25005 was replaced by B25270

B25006 was replaced by B25259

B25007 was replaced by B25260

B25008 was replaced by B25106

B25009 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40108 Images missing from the "Help" pages in Japanese version of SASŪ 9.2 TS2M3 B25009
NOTE: This hot fix is applicable to systems with the following language installed: Japanese
Released: June 29, 2010     Documentation: B25009wn.html       Download: B25009wn.exe  
Top ^

B25012 was replaced by B25260

B25013 was replaced by B25241

B25014 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40209 SAS session using SPDE library hangs and does not finish B25014
Released: July 26, 2010     Documentation: B25014wn.html       Download: B25014wn.exe  
Top ^

B25016 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40188 CALL IS8601_CONVERT generates error messages if a null argument is passed to the routine B25016
Released: July 20, 2010     Documentation: B25016wn.html       Download: B25016wn.exe  
Top ^

B25018 was replaced by B25250

B25019 was replaced by B25079

B25020 was replaced by B25242

B25022 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40428 Read Access Violation might occur after closing a SAS/AFŪ Frame entry containing an SCL List Model attached to a Table Viewer control B25022
Released: August 18, 2010     Documentation: B25022wn.html       Download: B25022wn.exe  
Top ^

B25023 was replaced by B25260

B25026 was replaced by B25260

B25027 was replaced by B25249

B25028 was replaced by B25219

B25029 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40596 SASŪ 9.3 BI Clients and SASŪ Business Solutions cannot log on to SASŪ 9.2 servers B25029
Released: July 12, 2011     Documentation: B25029wn.html       Download: B25029wn.exe  
Top ^

B25030 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39183 Data corruption occurs when you use the SELECT DISTINCT statement in the SQL procedure to select distinct rows from a SAS table B25030
Released: September 08, 2010     Documentation: B25030wn.html       Download: B25030wn.exe  
Top ^

B25031 was replaced by B25242

B25032 was replaced by B25259

B25034 was replaced by B25260

B25035 was replaced by B25241

B25036 was replaced by B25260

B25038 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40339 NLDATM informat does not read some month values correctly B25038
Released: September 09, 2010     Documentation: B25038wn.html       Download: B25038wn.exe  
Top ^

B25039 was replaced by B25242

B25041 was replaced by B25111

B25043 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40916 The read timeout is limited to 30 seconds when you use the SASŪ 9.2 SOAP procedure with the Axis2 engine B25043
Released: September 21, 2010     Documentation: B25043wn.html       Download: B25043wn.exe  
Top ^

B25044 was replaced by B25261

B25046 was replaced by B25218

B25047 was replaced by B25249

B25048 was replaced by B25068

B25049 was replaced by B25218

B25050 was replaced by B25239

B25051 was replaced by B25256

B25052 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41012 Graphics output generated with ODS HTML might not display correctly on a UNIX machine that is configured for Japanese DBCS support B25052
Released: October 28, 2010     Documentation: B25052wn.html       Download: B25052wn.exe  
Top ^

B25054 was replaced by B25242

B25056 was replaced by B25250

B25057 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41424 "ERROR: Invalid string" or "ERROR: Requested function is not supported" might occur when attempting to create graphics output with ODS Graphics B25057
Released: November 02, 2010     Documentation: B25057wn.html       Download: B25057wn.exe  
Top ^

B25058 was replaced by B25260

B25059 was replaced by B25181

B25061 was replaced by B25218

B25062 was replaced by B25106

B25063 was replaced by B25259

B25064 was replaced by B25241

B25066 was replaced by B25219

B25067 was replaced by B25227

B25068 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41067 Using the XML92 engine might generate an error or shut down the SASŪ System when the data contains specific characters B25048
41765 XML output might be encoded unnecessarily when using either the XML or XML92 LIBNAME engine B25068
41772 A "Write Access Violation" error might be issued when using the XML92 LIBNAME engine with the SQL procedure B25068
Released: January 25, 2011     Documentation: B25068wn.html       Download: B25068wn.exe  
Top ^

B25070 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41922 ALERT - Metadata disappears or becomes corrupted after committing an update to a metadata object B25070
Released: December 22, 2010     Documentation: B25070wn.html       Download: B25070wn.exe  
Top ^

B25071 was replaced by B25260

B25072 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41663 Details window reporting total observations B25072
Released: December 23, 2010     Documentation: B25072wn.html       Download: B25072wn.exe  
Top ^

B25074 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42320 The Export wizard deletes files when prompting B25074
Released: March 03, 2011     Documentation: B25074wn.html       Download: B25074wn.exe  
Top ^

B25075 was replaced by B25256

B25076 was replaced by B25111

B25077 was replaced by B25242

B25078 was replaced by B25218

B25079 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40433 EFI, Proc Import, Import Wizard reads a value with a single quote incorrectly B25019
41767 Import:List Window blank when importing an external file using EFI and User-Defined Formats B25079
Released: February 24, 2011     Documentation: B25079wn.html       Download: B25079wn.exe  
Top ^

B25080 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41661 "Segmentation Violation In Task [ RANK ]" might be received when ranking a large data set with PROC RANK B25080
Released: January 13, 2011     Documentation: B25080wn.html       Download: B25080wn.exe  
Top ^

B25081 was replaced by B25239

B25082 was replaced by B25152

B25084 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42092 MINGUO format does not handle 3-digit year properly for widths 7 and 9 B25084
Released: January 18, 2011     Documentation: B25084wn.html       Download: B25084wn.exe  
Top ^

B25085 was replaced by B25111

B25086 was replaced by B25260

B25087 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42301 The PROC SQL LIKE operator exhausts memory when it is used with a DBCS version of SASŪ B25087
Released: March 03, 2011     Documentation: B25087wn.html       Download: B25087wn.exe  
Top ^

B25088 was replaced by B25249

B25090 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42187 SASŪ software becomes unresponsive when publishing large packages to WebDAV B25090
Released: March 11, 2011     Documentation: B25090wn.html       Download: B25090wn.exe  
Top ^

B25092 was replaced by B25218

B25094 was replaced by B25225

B25095 was replaced by B25111

B25096 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42469 AF applications will not work in Spanish, French and Polish B25096
NOTE: This hot fix is applicable to systems with one or more of the following languages installed: French, Polish, Spanish
Released: February 23, 2011     Documentation: B25096wn.html       Download: B25096wn.exe  
Top ^

B25097 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42555 Incorrect messages are possible in SASŪ Analytics modules with UTF-8 encoding enabled B25097
Released: March 15, 2011     Documentation: B25097wn.html       Download: B25097wn.exe  
Top ^

B25098 was replaced by B25254

B25099 was replaced by B25210

B25100 was replaced by B25242

B25101 was replaced by B25239

B25103 was replaced by B25259

B25104 was replaced by B25218

B25105 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39621 Floating point exception in SAS program using hash table B25105
42684 Write Access Violation in tkeaa.dll B25105
42783 "Termination due to floating point exception..", "invalid operation.." errors occur when parsing textual data B25105
Released: May 04, 2011     Documentation: B25105wn.html       Download: B25105wn.exe  
Top ^

B25106 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39517 "Read Access Violation" or "Segmentation Violation" errors might be generated when creating ODS RTF output B25008
12601 ODS PRINTER generates "out of memory" errors B25062
38109 Justification, font, color, and height specifications do not replay to non-Listing ODS destinations when using PROC DOCUMENT B25062
40140 URLs generated on the mainframe when using the ODS HTML or the ODS TAGSETS.MVSHTML destination are incorrect in SASŪ 9.2 B25062
41024 Row headings might overwrite in PROC TABULATE output with ODS PRINTER (PCL/PDF/PS) destinations B25062
41445 Memory issues might occur when more than 19 DEFINE statements contain style options in PROC REPORT B25062
42238 Reports generated with SASŪ Enterprise Guide or the SASŪ Add-in for Microsoft Office with DBCS data might contain spaces in labels or cell values B25106
NOTE: If you install this hot fix, you must also install hot fixes B25260 and B25107 for Base SAS 9.21_M3.
Released: April 01, 2011     Documentation: B25106wn.html       Download: B25106wn.exe  
Top ^

B25107 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42238 Reports generated with SASŪ Enterprise Guide or the SASŪ Add-in for Microsoft Office with DBCS data might contain spaces in labels or cell values B25107
NOTE: If you install this hot fix, you must also install hot fixes B25260 and B25106for Base SAS 9.21_M3.
Released: April 01, 2011     Documentation: B25107wn.html       Download: B25107wn.exe  
Top ^

B25109 was replaced by B25218

B25111 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40494 ALERT - A SAS/SHAREŪ server fails or does not respond when it is run as a Microsoft Windows service B25041
41738 Sporadic abends of the SASŪ Metadata Server occur during start-up B25076
41921 ERROR: ORACLE connection error: ORA-01017: invalid username/password; logon denied. B25076
Released: April 28, 2011     Documentation: B25111wn.html       Download: B25111wn.exe  
Top ^

B25112 was replaced by B25260

B25113 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42806 Reading XML files that contain elements with long values might generate "segmentation violation" errors B25113
42807 Data elements might be replaced rather than concatenated when using the XML LIBNAME engine B25113
Released: March 30, 2011     Documentation: B25113wn.html       Download: B25113wn.exe  
Top ^

B25114 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42802 "ERROR: Read Access Violation In Task [ DISPLAY ]" could be received when refreshing the Organization Chart object in a SAS/AFŪ application B25114
Released: April 14, 2011     Documentation: B25114wn.html       Download: B25114wn.exe  
Top ^

B25115 was replaced by B25256

B25117 was replaced by B25219

B25118 was replaced by B25242

B25119 was replaced by B25225

B25120 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42626 SASŪ program files are overwritten with empty files B25120
Released: May 05, 2011     Documentation: B25120wn.html       Download: B25120wn.exe  
Top ^

B25121 was replaced by B25242

B25122 was replaced by B25239

B25123 was replaced by B25250

B25124 was replaced by B25218

B25127 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
43064 TRANWRD function can crash DBCS SAS when translating same variable to itself B25127
Released: May 09, 2011     Documentation: B25127wn.html       Download: B25127wn.exe  
Top ^

B25128 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
33451 An error occurs when you run a DB2 stored procedure that has a question mark for a parameter value in SAS/ACCESSŪ Interface to DB2 B25128
NOTE: If you install this hot fix and have SAS/Access Interface to DB2, you must also install hot fix B94010 for SAS/Access Interface to DB2.
Released: June 17, 2011     Documentation: B25128wn.html       Download: B25128wn.exe  
Top ^

B25129 was replaced by B25218

B25130 was replaced by B25242

B25131 was replaced by B25261

B25132 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40494 ALERT - A SAS/SHAREŪ server fails or does not respond when it is run as a Microsoft Windows service B25132
Released: July 01, 2011     Documentation: B25132wn.html       Download: B25132wn.exe  
Top ^

B25133 was replaced by B25218

B25135 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
43541 ALERT - The SASŪ 9.2 Stored Process Server becomes unresponsive in some conditions B25135
NOTE: SAS Integration Technologies customers who use the SAS Stored Process Server are required to install this fix for the issue described in SN-43541
Released: June 22, 2011     Documentation: B25135wn.html       Download: B25135wn.exe  
Top ^

B25136 was replaced by B25259

B25137 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
43337 B8601DT, B8601DA, B8601TM, and B8601DZ informats produce incorrect results B25137
Released: June 23, 2011     Documentation: B25137wn.html       Download: B25137wn.exe  
Top ^

B25138 was replaced by B25260

B25140 was replaced by B25242

B25142 was replaced by B25242

B25145 was replaced by B25218

B25147 was replaced by B25272

B25148 was replaced by B25218

B25149 was replaced by B25260

B25151 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
43686 The last text character in the SAS/AFŪ preview buffer might be truncated B25151
Released: October 18, 2011     Documentation: B25151wn.html       Download: B25151wn.exe  
Top ^

B25152 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41574 Double-byte character sets (DBCS) might not display properly in the ARM log B25082
43854 ARM4 "Segmentation Violation" error B25152
Released: August 12, 2011     Documentation: B25152wn.html       Download: B25152wn.exe  
IMPORTANT: If you install this hot fix, you must install Base SAS hot fix B25218.
Top ^

B25153 was replaced by B25181

B25154 was replaced by B25210

B25155 was replaced by B25259

B25158 was replaced by B25260

B25159 was replaced by B25250

B25161 was replaced by B25218

B25163 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45705 ALERT - Optimizer might "fail to respond" because of floating point error B25163
Released: October 11, 2011     Documentation: B25163wn.html       Download: B25163wn.exe  
Top ^

B25165 was replaced by B25218

B25166 was replaced by B25260

B25167 was replaced by B25218

B25168 was replaced by B25259

B25169 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
44714 Large utility file might unnecessarily be generated by SASŪ OLAP Server B25169
Released: November 04, 2011     Documentation: B25169wn.html       Download: B25169wn.exe  
IMPORTANT: You must also install hot fixes B25259 to fully implement the fixes for the issues addressed in this hot fix.
Top ^

B25170 was replaced by B25260

B25172 was replaced by B25239

B25174 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45200 The FDSTART option of the ARG statement might generate an incorrect argument list and thus cause errors B25174
NOTE: Customers running on z/OS must install hot fix B25214.
Released: February 02, 2012     Documentation: B25174wn.html       Download: B25174wn.exe  
Top ^

B25175 was replaced by B25210

B25176 was replaced by B25261

B25177 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45291 Performing a drag-and-drop operation within a SAS/AFŪ Version 6 Organizational Chart object might cause a read-access violation B25177
Released: February 22, 2012     Documentation: B25177wn.html       Download: B25177wn.exe  
Top ^

B25178 was replaced by B25218

B25179 was replaced by B25250

B25180 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
43399 Scalable vector graphics (SVG) files with data tips might cause 64-bit Microsoft Internet Explorer 9 to terminate abnormally B25180
Released: February 03, 2012     Documentation: B25180wn.html       Download: B25180wn.exe  
Top ^

B25181 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41183 Graphic Text Control in SAS/AFŪ software might not correctly display some characters B25059
43973 SAS/AFŪ Version 6 Critical Success Factor object is unreadable in SASŪ 9.2 B25153
45484 The SAS/AFŪ Graphics Text Control issue documented in SAS Note 41183 and fixed with Hot Fix B23059 is no longer resolved after applying Hot Fix B25153 B25181
Released: January 30, 2012     Documentation: B25181wn.html       Download: B25181wn.exe  
Top ^

B25183 was replaced by B25260

B25184 was replaced by B25242

B25185 was replaced by B25234

B25186 was replaced by B25222

B25187 was replaced by B25213

B25188 was replaced by B25218

B25190 was replaced by B25256

B25192 was replaced by B25259

B25194 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45501 Information maps with incorrectly truncated data item names cannot be opened in SASŪ Enterprise GuideŪ and the SASŪ Add-In for Microsoft Office B25194
Released: April 11, 2012     Documentation: B25194wn.html       Download: B25194wn.exe  
Top ^

B25195 was replaced by B25219

B25198 was replaced by B25256

B25199 was replaced by B25218

B25200 was replaced by B25239

B25201 was replaced by B25218

B25203 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45362 Intermittent errors reported in client session running a DISPLAY LIBRARY _ALL_ statement to a SAS/SHAREŪ Server B25203
Released: May 01, 2012     Documentation: B25203wn.html       Download: B25203wn.exe  
Top ^

B25204 was replaced by B25254

B25205 was replaced by B25250

B25206 was replaced by B25218

B25207 was replaced by B25259

B25208 was replaced by B25260

B25209 was replaced by B25239

B25210 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42629 Authentication error might appear when opening an information map in SASŪ Enterprise GuideŪ or the SASŪ Add-In for Microsoft Office B25099
44122 Performance degradation can occur when opening information maps in SASŪ Enterprise GuideŪ and the SASŪ Add-In for Microsoft Office B25154
45152 SASŪ Information Maps engine might incorrectly acquire a WRITE lock on SASŪ libraries in z/OS B25175
45153 SASŪ Enterprise GuideŪ and the SASŪ Add-In for Microsoft Office do not support general prefilters that are prompted B25175
46590 An internal error might occur when opening an information map in SASŪ Enterprise GuideŪ and the SASŪ Add-In for Microsoft Office B25210
Released: June 04, 2012     Documentation: B25210wn.html       Download: B25210wn.exe  
Top ^

B25211 was replaced by B25219

B25212 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
46612 Incorrect summed value for a data set variable might appear in PROC REPORT Listing output B25212
Released: June 26, 2012     Documentation: B25212wn.html       Download: B25212wn.exe  
Top ^

B25213 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45960 The SAS/CONNECTŪ job spawner does not release file handles B25187
46889 The SAS/CONNECTŪ PC Spawner program fails with the error "Thread pthread has been terminated due to an unhandled exception" B25213
Released: July 02, 2012     Documentation: B25213wn.html       Download: B25213wn.exe  
Top ^

B25215 was replaced by B25259

B25217 was replaced by B25240

B25218 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
41013 Errors might occur when you use the SASTRACE= system option with the SAS/ACCESSŪ engines B25046
37059 ERROR: "Read access violation in task [ DATASTEP ]" might occur when running SASŪ 9.2 on Microsoft Windows x64 and 64-bit Itanium-based systems B25049
41115 Loading a large SAS data file into memory can cause macro slowdown B25078
41574 Double-byte character sets (DBCS) might not display properly in the ARM log B25078
42240 The LIBNAME statement's FILELOCKWAIT= option might not check for a lock in all cases B25078
42376 An error occurs when reading a filename that includes an asterisk (*) with the Japanese edition of SASŪ 9.2 in a Windows operating environment B25092
42857 Poor performance when reading non-local files with SASŪ 9.2 on OpenVMS on HP Integrity B25109
43943 SASŪ Scalable Performance Data ServerŪ on Windows might experience problems with performance or appear unresponsive B25145
44472 Overwriting a SASŪ data set in a UNIX operating environment removes any existing ACL B25165
44584 SASŪ Enterprise GuideŪ does not import UTF-16 files correctly using a UTF-8 SASŪ server B25167
39615 ALERT - Input/output performance in SASŪ is degraded due to excessive memory usage on Windows B25188
45522 IGNOREDOSEOF option not honored when specified on the FILENAME statement B25188
45632 Queries against the SASŪ OLAP Server on Microsoft Windows might use excessive memory due to a Windows cache manager issue B25188
46251 Directories cannot be created under the Files folder in SASŪ Enterprise GuideŪ B25206
44257 A segmentation violation might occur and your server might not function when you run a SASŪ Stored Process that accesses a database B25218
Released: August 17, 2012     Documentation: B25218wn.html       Download: B25218wn.exe  
Top ^

B25219 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39997 A database error can occur when you submit an SQL query with a LIBNAME statement that uses the MULTI_DATASRC_OPT=IN_CLAUSE option B25028
41745 Accessing DB2 can result in System abend 0C4 in module SASIODB2 B25066
41748 Using the LIBNAME option MULTI_DATASRC_OPT=IN_CLAUSE can result in an error B25066
43275 A CLI error occurs when you access DB2 via SAS/ACCESSŪ 9.2 Interface to ODBC and PROC SQL implicit pass-through processing B25117
45162 ALERT - Slow performance and incorrect results might occur if you use DBCREATE_TABLE_OPTS to create a primary index for a Teradata table B25195
45375 Using the DBSASTYPE data set option on a z/OS system might result in an error B25211
46851 Errors occur when you perform tasks that require a reread of a DB2 table B25219
47898 The CREATE TABLE command spawns multiple connections when you use SAS/ACCESSŪ Interface to Teradata with UTILCONN_TRANSIENT=YES in a LIBNAME statement B25219
NOTE: If you install this hot fix, you must also install Base SAS 9.21_M3 hot fix B25226.
Customers running SAS/ACCESS Interface to DB2 9.21_M2 must also install hot fix B94020.
Customers running SAS/ACCESS Interface to Teradata 9.21_M2 must also install hot fix C71007.
Customers running SAS/ACCESS Interface to Teradata 9.21_M1 on Windows for x64 must also install hot fix D35006.
Customers running SAS/ACCESS Interface to Oracle 9.21_M2 must also install hot fix C36005.
Released: November 05, 2012     Documentation: B25219wn.html       Download: B25219wn.exe  
Top ^

B25220 was replaced by B25250

B25222 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45321 Exception and disk read errors occur when you import JMPŪ 9 files into SASŪ 9.3 B25186
47162 PROC EXPORT produces JMPŪ data tables having Version 3 file format B25222
Released: August 24, 2012     Documentation: B25222wn.html       Download: B25222wn.exe  
Top ^

B25225 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42652 Jobs that you submit to a grid environment might fail if they are controlled by the Platform Enterprise Grid Orchestrator (EGO) B25094
43170 The connection might fail when you submit to a grid environment with a multi-home grid control machine with Platform LSF 7.06 on the grid nodes B25119
43418 SASŪ Workspace Servers might not launch when you use the SASŪ grid load-balancing algorithm to make the server connections B25119
43577 Large numbers of simultaneous grid processes might stop responding B25119
47397 A segmentation violation and other errors might occur when your environment is under a heavy load and when resources are limited B25225
Released: October 02, 2012     Documentation: B25225wn.html       Download: B25225wn.exe  
Top ^

B25226 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39125 An SQLPLAN error might occur when you use a new column variable in a correlated subquery B25021
39129 Formatting a newly created, missing numeric variable might result in a "Format not found" error B25021
39304 SQL views of DBMS tables may not return aliased column names B25021
39984 An SQL procedure view does not return any rows when it is used in DATA step or a PRINT procedure B25021
40714 SQL procedure queries might take longer to run in SASŪ 9.2 TS2M2 and TS2M3 B25021
41875 SAS/ACCESSŪ Interface to DB2 might produce incorrect results when left joining two or more DB2 tables B25053
41619 Using PROC FORMAT in conjunction with PROC SQL to access a database gives different results between SASŪ 9.1.3 and SASŪ 9.2 B25060
41785 Read Access Violation errors occur when creating a long macro variable with the PROC SQL / INTO: macro interface B25060
42129 PROC SQL join operations result in "Floating Point Zero Divide" errors when the join columns are character and are extremely large B25060
48733 PROC SQL joins might result in errors if the join columns are character data type and the column lengths are too large for the current index page size B25060
34687 ALERT - Incorrect results might occur if you use the PUT() function in a WHERE clause to convert a DB2 timestamp to a character value B25083
38759 An error can occur when you run a query against a DBMS and the query contains a column that is renamed and that is then used in a GROUP BY clause B25083
42093 Using the PROC SQL BTRIM() function causes insufficient memory errors B25083
43970 Errors occur when you use input() or put() in a JOIN operation with a database table in a remote library B25083
44688 An INPUT() function used in PROC SQL might return incorrect results B25083
42425 SQLPLAN error might occur when creating a new variable based on another new variable B25116
43021 The SASŪ System might not consider the DBKEY= data set option when you join a SAS data set and a DBMS table B25116
43262 Queries that reference tables in libraries that are assigned using the META libname engine might perform poorly B25134
46712 Option for debugging META Libname Engine libraries B25134
42737 ALERT - Incorrect results occur in implicit pass-through when you use CALCULATED keyword on GROUP BY statement B25157
43787 Performance is adversely affected by SQL queries that use unique indexes through SAS/SHAREŪ software B25157
44069 Performance might be affected if your query joins multiple tables or views in which variables are being renamed B25157
44190 Unicode server performance is degraded when character literals in a WHERE clause are not passed to a database correctly B25157
45162 ALERT - Slow performance and incorrect results might occur if you use DBCREATE_TABLE_OPTS to create a primary index for a Teradata table B25196
45689 The SASŪ Stored Process Server might stop functioning properly if you cancel a request that is running PROC SQL code B25202
46830 ALERT - Specifying a LENGTH= modifier in an SQL procedure might result in a data integrity issue B25216
46832 ALERT - Incorrect results might occur when processing an SQL procedure query B25216
47967 "SPDS_ERROR: Column XXXXX could not be found in the table identified with the correlation name YYYYY" when running PROC SQL B25226
NOTE: Customers running on Solaris (64-bit) or AIX (64-bit) must install hot fix B25255 instead.
If you install this hot fix, you must also install Base SAS 9.21_M3 hot fixes B25250, B25260, and B25219.
Customers running SAS/ACCESS Interface to Teradata 9.21_M2 must also install hot fix C71007.
Customers running SAS/ACCESS Interface to Teradata 9.21_M1 on Windows for x64 must also install hot fix D35006.
Customers running SAS/ACCESS Interface to Oracle 9.21_M2 must also install hot fix C36005.
Released: September 26, 2012     Documentation: B25226wn.html D       Download: B25226wn.exe  
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.
Top ^

B25227 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39839 FILENAME FTP, URL and SOCKET access methods may fail to function correctly in some circumstances B25004
40538 Web addresses that contain a colon can cause the URL filename engine to fail with an error of "Hostname host not found" B25067
Released: September 28, 2012     Documentation: B25227wn.html       Download: B25227wn.exe  
Top ^

B25228 was replaced by B25259

B25231 was replaced by B25239

B25232 was replaced by B25242

B25233 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
48238 The error "Unable to contact the LDAP server" occurs when you use the LDAPS_OPEN CALL routine B25233
Released: November 09, 2012     Documentation: B25233wn.html       Download: B25233wn.exe  
Top ^

B25234 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
45160 The message: NOTE: Invalid argument to function FINANCE at line nnn column x. might occur when using the FINANCE function to calculate the XIRR B25185
48473 More robust algorithm implemented for properly determining internal rate of return when multiple solutions exist B25234
Released: November 26, 2012     Documentation: B25234wn.html       Download: B25234wn.exe  
Top ^

B25235 was replaced by B25259

B25239 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40061 An error occurs when you set the font option to 10 point Courier in SASŪ 9.2 (TS2M0) that uses a Thai_Thailand locale B25050
41621 Selecting "Save as HTML" does not save the data set in the redirected folder and SASŪ might terminate unexpectedly B25050
36548 When you maximize the Properties dialog box for a SASŪ data set, only 17 columns of the data set display and tabs might not be visible B25081
37700 Part of the variable listing of a data set appears to be blank when you view the data set in SAS Explorer B25081
42506 Text color for Microsoft Windows host controls might not be honored in a SAS/AFŪ Frame B25101
42729 SASŪ 9.2 overlays the Windows Forms API when you invoke SAS as an OLE automation server from a Microsoft Visual Basic application B25101
43112 The SASŪ system might become unresponsive or close unexpectedly when converting SASŪ6 data sets to SASŪ9 data sets B25122
44994 Using the Find dialog box to search in the SAS Log window might cause SASŪ 9.2 and SASŪ 9.3 to stop responding B25172
45003 A "generic critical error" might occur when you are paging up or down in or clearing the Output window in SASŪ 9.3 B25172
46076 Problems occur when you submit SASŪ code to an OLE Automation Server when the code contains embedded CRLF (newline) characters B25200
37304 SAS/AFŪ TextPad control might return incorrect information in a DBCS environment B25209
43603 Your SASŪ System fails to start on the Windows 7 operating system B25231
48694 The Xerox Phaser printer might prevent your SASŪ System from starting B25231
48901 The CheckBox control in SAS/AFŪ software might not honor the labelColor attribute B25239
Released: January 22, 2013     Documentation: B25239wn.html       Download: B25239wn.exe  
Top ^

B25240 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
46844 Client connections to the SASŪ Stored Process Server may fail when there is a delay starting the listen port. B25217
48314 A SASŪ Stored Process connection to a load-balanced SASŪ OLAP server might randomly fail under heavy load conditions B25217
49441 The SASŪ Workspace Server for local access is not enabled appropriately in some situations in SAS 9.2Ū and SAS 9.3Ū B25240
NOTE: If you install this hot fix and need the fix documented in SAS Note 48314, you must also install hot fix B25242.
Released: May 14, 2013     Documentation: B25240wn.html       Download: B25240wn.exe  
Top ^

B25241 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
40136 PROC TABULATE might give incorrect frequency statistics when only the N statistic is requested and memory is constrained B25013
40733 The SUMMARY, MEANS, TABULATE, and REPORT procedures might display an error message when accessing data using a SAS/ACCESS library engine B25035
41643 PROC SURVEYMEANS may terminate with the message: "NOTE: The SAS System stopped processing this step because of errors" B25064
48956 Using the PRELOADFMT option in a summary procedure and the OTHER= keyword in PROC FORMAT might generate error messages B25241
Released: March 20, 2013     Documentation: B25241wn.html       Download: B25241wn.exe  
Top ^

B25242 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
38906 The SASŪ metadata engine LIBNAME statement fails to interpret access password specification for the Remote Engine Library server B25020
40125 A slow response might occur when you connect to a SAS application server from client applications B25020
40366 ALERT - The error "Libname _PMTA01_ is not assigned" occurs when you try to update metadata for a work table B25020
39371 SASŪ Stored Process Server might hang during shut down if the SAS Workspace Server is being monitored B25031
40920 You are denied access to the SAS Workspace Server after you use SASŪ Enterprise GuideŪ to connect to the SASŪ Metadata Server B25039
39768 Existing client connections to SAS Workspace Servers are closed when the SAS Object Spawner is stopped or refreshed. B25054
41542 ALERT - SAS Object Spawner may crash when shutting down a SAS Pooled Workspace Server. B25054
41921 ERROR: ORACLE connection error: ORA-01017: invalid username/password; logon denied. B25077
42178 SAS Workspace server connections may fail when the SASŪ Grid Manager load balancing algorithm is used. B25118
42748 A validation failure occurs for a SASŪ Workspace Server in the SASŪ 9.2 environment B25118
43110 SASŪ OLAP Server might stop responding when the number of connected clients is high B25121
43204 The TIMEOUTSECONDS parameter might cause the SASŪ OLAP Server to stop responding B25130
43690 Library allocation messages are incorrectly reported at the WARN level instead of INFO B25140
43570 If one of the peers in a load balanced cluster of 3 or more peers is refreshed or restarted it causes load balancing to behave incorrectly. B25142
45627 Improved functionality to detect and stop orphaned SASŪ Workspace Server processes B25184
45661 Load balanced SASŪ OLAP Servers may abend and hang on shutdown B25184
48314 A SASŪ Stored Process connection to a load-balanced SASŪ OLAP server might randomly fail under heavy load conditions B25232
49795 The SASŪ pooled workspace server recycle activation limit is broken after applying Hot Fix B25086 B25242
NOTE: If you install this hot fix and need the fix documented in SAS Note 41921, you must also install Base SAS hot fix B25111.
NOTE: If you install this hot fix and need the fix documented in SAS Note 43204, you must also install hot fix B25171 (z/OS only).
NOTE: If you install this hot fix and need the fix documented in SAS Note 40125, you must also install Base SAS hot fix B25250.
NOTE: If you install this hot fix and need the fix documented in SAS Note 39768, you must also install hot fix B25260.
NOTE: If you install this hot fix and need the fix documented in SAS Note 48314, you must also install hot fix B25240.
Released: May 08, 2013     Documentation: B25242wn.html       Download: B25242wn.exe  
Top ^

B25243 was replaced by B25249

B25244 was replaced by B25261

B25245 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
50025 Transporting an FSVIEW formula corrupts the catalog B25245
NOTE: Hot fix I22036 must be applied to your SAS 9.3 TS1M2 installation prior to importing the transport catalog.
Released: August 15, 2013     Documentation: B25245wn.html       Download: B25245wn.exe  
Top ^

B25246 was replaced by B25256

B25247 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
50948 SAS/CONNECTŪ software returns an incorrect observation number when you access a DATA step view from a Remote Library Services LIBNAME statement B25247
Released: September 06, 2013     Documentation: B25247wn.html       Download: B25247wn.exe  
Top ^

B25248 was replaced by B25260

B25249 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39614 "ERROR: No email addresses specified" when sending email from SASŪ using SMTP B25003
40143 E-mail output from SASŪ 9.2 fails when attachments have an LRECL value greater than 1000 B25027
40178 The sender header field is truncated when you use SASŪ software for SMTP e-mail B25027
40978 The subject lines for e-mails sent from SASŪ might get truncated in some e-mail clients B25047
41926 ERROR: "Email: The connection was reset by a peer" B25088
41550 SMTP email access method randomly fails with "ERROR: Email: The specified address is not available" or "Email server did not respond" B25243
50070 Email messages sent by a SASŪ program fail with "ERROR: Invalid number" B25249
Released: June 17, 2013     Documentation: B25249wn.html       Download: B25249wn.exe  
Top ^

B25250 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
38906 The SASŪ metadata engine LIBNAME statement fails to interpret access password specification for the Remote Engine Library server B25018
40125 A slow response might occur when you connect to a SAS application server from client applications B25018
40231 "ERROR: Libname _PMTA01_ is not assigned" occurs when running the METALIB procedure B25018
40366 ALERT - The error "Libname _PMTA01_ is not assigned" occurs when you try to update metadata for a work table B25018
39550 A Read access violation occurs when you use the METALIB procedure to import or register database tables into the SASŪ Metadata Repository B25056
38707 An error occurs when you add the DBSASTYPE= option to a database table in SASŪ Management Console and you run a query that uses the metadata engine B25123
43224 An error message appears in your SASŪ log if you use the METALIB procedure to register or update a view that is defined in a Sybase database B25123
43262 Queries that reference tables in libraries that are assigned using the META libname engine might perform poorly B25123
46712 Option for debugging META Libname Engine libraries B25123
44153 Libraries referenced in PROC METALIB or a META LIBNAME statement look for DBMS credentials in metadata even when Authentication Type is "NONE" B25159
44180 "ERROR: Read Access Violation In Task [SQL]" might occur when using the META engine on a LIBNAME statement B25159
41093 An error occurs and you cannot access an Oracle table when you use a schema name or a user ID that contains a dollar sign ($) B25205
46153 The META libname engine ignores the Default Login associated with a relational database library B25205
46405 META libname engine no longer reports column length inconsistencies when it should B25205
46408 Access to third party database tables via the META libname engine fails when the userid contains special characters B25205
47017 The META LIBNAME engine permits a user to add rows to a table even when the user has been denied CREATE permission on the table B25220
43097 The error "No available engine session manager slots" occurs when you access Teradata tables with the META LIBNAME engine B25250
44120 Assigning DBMS libraries might fail in SASŪ Enterprise GuideŪ B25250
49607 The maximum number of database connections is exceeded when you access databases that are registered in metadata B25250
NOTE: If you install this hot fix, you must also install Base SAS 9.21_M3 hot fixes B25242 and B25226.
Released: August 07, 2013     Documentation: B25250wn.html       Download: B25250wn.exe  
Top ^

B25251 was replaced by B25256

B25252 was replaced by B25259

B25253 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
50673 Searching in SASŪ Web Report Studio from the SAS Folders root folder might cause the SASŪ Metadata Server to become unresponsive B25253
Released: August 12, 2013     Documentation: B25253wn.html       Download: B25253wn.exe  
Top ^

B25254 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
42496 Computed columns defined to an MDDB do not display without a SAS/AFŪ license B25098
46318 "ERROR: Invalid Operation. ERROR: Termination due to Floating Point Exception" B25204
50730 "WARNING: FMPFMT: outbuf too small" might appear unexpectedly when you run SAS/AFŪ applications that have been migrated to SASŪ 9.2 or later B25254
Released: August 15, 2013     Documentation: B25254wn.html       Download: B25254wn.exe  
Top ^

B25256 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39833 The SASŪ Metadata Server might terminate abnormally B25001
41201 The SASŪ Metadata Server might report that the members of the SAS Metadata Server fixed roles no longer have the associated privileges B25051
42284 The EXPORT Wizard may fail with: [Fatal Error] :154:345: An invalid XML character B25075
42768 Long member-level permission conditions for SASŪ OLAP cubes might cause the SASŪ Metadata Server to fail B25115
43114 An error might occur when you use SASŪ Management Console to change the association of one metadata object to another B25115
45686 New SASŪ Metadata Server logging functionality is available with SASŪ 9.2 TS2M3 hot fix B25190
46160 Check In fails with an "Error checking in metadata.." error in SASŪ Data Integration Studio B25198
49740 ALERT - The SASŪ Metadata Server might become unresponsive because of a memory overlay B25246
50290 An error occurs intermittently when you try to update metadata objects from SASŪ client applications B25251
51079 An existing target table's column informat value might not be overwritten when you import a table with a column informat value that is set to (None) B25256
Released: September 23, 2013     Documentation: B25256wn.html       Download: B25256wn.exe  
Top ^

B25258 was replaced by B25260

B25259 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39480 Queries that contain the PROPERTIES function might return a formula error on some operating systems B25002
39955 ALERT - VisualTotals and other calculated members might return unexpected values in OLAP-based reporting B25006
40077 MDX to-date functions might return incorrect values when used with other calculated members B25006
40091 AGGREGATE_TOTAL function in the SASŪ OLAP Server can restrict access to members with unexpected results B25032
40549 Optimization code might cause additional queries when accessing aggregation data B25032
40550 VisualTotals with MDX functions using the .CURRENTMEMBER function can return unexpected results B25032
40551 Performance issues might occur when using flattened results from MDX queries after appying hot fix B25006 B25032
41005 Use of the NONEMPTYCROSSJOIN function and multiple-selection filters might result in missing rows B25063
41078 Queries to SAS OLAP cubes that are built using ROLAP or external aggregations might perform slowly B25063
41175 SECURITY_SUBSET not honored for totals after import of cube metadata B25063
41234 The NonEmptyCrossjoin function might return incorrect results after applying hot fix B25032 B25063
41637 Large memory usage might occur on Solaris machines when an invalid dimension name is used in the VisualTotals_Behavior property B25063
41642 Multiple member filters on the hidden dimension or slicer axis might return incorrect results when totals are displayed on both rows and columns B25063
40911 Do not use reserved words in dimension names when working with external aggregations B25103
41577 Queries might perform slowly if ties are included when using TOPCOUNT B25103
41939 Columns for categorical data that contain only missing values might be removed from the output of a flattened OLAP query B25103
42160 Variables with more than 16777215 unique values cause a floating point exception in PROC OLAP B25103
42406 SASŪ session might stop responding when using the DISABLE CUBES statement B25136
42827 Drill-through to detail data for an OLAP cube might fail if UTF-8 encoding is used and member values contain non-English characters B25136
43542 "The server encountered an error accessing a source data table" received when macro references exist in a member caption for a ROLAP cube B25136
43554 PROC OLAPOPERATE and other administrative calls to the SASŪ OLAP Server could cause the OLAP Server to fail B25136
43556 Options NECJPERCENTTOTAL and NECJWHEREMAX have been added to the SASŪ OLAP Server to help disable NONEMPTY CROSSJOIN optimization for dense data B25136
43557 SQL range optimization is bypassed for data ordered by formatted values for a SASŪ OLAP cube B25136
44260 Continuous DISABLE CUBE operations might cause the SASŪ OLAP Server to stop responding B25155
44267 MDX ORDER function might generate a large number of subqueries B25155
44277 Final subquery to satisfy a query against a SASŪ OLAP cube might be unnecessary and impact performance B25155
44715 Performance enhancement enables the underlying data source to calculate TOPCOUNT and BOTTOMCOUNT for an OLAP query B25168
44742 General performance improvements for SASŪ OLAP cubes are included with Hot Fix B25168 for the third maintenance release for SAS 9.2 (TS2M3) B25168
44751 Poor performance when drilling to detail data from a SASŪ OLAP cube B25168
42667 Empty results from a non empty crossjoin query might result in slow performance from the SASŪ OLAP Server B25192
45266 Visual totals might be incorrect when single member on slicer and two hierarchies from the same dimension are on different axes B25192
45491 "Error: Insufficient memory" might appear when very large sets are crossjoined and the maximum number of members is exceeded B25192
45608 "Read Access Violation" using DATAPATH or INDEXPATH options creating SPDE library B25192
45633 Read Access Violation might be generated for PROC OLAP when there are many levels in a dimension with multiple hierarchies B25192
46447 The ORDER function might return incorrect results when the default measure is used in both the set and the numeric expression parameters B25207
46550 The SASŪ OLAP Server might stop responding after a client attempts to cancel a query that is running on the SAS OLAP Server B25207
46828 Infinite recursion error might occur when using both calculated members and measures in an OLAP cube B25215
47925 Using the TOPCOUNT function might produce errors when it is used with a set containing NUNIQUE measures B25228
47941 OLAP queries that use the NONEMPTYCROSSJOIN function, calculated members, and calculated measures might produce incorrect results B25228
47974 A data integrity issue might occur if the NWAY is not compacted when you build a SASŪ OLAP cube that uses a star schema B25228
48308 The SASŪ OLAP Server might stop responding if a nonstandard method is used to cancel the query B25228
48614 Intermittent access violation errors might occur when using SASŪ Web Report Studio to query an OLAP cube B25235
50352 The SASŪ OLAP Server might stop responding when you use PROC OLAPOPERATE DISABLE CUBE B25252
50220 A library assignment error might occur when you drill to detail records from a SASŪ OLAP cube B25259
Released: November 26, 2013     Documentation: B25259wn.html       Download: B25259wn.exe  
IMPORTANT: You must also install hot fixes B25169, B25261 and D28016 to fully implement the fixes for the issues addressed in this hot fix.
Top ^

B25260 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39807 Global macro variable values and scope may be set incorrectly when PROC RISK is within a macro B25007
40220 EFI, PROC IMPORT and IMPORT WIZARD read a quoted 4 digit number incorrectly B25007
40252 R interface in Proc IML does not work on 64-bit Windows Operating Systems B25012
40382 CALL SYMPUT may not update existing global macro variable B25023
40438 Extremely wide data sets created on a 64-bit operating system produce incorrect or missing values on 32-bit operating systems B25026
40521 SAS appears to hang in an endless loop if you use Cross Environment Data Access (CEDA) and select a large number of variables B25026
40449 ANYDTDTE doesn't read a period value properly B25034
40737 Calling user defined functions using %SYSFUNC can result in an error or termination of SAS B25036
41114 WHERE clauses that reference functions will execute slowly in SCL code B25058
41119 Multiple WHERE ALSO statements in the DATA Step returns incorrect results or errors B25058
39768 Existing client connections to SAS Workspace Servers are closed when the SAS Object Spawner is stopped or refreshed. B25086
41651 A segmentation violation might occur when performing a large number of asynchronous signons B25086
42252 ALERT - DATA step views are not accessible when you submit and pass them to a SAS grid from SASŪ Enterprise GuideŪ B25086
31887 Problems with macro variables created in an AUTOEXEC.SAS file when executing SASŪ on a workspace server B25112
42925 You cannot audit SASŪ library Open objects in the standard SAS logging facility B25112
43537 The last character of a double-byte character set variable is truncated when the variable length is 257 B25138
43671 A memory leak may occur in SASŪ Integration Technologies server processes. B25138
43967 Indexes on data sets can become corrupt when run against the same data multiple times B25149
44190 Unicode server performance is degraded when character literals in a WHERE clause are not passed to a database correctly B25158
39846 Errors occur in a Foundation SASŪ session when you try to connect with a SASŪ Integration Technologies Server B25166
44674 Referencing an autocall macro stored in a catalog causes a message window to appear upon exiting SAS B25170
45589 An index might be ignored in BY processing after importing the indexed data set from transport format from another operating system B25183
46164 &SYSSITE incorrectly returns site numbers with leading zeros B25208
48439 Global macro variables are incorrectly set within a workspace server B25208
49737 Catalog concatenation might result in locked catalogs B25248
51701 ALERT - When you run SASŪ Foundation, non-allocated memory might be overwritten B25260
NOTE: If you install this hot fix, you must also install hot fix B25226 for Base SAS 9.21_M3.
NOTE: SAS Integration Technologies customers must also install hot fix B25242 to fully implement the fix for the issue described in SN-39768.
NOTE: SAS Enterprise Guide customers must also install hot fix B99010 to fully implement the fix for the issue described in SN-42252.
Released: January 16, 2014     Documentation: B25260wn.html       Download: B25260wn.exe  
Top ^

B25261 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39408 SPDE data sets unexpectedly locked or not available B25044
43279 Unable to rename SPDE (Scalable Performance Data Engine) data sets B25131
44902 SPDE (Scalable Performance Date Engine ) LIBNAME statement can generate an HSSTER error or cause SAS to terminate B25176
49827 SASŪ Scalable Performance Data Engine might fail or might not respond during Read processing in which a WHERE clause is used. B25244
52286 Creating an index on an empty SASŪ Scalable Performance Data Engine data set fails in AIX operating environments B25261
Released: February 27, 2014     Documentation: B25261wn.html       Download: B25261wn.exe  
IMPORTANT: You must also install hot fixes B85005 to fully implement the fixes for the issues addressed in this hot fix.
Top ^

B25270 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
39088 An error occurs and the SAS Operating System Scheduler cannot create Visual Basic scripts when you try to schedule a flow to the scheduler B25005
57236 A daily flow scheduled via the Operating System Services Scheduler fails to run under the Schedule Manager plug-in in SASŪ Management Console B25270
Released: August 11, 2016     Documentation: B25270wn.html       Download: B25270wn.exe  
Top ^

B25272 for Windows
Base SAS 9.21_M3
Issue(s) Addressed:Introduced:
44121 Errors occur when you use the SASŪ Grid Manager Client Utility in UNIX operating environments B25147
58721 SASGSUB sign-on fails with "ERROR: Access denied" when you enter a password that contains more than eight characters B25272
Released: August 26, 2016     Documentation: B25272wn.html       Download: B25272wn.exe  
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.

Copyright © 2016 SAS Institute Inc. All Rights Reserved.