10-10-2023 09:56 AM
Hi all. We have a existing customer-facing application built with 2017 Labview. For reasons of backwards compatibility back in 2017 when the application was written, we built this with 32-bit Labview. Fairly obviously then, it needs the 32-bit LV2017 runtime engine, and we distribute that with the application.
We've had reports from customers who've installed more recent versions of Labview (specifically LV2022, but we have no idea whether it happens on previous versions too) that they could not install the LV2017 runtime. (See the attached picture of where the installer refuses to go further.)
I did wonder if a more recent runtime would supersede this and allow the application to run anyway, but in fact it doesn't work. (See the attached picture again.)
I'm not sure what's happening here, or how to fix it. I would expect applications to possibly have issues with different versions of Windows (MS changing the rules under you is always a possibility!), but as far as I knew, I expected different versions of LV to install side-by-side without problems.
Does anyone have any advice for what we can do about this, please?
10-10-2023 11:30 AM
Several comments.
You might have a working LabVIEW system. Did you try running LabVIEW 2017 software? Did you get an Error? Can you get a good "capture" of the error? Can you attach the VI that caused the error (it should be the last one mentioned on the Error message)?
Bob Schor
10-10-2023 02:30 PM
That combination of LabVIEW tricked me. That was a post earlier about problem with LabVIEW 2022.
See this post:
https://forums.ni.com/t5/LabVIEW/Installer-does-not-work-on-different-PC/m-p/4331456#M1269172
You might need to install VC 2015 to fix the problem.
10-18-2023 04:48 AM
I've just searched the text from the second picture, and came up with this. It's exactly the same error message.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000g1PuSAI&l=en-GB
We'll go and ask the customer to follow the repair process.