"Error 7" appearing in executable

[mbocchinfuso]

Hello all:

Late last week, a test setup we have running began giving us errors with regards to a Labview executable that is deployed on it.

Initial check of any recent Windows updates, or changes to files and folders, turned up negative.

Checked the code behind the program - nothing has changed there either.

The specific error message I'm getting is this:

Error 7 occurred at NI_LVConfig.lvlib:Load.vi

Possible reason:

(fairly lengthy to type - but there is a directory to a .ini file listed here)

Complete call chain:

NI_LVConfig.lvlib:Load.vi

NI_LVConfig.lvlib:Open Config Data.vi

SharedFile.lvclass:ReadEntry.vi

SharedFile.lvclass:CheckControlSW.vi

Some further digging and the report generating toolkit is included as described in this link: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019O6PSAU

Any assistance? Fairly rusty with Labview so any help is much appreciated.

[altenbach]

Since the identical code was running before, there is probably something wrong on the deployed computer.

---

@mbocchinfuso wrote:

Possible reason:

(fairly lengthy to type - but there is a directory to a .ini file listed here)

.

---

Is that .ini file there and does it contain reasonable words?

Does the program have permission to access this location? (try to run the app "right-click...run as administrator" to see if something changes).

Is the path very, very long?

Also check the drive for errors.

[Bob_Schor]

Error 7 is "File not Found".  LVConfig appears to be the set of VIs that NI uses to read "Configuration" (a.k.a. .ini) Files.  I'm guessing that your code expects to find a .ini file somewhere, but it's not there, hence you get a "File not Found" error, 7.

Bob Schor

[mbocchinfuso]

interestingly, I did a search and the file is in the location it should be in. tried Run as Admin - same problems as before. all file paths are correct.

it appears that this computer has been giving the operator sporadic problems for quite some time now after discussion with the operator.

after a little further investigation, it appears that something within Windows was corrupted recently. System Restore, Check Disk and other utilities are no longer functioning as they should.

will update once we find out more - either if the computer gets repaired or replaced.

[mbocchinfuso]

hello all - some updates.

computer had some issues which our MIS department fixed. there were some drive errors, among plenty of others, which are now fixed.

the test program ran fine on the first run after the computer was refreshed, but then went back to being uncooperative.

a little more detail: the .ini file which I had previously mentioned, is somehow being converted to a .cmd file at the beginning of the test program running. is this a Windows setting that may need to be resolved?