dll CAdapterShared.dll could not be found in the specified path

[aaronli2007]

Quite a number of the dll could not be found occasionally. This is illogical since these dll's are necessary to start the TS Engine. How come only at some instances that they could not be found?

[Jonathan_C]

Hello aaronli2007,

Based on your screenshot, it appears that you are using TestStand 3.1 with a custom Operator Interface.  Also, from what I could tell, it seems that you are doing parallel executions as well.

Do you happen to have multiple versions of TestStand installed on your machine?  If so, have you checked the active version of TestStand in the Version Selector, found at C:\Program Files\National Instruments\Shared\TestStand Version Selector?

This could also easily be a multithreading issue.  You can see an example of a parllel (multithreaded) sequence in C:\Program Files\National Instruments\TestStand 3.1\Examples\ExecutingCodeModulesInParallel to use as a reference.

[aaronli2007]

Hi Jonathan,

Thanks for the reply!

There is only one version installed on the PC ever and it is labview 7.1 & teststand 3.1.

The speicific model we used is a custom batch model and is not running tests in parallel. This allows us to scan in all serial numbers for 3 DUT at the beginning of the test sequence without having to wait in between.

I have reviewed the parallel sequence you mentioned and it is a fairly simple sequence.  However, it does help me identifying my own problem. You mentioned that multithreading can easily see this issue.  Can you pls elaborate or point direction how I can eliminate / avoid this issue?

thanks
Aaron

[Jonathan_C]

Hi Aaron,

I have seen similar error in the past when using multithreaded / parallel executions that do not properly implement locking and syncronization.  However, since you are executing using a batch model, this should not be an issue.

Does the seqence that you are executing contain steps that use the C/CVI Standard Prototype Adapter?  If so, this error could relate to how you have configured the C/CVI Standard Prototype Adapter from within TestStand.  When you configure the C/CVI Standard Prototype Adapter to execute steps in an external instance of CVI, the adapter launches a copy of LabWindows/CVI and loads an execution server project. The default execution server project is TestStand\AdapterSupport\CVI\tscvirun.prj. If this project's target type is set to something other than "Executable" (i.e. DLL or Static Library), you will get Error -17004 when the adapter tries to run the project.

To eliminate this error you may do one of the following:

1. Set the target type of the project to executable. To do this you must:
   
   • Launch LabWindows/CVI and load TestStand\AdapterSupport\CVI\tscvirun.prj.
     
   • Configure the project to create a debuggable executable by selecting Build»Target Type»Executable and then Build»Configuration»Debug.
   • Close LabWindows/CVI (optional).
   
   
2. Configure the C/CVI Standard Prototype Adapter to execute steps In-Process. To do this you must:
   
   • From within TestStand, select Configure»Adapters
     
   • Under "Configurable Adapters" highlight the LabWindows/CVI Standard Prototype Adapter and click "Configure"
   • In the window that appears, select the second bullet, "Execute Steps In-Process".

Note: If you select "Execute Steps In-Process" (option 2) you will not be able to debug your code modules from within the TestStand environment.