Error on DLL build with "Include a type library for TestStand or Call Library Nodes" enabled

[Varaprasath]

Hi All,

I just created a VI with a string in and out and tried to create a dll with"Include a type library for TestStand or Call Library Nodes" enabled, Out of 10 station in our Lab around 4 is working fine 6 is returning the below error for the same code. 

Uninstalled and reinstalled LabVIEW and other related software several times still the issue is not getting fixed.

Any ideas ?

LabVIEW Version : 2015.

I was having a doubt that McAfee security policy is blocking but my IT team is denying my claim since other PC are working fine.

 ----------------------------------------Build Errors---------------------------------------------

Possible reasons

An error occurred compiling the DLL because a function or parameter name is illegal. Please verify that the function and/or parameter names are legal C identifiers and do not conflict with LabVIEW headers.
Additional Information: 9 Project link errors
Error generating type library. Midl.exe failed while compiling the odl file used to create the type library.
Note: The error indicates that the odl file has unknown types. This error is possible when
functions with non-standard types are exported using the export qualifier method from files in
release configuration that have not been recompiled during the build process. You can mark all
files for recompilation and repeat the build. To avoid this situation, it is recommended that
you export these functions using the include file method.
Use the generated odl file "c:\Users\vmohan1\AppData\Local\Temp\dlltemp3525.328656\SharedLib.odl" with the command line:
C:\Program Files (x86)\National Instruments\Shared\MSDTRedistributables\BuildTools\8.1\midl.exe "c:\Users\vmohan1\AppData\Local\Temp\dlltemp3525.328656\SharedLib.odl" /win32 /mktyplib203 /tlb "SharedLib.tlb" /IC:\Program Files (x86)\National Instruments\Shared\MSDTRedistributables\BuildTools\8.1 /cpp_cmd c:\program files (x86)\national instruments\shared\lvdb 2015\bin\preprocessor.exe
to see what errors midl.exe reported.

ERROR_REPORTED_TO_USER

Details 

Click the link below to visit the Application Builder support page. Use the following information as a reference:

Error -2147221480 occurred at Compile DLL Stub.vi -> AB_Engine_DLL_Build_Stub.vi

This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.

Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (-2147221480) or for its hexadecimal representation (0x80040018).

[Varaprasath]

Dear NI,

Kindly comment.

I also noticed "C:\Users\vmohan1\AppData\Local\Temp\dlltemp3525.328656\" folder and files are getting generated and deleted immediately, which doesn't allow me to use the *.odl in midl.exe via command prompt.

I couldn't debug and check "AB_Engine_DLL_Build_Stub.vi" since it is password protected.

This issue is found in many of our Lab Stations.

[Varaprasath]

The problem can be either LabVIEW is not generating the *.odl files or midl.exe is not working correctly.

If I can get some *.odl files, I can use midl.exe via command prompt and do some checks.

[Varaprasath]

looks like this kind of issue occurred earlier https://lavag.org/topic/6873-app-builder-fails-creating-dll/ but solution was not posted. 

[Fapp]

Same problem here 

I could take a snapshot of the .odl file.

[LucianH]

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001Dm3nCAC&l=en-US

there is an solution from NI 😄 but I need that type lib for test stand use of the dll. So after installing MDTB Tool mentioned in possible reason https://www.ni.com/en/support/downloads/software-products/download.microsoft-development-technologie...

I am able to build even with type library checked. 

cheers