LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW error 44 and corrupting programs

I have some fairly complex code that I have written that does Bit Error Rate testing using multiple launches of asyncronous writers and readers, and communicaitons through queues.  It has been running on multiple machines for months and I built a new machine, installed LV2013 with all the updates, just like the other machines and now it is corrupting VI files.  I am running from a shared drive on our corporate network, just as in the previous months.  I can open a file on the remote server and run it.  I make a minor edit and resave.  This may work multiple times and then all of the sudden I get a message that I don't have permissions to save an intermediate file.  Even though it says it hasn't saved the file, if I exit without saving, it corrupts the file and it is no longer accessable as a vi.  It makes a comment about the help file.  I am not in front of the machine at the moment, but I will post up screen shots of the dialog boxes. 

 

I can take a copy of the original vi and run/modify it all day long on other machines with no problems.  From what I can see, along with my IT department, the machines have the exact same permissions and are on the same subnet.

 

What is wierd is that I can modify and save it one or more times, and then it craps out.

 

I am going to reinstall LV2013 for the 5th time, this time from the disks instead of from a National's server.

 

Anybody have any ideas?  At first I thought the file/path was too long, but I stripped it back and no change.  Where does LV2013 store intermediate/working files?

0 Kudos
Message 1 of 34
(5,052 Views)

I get an error  Can't load Help Information of "BERT Launch.vi"

 

the code is 13.02f (32 bit) and has all the updates.

 

The op system is Windows 10 on all the machines.

 

When I try to load I get:

 

LabVIEW:  Failed to load dynamic library because of missing external symbols or dependencies, or because of an invalid file format.  The file 'BERT Launcher.vi could not be loaded.

0 Kudos
Message 2 of 34
(5,044 Views)

Are the directories of the files located in a network drive? Try move them to another drive.
Also have you tried running the VI as an administrator? It could be because of some permissions.
What you did different with this machine that you didn't do in the others?

0 Kudos
Message 3 of 34
(4,980 Views)

Yes the files are on a networked drive.  With all the machines, they all accessed them from the same place.  All the machines I believe are set up the same.  I am however going to delete all the NI stuff and reload off the original disks and bring them up from there.

 

The biggest difference in the machines is that this machine is a Dell quad xeon machine with 16gb of ram and a local raid setup.  All the machines are running Windows 10 professional and are current on their updates.  I am the logged in user on all the machines and have local admin rights on all of them. 

 

This ain't my first rodeo 😉  I have been using LabVIEW for almost 20 years on close to a hundred different networks for dozens of companies and have never seen anything like this.  My thought is that somehow this install is putting temp files somewhere that is causing problems.  The funny thing is that it corrupts the files.

 

While the main program(s) I have seen the problem on are large and complex, I am also seeing the same problem on a fairly basic piece of code I wrote for a relay controller.

 

Why does it work for a few times, then corrupt the file?  I ran a full diagnostic on the machine, including an exhaustive memory test.  I even looked into the event logs and did not see anything out of the ordinary.

0 Kudos
Message 4 of 34
(4,977 Views)

Try running the code on a physical drive instead of a network drive. Do you still get that error? 

Also you could try to remaking the VI from the scratch. 

0 Kudos
Message 5 of 34
(4,951 Views)
The solution is to not work directly from a network drive. The correct way of handling this situation is to create a source code repository on the shared drive (SVN works really well) and then each user checks out a working copy to their local drive to use and work on.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 6 of 34
(4,936 Views)

@oldmanXJ wrote:

 

 

LabVIEW:  Failed to load dynamic library because of missing external symbols or dependencies, or because of an invalid file format.  The file 'BERT Launcher.vi could not be loaded.


Just to make sure: are you using any shared libraries (DLLs) in that VI?

Rolf Kalbermatter
My Blog
0 Kudos
Message 7 of 34
(4,929 Views)

What OS are you using? It might not be a problem with LabVIEW 2013 in particular, but it depends on which OS you're using.

Jorr-El
Systems Engineer
Testeract: Automated Test Specialists
0 Kudos
Message 8 of 34
(4,893 Views)

Ok, once again...all the systems, both the ones that work and the one that doesn't work are running Windows10 professional, fully patched and up to date.  All are running LabVIEW 2013, fully patched and up to date.  See previous post for more info.  They are running from the same network drive.

 

I have removed LabVIEW multiple times and reloaded from the NI server.

 

Friday AM, I removed LabVIEW again and this time I loaded it from the distribution DVD's.  I have not had a chance to see if that helps.

 

 

0 Kudos
Message 9 of 34
(4,889 Views)

Ok. Thanks for the reply. 

 

This is a known issue in LabVIEW, and there has been a Corrective Action Request (CAR) filed to fix it. LabVIEW has been having a conflict when saving VIs on network drives with Windows 10 machines. The current workaround is to just use the Save As function or to save the files locally.

While this is less efficient, it is currently the best way to get around this issue. The CAR number is 597858, and will be listed in the bug fixes in the LabVIEW update it is a part of.

Jorr-El
Systems Engineer
Testeract: Automated Test Specialists
0 Kudos
Message 10 of 34
(4,883 Views)