| J2L013 |
| SAS Middle Tier 9.4_M7 |
| Issue(s) Addressed: | Introduced: |
| 66922 | SAS® 9.4 Logon Manager contains third-party libraries that have known vulnerabilities |
J2L001 |
| 67031 | Middle-tier configuration fails with errors during the "Load Content/Upload Content, Web Infrastructure Platform Configuration" step |
J2L002 |
| 66540 | SAS® Management Console and SAS® Data Integration Studio might return the message "table failed to update" when you use the Update Metadata tool |
J2L003 |
| 67069 | The Number of Records field in the Basic Properties pane of SAS® Data Integration Studio might contain an incorrect value |
J2L003 |
| 67171 | A job that contains a Model Scoring transformation fails with the message "ERROR: Invalid hexadecimal constant string..." |
J2L003 |
| 67177 | Deployment of a stored process as a SAS® BI Web Service fails with the error "com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character..." |
J2L003 |
| 67188 | A "Compare Tables: java.lang.NullPointerException" error occurs when deploying a job that contains a Compare transformation using a hash lookup method |
J2L003 |
| 67800 * | The high availability feature is added to SAS® Job Flow Scheduler |
J2L004 |
| 67555 | SAS® Job Flow Scheduler is non-responsive and a null pointer exception occurs after scheduling a single flow |
J2L004 |
| 67742 | Performance degradation occurs when you open campaigns in SAS® Customer Intelligence Studio |
J2L005 |
| 68006 | The "Send Test Notification" action in SAS® Web Administration Console (in SAS® 9.4M7) fails for any template that is edited or modified |
J2L006 |
| 68162 | Preventing Cross-Site Request Forgery (CSRF) attacks for SAS® Comments Manager and other shared applications |
J2L006 |
| 67771 | SAS® LASR™ Analytic Server Loader ignores "Use runtime lookup for credentials for statements requiring credentials" in SAS® Data Integration Studio |
J2L007 |
| 68479 | The GemfireBasedTicketCache cache locator can fail with the error "ClassCastException" in a clustered SAS® 9.4 middle-tier environment |
J2L007 |
| 68521 | The export wizard in SAS® Data Integration Studio does not retain the expected column order in the composite index or composite primary key |
J2L007 |
| 68522 | SAS® Data Integration Studio 4.905 displays "Error writing metadata:Repository ABCDEFGH is not registered" when you add a new responsibility |
J2L007 |
| 68540 | SAS® Data Integration Studio jobs contain extraneous metadata content that might negatively impact metadata performance |
J2L007 |
| 68545 | The command-line batch deployment tool fails to include the Metadata Server and Port information in the job header comments |
J2L007 |
| 68546 | "...Multiple lengths were specified for the variable recreate by input data set(s). This may cause truncation..." occurs after you submit a job |
J2L007 |
| 68566 | A DeployJobs command with the REDEPLOY option creates a new job with the name of the original job, even though you entered a new Deployed Job Name |
J2L007 |
| 60769 | File events are not mapped correctly after importing a flow |
J2L010 |
| 68789 | SAS® Content Server contains a cross-site scripting vulnerability |
J2L010 |
| 68924 | SAS® Data Integration Studio jobs contain extraneous metadata content that might negatively impact metadata performance |
J2L010 |
| 68945 | The SAS® Stored Process Web Application contains a reflected cross-site scripting (XSS) vulnerability |
J2L011 |
| 69038 | "An error occurred when loading data" appears in the SAS® Analytical Data Set Builder Web Application |
J2L013 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
NOTE: The installation instructions for this hot fix contain a PRE-INSTALLATION section that must be reviewed before proceeding with the installation of this hot fix. Please contact SAS Technical Support if you have questions.
If you install this hot fix, you must also install hotfixes J7S004 and I9E010 to surface the fix documented in SAS Note 68924
|
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes