NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to Load a required Step's associated module Err:-17600

Solved!
Go to solution

the Issue was already solved by Me

0 Kudos
Message 11 of 15
(2,012 Views)

@aparab wrote:

the Issue was already solved by Me


Yes, I was just proposing an alternate solution, build "Release" versions of your dlls.

 

-Doug

0 Kudos
Message 12 of 15
(2,006 Views)

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!!

 

 

0 Kudos
Message 13 of 15
(1,337 Views)

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!!

 

 


 

0 Kudos
Message 14 of 15
(593 Views)

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

0 Kudos
Message 15 of 15
(576 Views)