07-09-2014 02:45 AM
the Issue was already solved by Me
07-09-2014 10:37 AM
@aparab wrote:
the Issue was already solved by Me
Yes, I was just proposing an alternate solution, build "Release" versions of your dlls.
-Doug
07-17-2015 09:30 AM
Hi guys,
unfortunate as it may be, its a dying need to reopen this thread after 1 yr.
Using Testsand Ver 2012 labview 2012 f3
I find myself tangled in a snake pit, This time the Situation is different , I am trying to use the Labview Runtime with the Teststand Seq file (another project).
I did a mass compile in the project & in Labview(Tools> Advanced >Mass compile) Result ->> all well
The Seq. runs fine when the labview Adapter setting is Dev system.
No sooner I switch the Labview Adapter to Run-time Engine than starts the problem, "Failed to Load a required Step's associated module Err:-17600"
my prep
- the DLL mentioned in this thread(msvcr100d.dll) is present
- All paths are relative,
- search directories are clean
Any workaround or hint for this newly found old issue!!
03-04-2018 07:28 AM
Any solutiuon ?
@aparab wrote:
Hi guys,
unfortunate as it may be, its a dying need to reopen this thread after 1 yr.
Using Testsand Ver 2012 labview 2012 f3
I find myself tangled in a snake pit, This time the Situation is different , I am trying to use the Labview Runtime with the Teststand Seq file (another project).
I did a mass compile in the project & in Labview(Tools> Advanced >Mass compile) Result ->> all well
The Seq. runs fine when the labview Adapter setting is Dev system.
No sooner I switch the Labview Adapter to Run-time Engine than starts the problem, "Failed to Load a required Step's associated module Err:-17600"
my prep
- the DLL mentioned in this thread(msvcr100d.dll) is present
- All paths are relative,
- search directories are clean
Any workaround or hint for this newly found old issue!!
03-05-2018 08:10 AM
msvcr100d.dll is part of the debug version of the VC runtime is not something you should be using on a deployed machine. You should be building the release versions of all of your dlls instead and then using the VC++ runtime redistributable package to install the release version of the vc runtime.
Hope this helps,
-Doug