V11030 |
SAS Management Console 9.4_M3 |
Issue(s) Addressed: | Introduced: |
56560 | SAS® Content Server is vulnerable to an XML external entity exploitation (CVE-2015-1833) |
V11001 |
58206 | In SAS® Data Integration Studio and SAS® Management Console, the German translation of the message confirming object deletion is incorrect |
V11001 |
56414 | SAS® Web Report Studio list tables might display a user-defined format in the total row |
V11002 |
57131 | SAS® Data Integration Studio jobs that contain an SQL subquery lose subquery metadata after you run the Analyze and Repair Tool |
V11003 |
57799 | The WebDAV repository connection attempt fails with HTTP connection-manager errors |
V11004 |
58270 | Metadata support for SAS/ACCESS® Interface to Amazon Redshift |
V11004 |
56172 | Disabling a cube in SAS® OLAP Cube Studio or SAS® Data Integration Studio might fail if you are using a load-balanced SAS® OLAP Server |
V11005 |
58042 | When you import tables using SAS® Management Console, the physical names of the imported tables become corrupted |
V11005 |
58197 | When you click the Data Server tab in SAS® Management Console, an out-of-memory condition occurs and performance is affected |
V11005 |
58336 | Using SAS® Real-Time Decision Manager 6.5 with the SAS® Federation Server 4.2 causes gradual decline of throughput and increased response time |
V11005 |
58337 | When you are using SAS® Real-Time Decision Manager, duplicate warning or diagnostic messages might occur in SAS® Federation Server 4.2 logs |
V11005 |
58469 | When you import a SAS® Data Integration Studio job containing a Lookup transformation, "Error: Lookup has no target column mapping information" occurs |
V11006 |
58867 | TLSv1.2 is not supported by Java IOM clients |
V11006 |
59094 | Reimporting jobs in SAS® Management Console fails with the error "Scheduling of 'job-name' failed..." |
V11006 |
52971 | Results are incorrect when you use the operator EXACTLY MATCHES in the custom details of SAS® Marketing Automation |
V11007 |
58846 | You receive the error "Scheduling of job-name failed..." when you schedule flows using SAS® Management Console |
V11008 |
58366 | SAS® Management Console stops responding when you access Active Server Properties for metadata server details or to send a test alert message |
V11009 |
58773 | Queries in SAS® Workflow Services fail for users that belong to more than 1,000 groups |
V11010 |
58774 | SAS® Web Infrastructure Platform Unable to log on as a user with membership in over a 1,000 groups |
V11010 |
59188 | Updating an expired internal account password fails with the message "The password for this user ID has expired. Create a new password" |
V11010 |
60072 | Subflows are lost when reimporting the subflow with its parent flow in the same package |
V11010 |
60719 | Out-of-disk-space issues occur when temporary files are not removed from the \\WebAppServer\\SASServer_#\\temp directory |
V11010 |
59403 | "Error reading metadata: Insufficient memory" occurs when you rename a library in SAS® Data Integration Studio or in SAS® Management Console |
V11011 |
59569 | Some database management system library options are omitted from explicit SQL pass-through code in SAS® Data Integration Studio |
V11011 |
60351 | Internet HTTP requests for "tgt.keepal.ive" and "www.LazySecurityContext.com" originate from SAS® 9.4 Web Infrastructure Platform |
V11012 |
59700 | Flow contents are lost when more than one person edits the same flow concurrently in the SAS® Management Console Schedule Manager plug-in |
V11013 |
60073 | Scheduling many operating system scheduler jobs causes the operating system to use a large quantity of resources and affects performance |
V11013 |
57962 | The SAS® Data Integration Studio SCD Type 2 Loader transformation generates errors when loading data into an external DBMS |
V11014 |
60595 | Connections between work tables and database libraries are incorrectly removed when these objects are included in metadata import processing |
V11014 |
62666 | SAS® Content Server contains a cross-site request forgery (CSRF) vulnerability |
V11014 |
60275 | SAS® Enterprise Guide® might perform slowly when opening an information map that has millions of rows |
V11015 |
61010 | Incorrect values are stored for the common data model when it is used in a SAS® Customer Intelligence Studio campaign |
V11016 |
60545 | Values for the date-and-time range are displayed incorrectly in SAS® Customer Intelligence Studio |
V11017 |
62194 | The command for a job is not updated when you redeploy a job and select a new batch server in the Schedule Manager plug-in for SAS® Management Console |
V11018 |
63051 | A date prompt for a report incorrectly displays August instead of September when you use the Russian locale |
V11021 |
64181 | SAS® Visual Analytics fails to import data when running in Google Chrome 74 |
V11024 |
65077 | SAS® Enterprise Case Management does not report an error when you attempt to attach a file with a blocked file extension |
V11024 |
65078 | SAS® Enterprise Case Management does not respond properly when disallowed file uploads are blocked |
V11024 |
60622 | Redeploying a job using SAS® Management Console fails with the "UNKNOWN_ORIGINAL_SOURCE_FILE" error when the deployed job is defined by importing |
V11026 |
65746 | A metadata connection leak occurs when you save a SAS® Enterprise Guide® project on SAS® Content Server |
V11028 |
67057 | Multiple instances of the error "Unable to determine database vendor" are displayed in the catalina.out log during normal operation of the software |
V11029 |
67449 | A security vulnerability in IBM Platform Process Manager affects Platform Suite for SAS® |
V11030 |
NOTE: If you install this hot fix , you must also install
Y20008 for SAS Deployment Backup and Recovery Tool 9.41.
to fully implement the fix for the issue described in 56910.
If you install this hot fix , you must also install
B4P009 for SAS Add-in for Microsoft Office 7.15 and B4N009 for SAS Enterprise Guide 7.15
to fully implement the fix for the issue described in 65746.
|
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |