Ansys Insight: Fixing MPI related 'Job error' when running Lumerical simulations

LitoLito Ansys Employee Posts: 37
edited April 2021 in Ansys Products

When you ran into 'Job Error' while running Lumerical simulation, right click on the job status and 'View job details'.

Depending on the job error details, this can sometimes be related to the MPI installation.

Typical 'Job Errors' due to MPI:

  • Error: failed to run job! Could not find MPI executable: 
  • Invalid MPI path
  • Unable to connect to host
  • Failed... Possible error: license not configured

Resolve by installing the MPI:

  • Check Windows 'Control Panel > Programs and Feature', if 'Microsoft MPI' and 'Intel MPI' are on the list of install software. If these are not found, install them from the Lumerical installation package. If these are installed, your current installation might be corrupted and needs to be fixed.

Prior to installation. Ensure that Lumerical is not open or running in the background. If the MPI is already installed and you are still having issues, Uninstall this MPI.

Microsoft MPI installation. Open the ‘MS-MPI’ folder inside the ‘Lumerical_Suite’ folder in the extracted Lumerical installation package. Run msmpisetup.exe. Install with default options when prompted and complete the installation.

Intel MPI installation. Open the ‘intel_mpi_runtime’ folder inside the ‘Lumerical_Suite’ folder in the extracted Lumerical installation package. Run w_mpi-rt_p_2018.4.274.exe. Extract and install with default options when prompted and complete the installation.

Run simulation with MPI. Open and run your simulation using the installed MPI as your job launching preset in the Resource advanced options in the Resource configuration.

Install Lumerical without the MPI. Install using the 'lumerical_data.msi' installer. This will not check and install the MPI components on your PC.

Run jobs without MPI. If for some reason you are unable to install the MPI, and you are only running simulations on your PC, use 'Local Computer' as your job launching preset.

See also:


This discussion has been closed.