Distributed parallel processing is not supported for Windows systems. As a result, the --cnf command-line argument is not available for Windows and, if issued, will cause System Coupling to generate an exception.

For local jobs that were set up using the --cnf argument, you may instead use the -t option to specify the number of cores.

For more information on configuring parallel participant execution on Windows, see Parallel Processing for Coupling Participants.

When submitting a job to RSM on a machine that uses Microsoft HPC Pack 2019, you may receive an error message indicating that the coupling process failed to start.

To address this issue, submit the job on another resource, either by using an earlier version of HPC Pack or by submitting the job on a Linux system.

When submitting a job to RSM on a machine that uses Microsoft HPC Pack 2019, you may receive an error message indicating that the coupling process failed to start.

To address this issue, submit the job on another resource, either by using an earlier version of HPC Pack or by submitting the job on a Linux system.

System Coupling jobs sent to RSM must run in the foreground, and all coupling participant setups must be consistent with that of System Coupling. Any coupling participant with its Solution cell's Solution Process | Update Option property set to Run in Background will fail to connect to System Coupling.

To avoid this issue, ensure that any CFX coupling participant has its Solution | Update Option property set to Run in Foreground before submitting a coupling job to RSM.

Once an update has been attempted with a CFX participant’s Solution | Update Option property set to Run in Background, you may find that it is not possible to change the value of this setting for CFX. To address this issue, first reset System Coupling's Solution cell and then set CFX to perform updates using Run in Foreground.