12-01-2023 10:36 AM
Hello,
I have various PCs with Labview 2012 apps running. I read the following article https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001DjeMCAS&l=fr-BE
If I build a Labview 2012 installer I confirm that I get the nisvcloc.exe in <Program Files>\National Instruments\Shared\NI WebServer\
If I build a Labview 2022 installer on a PC that never saw another Labview product previously then I do get this exe file in \\Program Files (x86)\National Instruments\Shared\nisvcloc
The problem is if I run a Labview 2022 installer on a PC that had a Labview 2012 installer previously executed. In that case I also see the exe in \\Program Files (x86)\National Instruments\Shared\nisvcloc BUT there is no track of the NI Service Locator in the services.msc list.
One of the consequences is that I get the "Failed to Start Debug Server" message prompt when I launch my Labview 2022 executables.
I need to maintain both Labview 2012 and 2022 on the same PC.
What is going on?
Thank you
Christophe
12-01-2023 11:17 AM
@Christ0phe wrote:
I need to maintain both Labview 2012 and 2022 on the same PC.
None of the Windows versions support both LabVIEW 2012 and 2022. It is possible to have both 2012 and 2022 work properly on a same PC at a same time.
See LabVIEW and Microsoft Windows Compatibility
12-04-2023 03:01 AM
Hello,
There is the theory and what it means in the real-world and all depends on the functionalities of Labview that the application uses. Practically speaking off my 150 stations running 24/7 all are set up using the same Windows 10 image. Half of them are running the Labview 2012 version of my app and the other half the Labview 2022 version. Everything runs well.
The only problem is if I try to install both Labview 2012 and 2022 runtimes on the same PC as I explained it above... and the problem is only this initial error message when starting the app, after clicking OK, the apps run without a problem.