| E5T019 |
| SAS Grid Manager Plug-ins for SAS Management Console 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63684 | Changing the status of a job returns the error "The job ID specified is not found" |
E5T001 |
| 63685 | Setting the "Maximum Jobs" value to 0 for a queue causes SAS® Job Flow Scheduler to stop responding |
E5T001 |
| 63686 | SAS® Job Flow Scheduler does not schedule jobs from queues with equal priority on a FIFO basis |
E5T001 |
| 63687 | A SAS® Grid Manager grid queue fails when it is preempted by multiple queues |
E5T001 |
| 63761 | SAS® Visual Analytics delivers more copies of distributed reports than expected |
E5T002 |
| 63894 | Rescheduling a flow on the Distributed In-Process Services Scheduling Server causes jobs to be run on both the old and new schedules |
E5T002 |
| 64842 | SAS® 9.4 software references Apache Struts libraries that contain known vulnerabilities |
E5T003 |
| 60622 | Redeploying a job using SAS® Management Console fails with the "UNKNOWN_ORIGINAL_SOURCE_FILE" error when the deployed job is defined by importing |
E5T006 |
| 64331 | SAS® Job Flow Scheduler does not support UNC paths properly on a Microsoft Windows system |
E5T006 |
| 65206 | A daily flow in SAS® Job Flow Scheduler does not run on Mondays, even when you select the "Every Weekday" option |
E5T006 |
| 61010 | Incorrect values are stored for the common data model when it is used in a SAS® Customer Intelligence Studio campaign |
E5T008 |
| 66134 | SAS® Management Console contains an XML External Entity (XXE) processing vulnerability |
E5T009 |
| 66307 | ALERT - You see a null pointer exception message in the Schedule Manager when you initially schedule a flow with Platform Suite for SAS® |
E5T010 |
| 68479 | The GemfireBasedTicketCache cache locator can fail with the error "ClassCastException" in a clustered SAS® 9.4 middle-tier environment |
E5T015 |
| 68546 | "...Multiple lengths were specified for the variable recreate by input data set(s). This may cause truncation..." occurs after you submit a job |
E5T017 |
|
| 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