labview system.io.filenotfoundexception

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

相关文章推荐

粗眉毛的松鼠 · String Value Test ...· 8 小时前 ·

呐喊的乌冬面 · 2020年中国法院10大知识产权案件和50件 ...· 1 月前 ·

文雅的开水瓶 · 人民教育家先进事迹——于漪· 10 月前 ·

重情义的铁链 · 机器学习三人行-手写数字识别实战-腾讯云开发 ...· 1 年前 ·

忐忑的眼镜 · 收不到的邮件右下角有弹窗帮忙看一下是什么原因 ...· 1 年前 ·

高兴的山羊 · 发生了未经处理的异常（"system.io. ...· 1 年前 ·

Hi All,

I'm getting the labview system.io.filenotfoundexception error when executing the application built from my VI.

Initially I was getting this error (screenshot below), which I mitigated by placing the missing . llb in "data" folder in the application directory:

However now I'm getting this error (screenshot below) and can't figure out what exactly is missing:

I tried using Process Monitor from sysinternals with no help as I'm getting thousands of lines even after filtering to see prompts initiated by the application only.

I also reviewed all the associated VI's and subVI's using LLB manager. I have reconfigured some path's which Labview couldn't locate by itself, however the problem is still there...

Any help is much appreciated!

Regards,

Alibek

It seems to me the dlls are loaded and executing as expected.

A .NET function in Run Ultracom.vi is trying to locate a file (not a dll), and that file cannot be found.

If the file is passed by the VI to the function, put a popup in the VI so the exe shows the path. If not, you'll have to dig until you find what file is missing.

LabVIEW Programming ( (make LV more popular, read this)

Found the problem. When compiling (building the .exe), Labview placed one of the dependant files into the "data" folder, while it should have been sitting in the same folder with the created executable.

Would be much easier if labiew indicated exactly what file was missing in the first place...

@Alibek70 wrote:

Found the problem. When compiling (building the .exe), Labview placed one of the dependant files into the "data" folder, while it should have been sitting in the same folder with the created executable.

The file can be placed in the executable root directory*, but it's not by default.

* You can change this in the "destination" tab in the execution builder, but you first have to add a destination, IIRC.

@Alibek70 wrote:

Would be much easier if LabVIEW indicated exactly what file was missing in the first place...

LabVIEW functions give a detailed error, and it would be up to the programmer to report them. However, the .NET errors are a bit more abstract...

LabVIEW Programming ( (make LV more popular, read this)