| J9K016 |
| SAS Workload Orchestrator and SAS Grid Manager for Platform 9.47 |
| Issue(s) Addressed: | Introduced: |
| 66711 | Grid-launched workspace servers fail when Kerberos authentication is used with SAS® Workload Orchestrator |
J9K001 |
| 67077 | Signing in to SAS® Grid Manager from SAS® Enterprise Guide® takes a longer time than expected |
J9K001 |
| 67379 | The maxStdOutLines parameter is added to the SAS® Workload Orchestrator web interface |
J9K001 |
| 68843 | The maxStdOutLines parameter does not have a default value for SAS® Workload Orchestrator |
J9K001 |
| 67800 * | The high availability feature is added to SAS® Job Flow Scheduler |
J9K002 |
| 69176 | The SGMG daemon in SAS® Workload Orchestrator returns a segmentation violation with the message "Exception occurred. Thread: SGMG Master Thread..." |
J9K003 |
| 69175 | The SAS® Workload Orchestrator daemon on the grid controller host might experience a memory leak |
J9K004 |
| 69663 | The message "TKM: Memory Error [CHECKOWNER]" occurs when you use SAS® Workload Orchestrator |
J9K005 |
| 69770 | Kerberos credentials might not be removed from the disk or memory in SAS® Workload Orchestrator grid clients |
J9K006 |
| 69771 | Kerberos connections to SAS® Workload Orchestrator from grid clients might fail to authenticate |
J9K006 |
| 69772 | SAS® Workload Orchestrator memory consumption might steadily increase |
J9K006 |
| 69966 | "An invalid compare order value was specified" occurs when using 'Compare Order' from the SAS® Workload Orchestrator web interface Configuration tab |
J9K007 |
| 70537 | ALERT - Jobs might remain in a starting or running state indefinitely when using SAS® Grid Manager (SAS® Workload Orchestrator) |
J9K008 |
| 70608 | Slow sign-ons to SAS® Grid Manager might result in the error “PROVIDER(SAS): Could not authenticate to the cluster” |
J9K009 |
| 70688 | The SAS ® Grid Manager Grid (sgmg) service might consume 100% CPU |
J9K010 |
| 70741 | The Host status in SAS ® Workload Orchestrator might enter an INACTIVE state unexpectedly |
J9K011 |
| 70810 | The object spawner stops responding in SAS® Grid Manager for Platform environments when you submit multiple workspace server requests simultaneously |
J9K012 |
| 70949 | Object spawners stop processing grid-launched workspace server requests in SAS® Grid Manager for Platform environments |
J9K013 |
| 71114 | SAS® Workload Orchestrator client applications fail with varying errors when using a SAS license file that expires in 2028 or later on Windows |
J9K014 |
| KB0041438 | Issues that are addressed in Hot Fix J9K015 for SAS® Workload Orchestrator |
J9K015 |
| KB0043041 | 403 Forbidden..." errors appear in the SAS Object Spawner log file when users try to connect to the grid environment |
J9K016 |
| * 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. This section includes a list of other hot fixes that must be applied. Please contact SAS Technical Support if you have questions. |
|
| 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