What is the "primary message table for module 77"?

3 views (last 30 days)
Tonny Madsen
Tonny Madsen on 5 Oct 2016
Commented: Bo Li on 11 Oct 2016
We use the engine interface to call functions in Matlab from Python. But every now and then we get the following message during engOpen, after which the application exists unconditionally:
Internal Error: A primary message table for module 77 was already registered with a differing collection of error messages.
Process exited with code 1
What exactly is going on here? Right my application exits consistently for R2016a!
A little background:
  • We open the engine multiple times from the application. We sometimes see some transient errors from Matlab, in which case, we close the engine and re-open it again. This works fine in our unit tests (where Matlab is opened via the engine API 15 times) and most of the time in the application.
  • We have seen this problem both in Matlab R2011b and R2016a (we have not used any on the intervenient releases) Right now we see the issue consistently on R2016a!

Accepted Answer

Bo Li
Bo Li on 5 Oct 2016
You may try to create a dummy Engine object using engOpen and keep it alive until the end of the application. Meanwhile, you can use engOpen to create Engine repeatedly. The dummy Engine can avoid the issue of unloading/loading of related libraries.
The other solution is to consider MATLAB Engine API for Python:
  4 Comments
Bo Li
Bo Li on 11 Oct 2016
Yes, using engOpenSingleUse on Windows for the "dummy Engine" makes sense. On Linux, engOpen is enough as Engines cannot be shared.

Sign in to comment.

More Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by