Why do I receive a "procedure entry point" error concerning tbb.dll when executing a MATLAB Compiler standalone application outside MATLAB?

I have a standalone application that I generated using MATLAB Compiler. It runs fine inside MATLAB Desktop(e.g., using the ! operator) , but when I run the executable file outside of MATLAB, I receive errors such as:

ERROR: The procedure entry point
?internal_empty@concurrent_queue_base_v3@internal@tbb@@IEBA_NXZ could not be located in the dynamic link library tbb.dll.

The procedure entry point
?throw_exception_v4@internal@tbb@@YAXW4exception_id@12@@Z could not be located in the dynamic link library C:\Program Files\MATLAB\R2019a\bin\win64\libmwms.dll

The procedure entry point
?internal_empty@concurrent_queue_base_v3@internal@tbb@@IEBA_NXZ could not be located in the dynamic link library C:\Program Files\MATLAB\MATLAB Compiler Runtime\v83\bin\win64\libmwms.dll

Answer 1

[MathWorks Support Team]

The error arises due to the presence of multiple versions of the "tbb.dll" on your computer. "tbb.dll" is part of Intel's Threading Building Blocks library, and a copy of it is also shipped with MATLAB and MATLAB Runtime.

The tbb.dll that comes with MATLAB can be found in '$MATLABROOT\bin\win64'. When the error occurs, your application is most likely picking up a different version of tbb.dll from the "C:\Windows\System32" folder.

There are two possible workarounds:

1) Drag a copy of MATLAB's tbb.dll and place it within the same folder as your application file. Because Windows search path mechanism is:

1. Current directory where the .exe resides

2. Windows System paths

3. PATH environment variables.

The above workaround is to force the process to pick up the required version of tbb.dll.

2) Back up the "tbb.dll" file in your C:\Window\System32 directory before removing it. This will restore functionality to your compiled MATLAB applications, but may break the functionality of whichever 3rd party application that originally placed the "tbb.dll" file in your C:\Window\System32 directory. Once the exact 3rd party application can be verified, placing the backup "tbb.dll" directly in that application's installation directory should resolve the issue.