LVMerge.exe not working with LabVIEW 2024 Q3 64-bit

[DBT9]

Hello,

We have upgraded to LabVIEW 2024 Q3 64-bit version a few weeks ago in all our setups and we have tried to run LVMerge.exe tool from cmd with no success. We run the command:

LVMerge.exe "path to base vi" "path to remote vi" "path to local vi" "path to vi to merge"

When we run previous command, LabVIEW Merge executable front panel window opens without showing any error and also opens labview 2024 Q3 but then nothing else happens, the merging UI is not showing.

Could anyone provide any solution to this problem? We have tried installing LabVIEW 2024 Q3 64-bit in many other setups and we have the same results. Instead, when we use LabVIEW 2020 it works just fine and we can merge VIs without any issue.

Thank you.

[Intaris]

Perhaps something else.

LVMerge and LVCompare open in the last active context of the LV IDE. If this is RT or FPGA, the LVCompare and LVMerge code will fail. This will also lead to the program failing to show any UI.

To clarify, just make sure your last mouse click was on "My Computer" in a LV project before calling the merge or compare, see if that helps.

[DBT9]

Thanks for your reply,

I'm calling LVMerge.exe from windows command line window. It works when I specify "C:\Program Files\National Instruments\LabVIEW 2020\LabVIEW.exe" as argument, so LVMerge.exe runs on labview 2020, but it does not work when i run it in LabVIEW 2024 Q3 64-bit specifying "C:\Program Files\National Instruments\LabVIEW 2024\LabVIEW.exe" as first argument (note that I also specify the other 4 arguments after this one which are Base vi path, Remote vi path, Local vi path and merge vi path).

Thank you,

[Intaris]

OK,that's something different.

It seems like your LVMerge and LVCompare EXEs are from LV 2020, not the newer LV version.

I have not used either of these LV versions, and I principally avoid trying to have multiple LV versions on any PC, so I'm not familiar with a lot of LVs idiosyncracies in these cases.

Have you looked at the properties of the EXE in explorer? Rightl-click and view "properties" of the EXE. It should telly ou which version it is.

[DBT9]

I cannot see the LabVIEW version used to build the executable in the properties of the .exe file. Only information I see is:

Thank you,

[Intaris]

Hmm, the version is weird, when I look at LVMerge in my LV 2015 folder, it shows me the following

[dkfire]

I can confirm that for version upto 2021, the version of LVMerge matches the LabVIEW version. 

On 2023 Q3 and 2024 Q3 the LVMerge version is 1.0.0 as OP has shown. 

[dkfire]

I have 2 questions: 

Is LabVIEW 2020 and LabVIEW 2024 installed on the same PC ? 

Can you show the command that you use to can LVMerge for LabVIEW 2024 ?  

[dgdgomez]

I have LabVIEW 2024 Q3 64-bit installed, and LVMerge.exe isn't running properly from TortoiseGit.

The command used is: "C:\Program Files\National Instruments\Shared\LabVIEW Merge\LVMerge.exe" %base %mine %theirs %merged

the result is incorrect, because the Merge VIs window doesn't open:

When the same operation is executed from Tools>Merge>Merge VIs..

the result is correct:

Only LabVIEW 2024 Q3 64-bit is installed.

[JJ_dev]

In that case the reason why LVMerge.exe does not work comes from labview environtment installation. I recently checked  if NI Compact RIO support for LabVIEW 2024 Q3 is installed then the external calls to LVMerge.exe does not work.

After to send the known command from windows console, the CallLVMerge.vi is called by labview and all arguments received from this vi looks fine but the main screen is waiting some unaccessible resource or maybe something is not found during the process. There is no error message reported by the labview application but LVMerge tool does not start.

And yes, Labview professional license has been activated previously. The Labview merge tool works fine if it is called internally and manually from labview menu. (Tools-> Merge->Merge VIs...) but there is no solution yet when the user needs to have the CRIO drivers installed and needs to call merge.exe externally using for example tortoise Git.

The NI Labview version used is LabVIEW 2024Q3.

Can anyone from NI reproduce the bug and suggest a solution? Thank you in advance.