NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Module for step not loadable

Hello 

 

I use Teststand 2014 and Labwindows CVI 2015. When i create a dll in CVI (witch is used in Teststand) it is without errors. When i load my sequence file in Teststand and run Analyze i get an error on each teststep with the message Module for step  not loadable (zie message below). What can be the problem ?. I never saw this before. When i Analyze other projects on the same computer it is without problems so the files that " can't be found" are on the pc. So i don't now why the dll's can't be found. Is it a setting in Labwindows CVI ?

 

Severity Rule Category Text File Location
Error Code modules must be able to load General Module for Step 'Close SafetyCover' not Loadable. Could not load DLL or external library 'C:\Temp\FT_KW_PFC\CVI_2015\PFC.dll'.

This DLL requires the following DLLs which could not be found or loaded:
api-ms-win-core-console-l1-1-0.dll (Not Found)
api-ms-win-core-datetime-l1-1-1.dll (Not Found)
api-ms-win-core-debug-l1-1-1.dll (Not Found)
api-ms-win-core-errorhandling-l1-1-1.dll (Not Found)
api-ms-win-core-fibers-l1-1-1.dll (Not Found)
api-ms-win-core-file-l1-2-1.dll (Not Found)
api-ms-win-core-handle-l1-1-0.dll (Not Found)
api-ms-win-core-heap-l1-2-0.dll (Not Found)
api-ms-win-core-localization-l1-2-1.dll (Not Found)
api-ms-win-core-libraryloader-l1-2-0.dll (Not Found)
api-ms-win-core-memory-l1-1-2.dll (Not Found)
api-ms-win-core-namedpipe-l1-2-0.dll (Not Found)
api-ms-win-core-processenvironment-l1-2-0.dll (Not Found)
api-ms-win-core-processthreads-l1-1-2.dll (Not Found)
api-ms-win-core-profile-l1-1-0.dll (Not Found)
api-ms-win-core-string-l1-1-0.dll (Not Found)
api-ms-win-core-synch-l1-2-0.dll (Not Found)
api-ms-win-core-sysinfo-l1-2-1.dll (Not Found)
api-ms-win-core-util-l1-1-0.dll (Not Found)
api-ms-win-eventing-provider-l1-1-0.dll (Not Found)
api-ms-win-core-apiquery-l1-1-0.dll (Not Found)
api-ms-win-core-registry-l1-1-0.dll (Not Found)
api-ms-win-core-heap-l2-1-0.dll (Not Found)
api-ms-win-core-libraryloader-l1-2-1.dll (Not Found)
api-ms-win-devices-config-l1-1-1.dll (Not Found)
api-ms-win-core-kernel32-legacy-l1-1-1.dll (Not Found)
api-ms-win-core-string-obsolete-l1-1-0.dll (Not Found)
api-ms-win-core-heap-obsolete-l1-1-0.dll (Not Found)
api-ms-win-core-stringansi-l1-1-0.dll (Not Found)
api-ms-win-core-crt-l1-1-0.dll (Not Found)
api-ms-win-core-crt-l2-1-0.dll (Not Found)
api-ms-win-security-base-l1-2-0.dll (Not Found)
api-ms-win-core-io-l1-1-1.dll (Not Found)
api-ms-win-core-threadpool-l1-2-0.dll (Not Found)
api-ms-win-core-wow64-l1-1-0.dll (Not Found)
api-ms-win-core-delayload-l1-1-1.dll (Not Found)
api-ms-win-devices-query-l1-1-1.dll (Not Found)
api-ms-win-core-timezone-l1-1-0.dll (Not Found)
api-ms-win-core-file-l2-1-1.dll (Not Found)
api-ms-win-core-kernel32-private-l1-1-1.dll (Not Found)
api-ms-win-mm-time-l1-1-0.dll (Not Found)
api-ms-win-mm-mme-l1-1-0.dll (Not Found)
api-ms-win-mm-misc-l1-1-1.dll (Not Found)
api-ms-win-mm-joystick-l1-1-0.dll (Not Found)
api-ms-win-core-path-l1-1-0.dll (Not Found)
api-ms-win-core-rtlsupport-l1-2-0.dll (Not Found)
api-ms-win-core-kernel32-private-l1-1-2.dll (Not Found)
api-ms-win-core-privateprofile-l1-1-1.dll (Not Found)
api-ms-win-core-string-l2-1-0.dll (Not Found)
api-ms-win-core-atoms-l1-1-0.dll (Not Found)
api-ms-win-core-localization-obsolete-l1-3-0.dll (Not Found)
api-ms-win-core-sidebyside-l1-1-0.dll (Not Found)
api-ms-win-core-windowserrorreporting-l1-1-0.dll (Not Found)
api-ms-win-core-appinit-l1-1-0.dll (Not Found)
api-ms-win-core-localization-private-l1-1-0.dll (Not Found)
api-ms-win-eventing-classicprovider-l1-1-0.dll (Not Found)
api-ms-win-eventing-obsolete-l1-1-0.dll (Not Found)
api-ms-win-core-interlocked-l1-2-0.dll (Not Found)
api-ms-win-core-threadpool-legacy-l1-1-0.dll (Not Found)
api-ms-win-core-processthreads-l1-1-3.dll (Not Found)
api-ms-win-core-synch-l1-2-1.dll (Not Found)
api-ms-win-core-file-l1-2-2.dll (Not Found)
api-ms-win-core-job-l1-1-0.dll (Not Found)
api-ms-win-core-threadpool-private-l1-1-0.dll (Not Found)
api-ms-win-core-largeinteger-l1-1-0.dll (Not Found)
api-ms-win-core-libraryloader-l2-1-0.dll (Not Found)
api-ms-win-core-namedpipe-l1-2-1.dll (Not Found)
api-ms-win-core-datetime-l1-1-2.dll (Not Found)
api-ms-win-core-sysinfo-l1-2-3.dll (Not Found)
api-ms-win-core-processsnapshot-l1-1-0.dll (Not Found)
api-ms-win-core-errorhandling-l1-1-3.dll (Not Found)
api-ms-win-security-appcontainer-l1-1-0.dll (Not Found)
api-ms-win-core-comm-l1-1-0.dll (Not Found)
api-ms-win-core-realtime-l1-1-0.dll (Not Found)
api-ms-win-core-wow64-l1-1-1.dll (Not Found)
api-ms-win-core-systemtopology-l1-1-0.dll (Not Found)
api-ms-win-core-processtopology-l1-2-0.dll (Not Found)
api-ms-win-core-namespace-l1-1-0.dll (Not Found)
api-ms-win-core-file-l2-1-2.dll (Not Found)
api-ms-win-core-xstate-l2-1-0.dll (Not Found)
api-ms-win-core-localization-l2-1-0.dll (Not Found)
api-ms-win-core-normalization-l1-1-0.dll (Not Found)
api-ms-win-core-fibers-l2-1-1.dll (Not Found)
api-ms-win-core-appcompat-l1-1-1.dll (Not Found)
api-ms-win-core-console-l2-1-0.dll (Not Found)
api-ms-win-core-psapi-l1-1-0.dll (Not Found)
api-ms-win-core-psapi-ansi-l1-1-0.dll (Not Found)
api-ms-win-security-activedirectoryclient-l1-1-0.dll (Not Found)
api-ms-win-eventing-controller-l1-1-0.dll (Not Found)
api-ms-win-eventing-consumer-l1-1-0.dll (Not Found)
api-ms-win-service-core-l1-1-1.dll (Not Found)
api-ms-win-service-core-l1-1-2.dll (Not Found)
api-ms-win-service-management-l1-1-0.dll (Not Found)
api-ms-win-service-management-l2-1-0.dll (Not Found)
api-ms-win-service-private-l1-1-1.dll (Not Found)
api-ms-win-service-winsvc-l1-2-0.dll (Not Found)
api-ms-win-security-base-private-l1-1-1.dll (Not Found)
api-ms-win-core-registry-l1-1-1.dll (Not Found)
api-ms-win-security-audit-l1-1-1.dll (Not Found)
api-ms-win-core-perfcounters-l1-1-0.dll (Not Found)
api-ms-win-core-string-l2-1-1.dll (Not Found)
api-ms-win-core-localization-l1-2-2.dll (Not Found)
api-ms-win-core-version-l1-1-0.dll (Not Found)
api-ms-win-core-shlwapi-obsolete-l1-2-0.dll (Not Found)
api-ms-win-core-shlwapi-legacy-l1-1-0.dll (Not Found)
api-ms-win-core-kernel32-legacy-l1-1-3.dll (Not Found)
api-ms-win-core-url-l1-1-0.dll (Not Found)
api-ms-win-core-registryuserspecific-l1-1-0.dll (Not Found)
api-ms-win-storage-exports-internal-l1-1-0.dll (Not Found)
api-ms-win-storage-exports-external-l1-1-0.dll (Not Found)
api-ms-win-shell-shellcom-l1-1-0.dll (Not Found)
api-ms-win-shell-shellfolders-l1-1-0.dll (Not Found)
api-ms-win-core-job-l2-1-0.dll (Not Found)
api-ms-win-core-com-l1-1-1.dll (Not Found)
api-ms-win-core-com-midlproxystub-l1-1-0.dll (Not Found)
api-ms-win-core-winrt-string-l1-1-0.dll (Not Found)
api-ms-win-core-winrt-error-l1-1-1.dll (Not Found)
api-ms-win-security-sddl-l1-1-0.dll (Not Found)
api-ms-win-core-com-private-l1-1-0.dll (Not Found)
api-ms-win-core-com-private-l1-1-1.dll (Not Found)
api-ms-win-core-quirks-l1-1-0.dll (Not Found)
api-ms-win-core-psm-key-l1-1-0.dll (Not Found)
api-ms-win-core-versionansi-l1-1-0.dll (Not Found)
cicmx.dll (Not Found)
7823088.seq Seq["MainSequence"].Setup["Close SafetyCover"].TS.SData

0 Kudos
Message 1 of 6
(4,003 Views)

I don't use Labwindows CVI, but maybe mass compiling your VIs might help?

0 Kudos
Message 2 of 6
(3,977 Views)

Hope it depends on the Mode of Step Execution,

 

if you are using "Execute Steps In- Process (LabWindows/CVI is not required for this mode )", then make sure CVI Modules are Complied properly.

----------------------------------------------------------------------------------------------------------------
Palanivel Thiruvenkadam | பழனிவேல் திருவெங்கடம்
LabVIEW™ Champion |Certified LabVIEW™ Architect |Certified TestStand Developer

Kidlin's Law -If you can write the problem down clearly then the matter is half solved.
-----------------------------------------------------------------------------------------------------------------
0 Kudos
Message 3 of 6
(3,969 Views)

Hello,

 

I've exactly the same problem. Do you have fix it ?

 

Thanks

0 Kudos
Message 4 of 6
(3,477 Views)

I also have the same issue. Was this ever solved?

0 Kudos
Message 5 of 6
(3,308 Views)

Yes the problem is solved but i don't know what the solution was. I wasn't done by myself. Sorry for that

0 Kudos
Message 6 of 6
(3,281 Views)