Problem Note 65359: Server launch might fail with "The Balance algorithm timed out before a server could be found" in SAS® Workload Orchestrator
 |  |  |  |  |
When an application server is configured for load balancing using the grid algorithm and the SAS Workload Orchestrator grid provider, the launch of the server might fail. In this scenario, the object spawner log contains the following error:
The Balance algorithm timed out before a server could be found.
To confirm that you are encountering this failure, set the object spawner's App.tk.tkegrid logger to the debug level and check for the following message:
getHostList: req resources=SASApp
This issue is caused by the object spawner submitting the application server context name as a required tag.
There are two possible workarounds:
- Set the application server to launch via grid.
- Add a tag that specifies your application server context name to your execution hosts in SAS Workload Orchestrator. For more information, see the Defining a New Host Type section in Grid Computing in SAS® 9.4, Fifth Edition.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS Workload Orchestrator | Microsoft® Windows® for x64 | 9.4 TS1M6 | |
| Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8 Enterprise x64 | 9.4 TS1M6 | |||
| Microsoft Windows 8 Pro 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8 Pro x64 | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Pro x64 | 9.4 TS1M6 | |||
| Microsoft Windows 10 | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 Datacenter | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 R2 Std | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 Std | 9.4 TS1M6 | |||
| Microsoft Windows Server 2016 | 9.4 TS1M6 | |||
| Microsoft Windows Server 2019 | 9.4 TS1M6 | |||
| Windows 7 Enterprise 32 bit | 9.4 TS1M6 | |||
| Windows 7 Enterprise x64 | 9.4 TS1M6 | |||
| Windows 7 Home Premium 32 bit | 9.4 TS1M6 | |||
| Windows 7 Home Premium x64 | 9.4 TS1M6 | |||
| Windows 7 Professional 32 bit | 9.4 TS1M6 | |||
| Windows 7 Professional x64 | 9.4 TS1M6 | |||
| Windows 7 Ultimate 32 bit | 9.4 TS1M6 | |||
| Windows 7 Ultimate x64 | 9.4 TS1M6 | |||
| 64-bit Enabled AIX | 9.4 TS1M6 | |||
| 64-bit Enabled Solaris | 9.4 TS1M6 | |||
| HP-UX IPF | 9.4 TS1M6 | |||
| Linux for x64 | 9.4 TS1M6 | |||
| Solaris for x64 | 9.4 TS1M6 | |||
A fix for this issue for Threaded Kernel IOM 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/E8G.html#65359
When an application server is configured for load balancing using the grid algorithm and the SAS Workload Orchestrator grid provider, the launch of the server might fail with an error. This issue is caused by the object spawner submitting the application server context name as a required tag.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2020-01-21 16:35:04 |
| Date Created: | 2020-01-15 10:48:55 |