04-07-2011 09:23 PM
HI all,
I have struggled with this for 2 days now and tried to use the forum to figure this one out, but I cannot. I have built quite a few deployments before, however, when I try to put a new deployment on a clean Win7 32-bit PC, I get the same issue:
Whenever I try to run the deployment I get the lvrt.dll error...please see JPEG. I am not sure why I am getting this. However, I have two concerns that may be causing it.
1. If you look at the error, it is looking in the Program Files (x86) folder....I don't have that folder on my Win 7 32 bit machine....only Program Files.
2. It seems like when I run the deployment, it is totally skipping the model. I believe this because the error it gives is for a sequence in main, and I have a vi call in the model. However, i do have the cfg folder in my workspace.
Any ideas?
Thanks,
Ryan
04-07-2011 11:03 PM
SimpleJack
What version of TS are you using? Can you post your Testexec.ini file from the cfg folder.
Regards
Anand Jain
National Instruments
04-08-2011 10:29 AM
Hi, I am using 4.2. I believe I have solved that issue. It was an issue with the wrong engine below loaded.
However, I am stuck here now. When I build, I get the following warnings, and I cant seem to solve it. Please advise. I realize it wants me to add some paths in the search directories but I'm not sure exactly what it should be.
Thanks,
Ryan
---------------------------------------
Warning: There is no relative path between the following files. You may need to add a path to your search directories.
From [TestStand]\Components\Models\TestStandModels\FT_ParallelModel.seq to [Installation Directory]\vi\user_stats.vi
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\SeqEdit\layout_Small Screen Example.bin
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\SeqEdit\layout_Large Screen Example.bin
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Users.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\ToolMenu.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TeststandPersistedOptions.opt
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TestStandModelReportOptions.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TestStandModelModelOptions.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TestExec.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Templates.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\StationGlobals.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\PLPropertyLoader.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Filter.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\EngineParts.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\DeploymentUtilityOptions.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\DeploymentUtility.log
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Deployment Utility RecentFiles.ini
+++++++++++++++++++++++++++++++++++++++
04-11-2011 10:43 AM
Hi SimpleJack,
It looks like there are 2 directories there that need to be added to your search paths.
[Installation Directory]\vi\user_stats.vi
[Installation Directory]\TS\MF_Final_Test.tpj
You can add them by going to Configure >> Search Directories...
If you still receive errors, verify that the TestStand directories that are mentioned are also included in the Search Directories.
You may also want to include the search directories with your deployment. You can do this by adding the TestExec.ini file to the deployment. Here is more information on that.
Regards,
Brandon V.
Applications Engineering
National Instruments