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.
05-18-2020 03:11 AM
Hi all,
Veristand 2019 introduced a new project file format. If I open a project through the UI, it expects me to open a new (nivsprj) file or convert an old (nivsproj) file. However when I try to open files through the .NET API, I get:
That causes a sort of conmfusion for me, as now I don't know which file to keep/use.
I'm using
NationalInstruments.VeriStand.ClientAPI.Factory().GetIProject()
function to open the project.
Error text (opening nivsprj with GetIProject()):
-307650: Error -307606 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Initialization.vi >> NIVSProj_Filemanager.lvlib:LoadDataXMLFile.vi >> NIVSProj_Filemanager.lvlib:LoadProjectXMLFile.vi
Possible reason(s):
NI VeriStand: The file does not contain a valid file format.
Any explanations and/or tips on automating the 2019 R3? Thank you in advance!
05-22-2020 04:36 PM
Hello iwane,
Have you had a chance to view this KB?
05-24-2020 11:19 PM
Hello VA.KI,
Thank you for the link! I haven't seen it yet. The error is similar, but not the same... In the KB, error location is in NIVS_DataStorage.lvlib:LoadDataXMLFile.vi; in my case the error pops up in NIVSProj_Filemanager.lvlib:LoadProjectXMLFile.vi - I suppose that the location matters. Veristand itself starts fine; the problem appears when launching a project from the API.
I think it might be an migration issue, as (maybe) not all features are already migrated to the new file format and both old one and the new one is required for the time being... I'd like to confirm it, though 🙂
05-25-2020 01:05 AM
Hello Piotr,
Fully agree, should be migration issue.
08-16-2021 09:08 AM
did you get the solution?
08-16-2021 11:26 PM
Hi fabio.int,
Yes. I don't really remember the exact issue (and the code that caused it), but after all the solution is to open the *.nivsprj (new project file) file through Veristand command line - calling 'veristand.exe /openProject path_to_proj.nivsprj'. After that, it's enough to create a Workspace2 object. Using GetIProject() also works then, but you should pass the *.nivsproj (old project) file as a parameter (This might be different for non-migrated projects. Ours are migrated from 2018, so have both files).
08-17-2021 01:37 AM
Thank you very much!!!
In my case I have to move from one project to another one, that means that every time I have to close VeriStand and reopen with the right project, isn't it?
Fabio
08-20-2021 12:14 AM
You might have some luck with Veristand command line (https://www.ni.com/documentation/en/veristand/latest/manual/run-operations-command-line-interface/). I'd give not closing Veristand and just opening a new project a shot.