HELP! Error 8 occurred at TDMS Open

[TDL85]

Hi,

I have built 2 vis to run concurrently, 1 vi acquires data from hardware and saves it as a TDMS file on a network drive. The other reads the TDMS file, and displays a graph.

In the development environment, both vis run fine. When I build an executable, the read vi gets error 8. Somehow as an executable the vi lost file permissions but as a plain vi it is fine?!

If I relocate the code to another PC, the development vi and the executable both get error 8!

All PCs in this scenario have R/W access to the network drive. I'm using LabVIEW 2014.

Anyhelp would be great!! 

Thanks

[Hooovahh]

Try running as an administrator, or turning UAC down.  Do you have any firewall or anti-virus programs running?

[mikeporter]

Yes, to echo Brian, when ever I have seen this error it has been a directory permissions problem. Where specifically on the network drive are you trying to write the file? Is there anything special about the location?

Mike...

[TDL85]

Thanks for the suggestions. I'm still wrestling with this... I've tried running as administrator... same result. We do have some firewall, anti-virus programs running, due to IT policies I dont have any access to modify those things...

There's nothing special about the location of the network drive. It's just an easily accessible resource, available to everyone who needs to run the program.

[Hooovahh]

I've had anti-virus, firewall programs, and domain policies, cause many programs to not behave correctly.  From seeing graphical glitches on cameras, corrupted file transfer, remove desktop flackyness, file I/O errors, remote front panel failures, and DAQ errors.  I've seen many issues all attributed to IT policies put in place to protect us.  They have their job and I have mine, and when I waste days troubleshooting a feature I can't deliver due to their policies, I get cranky.

I'd do what you can to try to test this on a PC that is not domain controlled and see if the issue goes away.  It might not be related but I can't think of any other reason this would act like you are describing.