Why do I receive a License Manager Error -4 in Polyspace?

Why do I receive a License Manager Error -4 when running a job in Polyspace Bug Finder, either locally or on a remote Code Prover server?

Answer 1

[MathWorks Support Team]

This error indicates that the Polyspace Bug Finder seat included on your license is currently in use. Polyspace licenses have multiple dependencies which are included with the license. When submitting analyses to be be performed remotely in parallel, these are the license requirements for R2019a and newer:

Client-side

Polyspace_BF (Polyspace Bug Finder)

Polyspace_BF_Engine (Polyspace Bug Finder Engine, included with Polyspace Bug Finder)

Cluster-side

MATLAB_Distrib_Comp_Engine (MATLAB Parallel Server)

Polyspace_BF_Server (Polyspace Bug Finder Server)

Polyspace_CP_Server (Polyspace Code Prover Server)

When using the Processes profile in Polyspace, Polyspace Bug Finder, Polyspace Bug Finder Engine and MATLAB licenses will be checked out. If you're using Polyspace Code Prover, a license for that will be checked out as well.

This error most commonly occurs when 2 sessions of Polyspace are opened on a single machine.

NOTE: Starting in R2019a the following name changes occurred:

•     MATLAB Distributed Computing Server was renamed to MATLAB Parallel Server
•     mdce_def was renamed to mjs_def
•     mdce binary was renamed to mjs