09-26-2018 09:39 AM
So I have ran across this and am having the reverse issue, I have some 2015 code downgraded to 2011 SP1. I run fine when inside of development however, even on the exact same PC, I create the executable and it will no longer run and just gives the "Error 7, Call Library Function Node". It is searching for the file at startup even though I have it inside the root, inside the data folder (Support), even inside system32 folder. I placed another lvimptsl.dll inside the project and packaged it with it in order to get rid of the find file message however the function is still returning the error 7.
When I try and package the exact dll with the callers associated into the "Always Include" Field during building it says the file is not saved. I have found no way to 'save' the DLL. Mass Compile, Save all, anything lse has not worked so far. Does anyone have any idea of how to build this and get around the error 7?
Thank You,
Rob Slad
09-26-2018 04:25 PM
Here is a picture of the XNode that is causing me issues in my 2011 SP1 Version. Just in case there is another way to accomplish this task.
09-27-2018 02:22 PM
Well, I found out my own solution eventually, it was a multipart.
First I had to enable Xnodes in LabVIEW by editing the LabVIEW.ini file inside of the labview executable folder and add this line.
xnodewizard=true
Then I could finally see the xnode code.
Due to this code being shared I had no clue where the utilized lvimptsl.dll was located (Neither could LabVIEW for that matter)
So I could view the code from the xnode finally instead of it being read-only.
I copied the whole set of code and pasted it into a new VI. I could now take the lvimptsl.dll out of the dependencies and put it in the base of my project. Viola! LabVIEW would allow me to finally put it as 'Always Included' and I could set it into the root directory with the .exe I was building.
Then I would through the shared code and replaced every xnode with my VI and everything worked like a charm.