From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
10-16-2020 02:57 AM
Setup: TestStand 2019 f3 32-bit
We have created a CSV-based Sequence translator. We try to open a csv file on a colleague's computer, and we get this error:
We know that the file format is ok, because it works fine on my machine.
We can see that the translator is in the correct location of <TestStand Public>:
Note that we have changed our environment file to have the public directory redirected to T:\. As I mentioned, this is working fine on my machine, but not on my colleagues.
Does the DLL need to be registered somewhere?
Does the error indicate that TestStand simply doesn't know about the translator we've created?
Thanks in advance for any guidance!
Solved! Go to Solution.
10-16-2020 04:05 AM - edited 10-16-2020 04:06 AM
Maybe you should have a look on the search directories (Configure -> Search Directories). So you could be sure that TestStand will find your .DLL
10-16-2020 03:27 PM
The correct paths seemed to be present, but I will play around with that a bit and see if it helps. Thanks for your suggestion MOBA!
10-16-2020 03:44 PM
Hi,
Based on the error, it looks like TS engine is unable to load the translator DLL. Can you check if you are missing any dependencies?
Regards,
Anand Jain
NI
11-03-2020 05:58 PM
One developer did this to get it to work:
1) Updated the search directories to include the path to the translator high up in the list)
2) Ensured all associated files/dependencies were there (ie. including the .lib file)
That didn't work for another developer, but when they rebuilt the DLL, they were able to get it to work.
So some slight differences between our dev environments seems to have caused this issue.
But anyway, its solved now, so thanks for your recommendations.