labviewsolutions

is a Call Library Node in your own code that is calling a poorly written DLL or a poorly configured Call Library Node that doesn't match what the underlying DLL is doing.

Yes, I also have seen this error before: The problem was that the VI uses a "Call Library Node" to call LabView itselfe and for some reasons it seems that the app builder uses the wrong LabVIEW File/Version to call (there where more than on versions of the LabVIEW runtimelib on the machine). Reinstalling LabVEIW fixes the problem for me.

This method has several flaws. First the offset to the MD5 in the VI is not always in the same place. It can change based on LabVIEW version number, or just the format of the VI may cause the structure to change. But if you got a large enough sample a set of offsets could be used.

hooovahh is right. The password is saved as a md5 hash. The problem is that the offset differs from file to file.

A few days ago I was looking for a way get the hash from the VI-file. After some time of searching i find this

website.

There, you can upload a VI file and the page extracts/finds the password-hash. But this site makes me scared because you can simply overwrite the file-password - so no need to crack/brute force the password at all.

Happy New Year!

You can simply overwrite all VI password using this online-tool:

http://www.hmilch.net/hmilch.php/labview.php

Have fun