09-16-2024 09:03 AM
Hi,
With TS 2020, when using the CLI of the Sequence Analyser, having a /env switch generates an error.
Command Example :
C:\Program Files (x86)\National Instruments\TestStand 2020\Bin\AnalyzerApp.exe "D:\XXXXX\Environment\Public\MyAnalyzerProject.tsaproj" /analyze /report "D:\XXXXX\Environment\Public\MyAnalyzerProject.xml" /save /quit /env "D:\XXXXX\MyEnvFile.tsenv"
The .tsenv exists and is correctly loaded (visible on the lower part of the front panel of AnalyzerApp.exe), but the return numeric code is -1073741787 instead of the numeric code of the status of the analysis execution.
Removing the /env switch remove the error but it is not suitable for an exported TS environment.
I believe it's a bug, easily reproductible.
09-17-2024 04:35 AM
Anybody from the TestStand dev team ?
09-17-2024 01:29 PM
These forums are mostly end-users. The best way to report a bug is located here: Report an NI Software Bug - NI
09-25-2024 10:49 AM
I did the service request but of course as usual I got no answer from NI.
I did new tests and finally come up to the conclusion that the culprit is not /env switch but the call to a VI inside a PPL. So the post become :
With TS 2020, when using the CLI of the Sequence Analyser, having at least one step with a call to a VI inside a PPL generates an error.
Command Example :
C:\Program Files (x86)\National Instruments\TestStand 2020\Bin\AnalyzerApp.exe "D:\XXXXX\Environment\Public\MyAnalyzerProject.tsaproj" /analyze /report "D:\XXXXX\Environment\Public\MyAnalyzerProject.xml" /save /quit /env "D:\XXXXX\MyEnvFile.tsenv"
The .tsenv exists and is correctly loaded (visible on the lower part of the front panel of AnalyzerApp.exe), but the return numeric code is -1073741787 or -1073740791 instead of the numeric code of the status of the analysis execution.
I believe it's a bug, easily reproductible.
09-25-2024 10:50 AM
Let me cross another related post here :