Problem Note 64189: The OPTMODEL or OPTMILP procedures might lose communication with a CAS worker node and fail to complete the optimization
 |  |  |  |  |
If you specify the DECOMP option in the PROC OPTMILP statement or in the SOLVE WITH MILP statement in PROC OPTMODEL, communication with a CAS worker node might be lost. If this happens, the optimization does not complete and the following warning and error messages are issued in the CAS server log:
WARNING: Communication with machine <name> has been lost.
ERROR: The action cannot be retried because the session has no available workers.
ERROR: The operation was not performed because contact with at least one node was lost before the operation could complete.
tracktkt generates the following traceback on the worker nodes:
ERROR: The system has encountered an unhandled Exception.
: Please contact technical support and provide them
: with the following traceback and system dump information:
ABORT: SAS/TK is aborting
: Abort Log file [/cascache/castracktkt.3781]
: ---------------------------------------
: Time [mm/dd/yyy hh:mm:ss ]
: ---------------------------------------
: Thread Name [GenThread]
ERROR: The action cannot be retried because the session has no available workers.
ERROR: The operation was not performed because contact with at least one node was lost before the operation could complete.
tracktkt generates the following traceback on the worker nodes:
ERROR: The system has encountered an unhandled Exception.
: Please contact technical support and provide them
: with the following traceback and system dump information:
ABORT: SAS/TK is aborting
: Abort Log file [/cascache/castracktkt.3781]
: ---------------------------------------
: Time [mm/dd/yyy hh:mm:ss ]
: ---------------------------------------
: Thread Name [GenThread]
A possible workaround is to remove the DECOMP option and solve the problem directly as a mixed integer linear program (MILP).
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/OR | z/OS | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 |
| Microsoft® Windows® for x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Enterprise 32-bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Enterprise x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro 32-bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Pro 32-bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Pro x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 10 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 R2 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 for x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 Datacenter | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 R2 Std | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 Std | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Enterprise 32 bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Enterprise x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Home Premium 32 bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Home Premium x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Professional 32 bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Professional x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Ultimate 32 bit | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Ultimate x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| 64-bit Enabled AIX | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| 64-bit Enabled Solaris | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| HP-UX IPF | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Linux for x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Solaris for x64 | 14.1 | 14.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdates
When using the decomposition algorithm for a mixed integer linear mathematical programming problem, PROC OPTMODEL or PROC OPTMILP might stop processing and issue communication error and warning messages.
| Type: | Problem Note |
| Priority: | medium |
| Topic: | Analytics ==> Mathematical Optimization SAS Reference ==> Procedures ==> OPTMILP SAS Reference ==> Procedures ==> OPTMODEL |
| Date Modified: | 2019-06-18 10:47:14 |
| Date Created: | 2019-05-13 09:15:15 |