LabVIEW
Executable 2501 Error
Are you sure it is erro 2501 and not -2501? Because the negative makes a difference and that error is related to an invalid TDMS file reference. What kind of error handling are you doing? I'm guessing a path isn't right and it becomes invalid, but your code tries to use it and generates more errors related to not having a valid reference. You can try to debug your application using some debugging techniques that show you the block diagram of a VI inside an EXE. This allows you to probe and find where the error is coming from and why.
http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/debug_apps_dlls/
Other than that you are going to need to attach some code showing what you are doing. I'd me most interested in any part of the code relating to path manipulation.
EDIT: Oh sorry I didn't see the posted code. Does the log file get created properly? Is there a write permission issue with where the log is going to be written to? Do you know what function generates the error?
What good do you think the shift register will do for you? The path that the Application Directory returns doesn't change inside the while loop. Not sure if you read the help but it has this to say.
If you call this VI from a stand-alone application, this VI returns the path to the folder containing the stand-alone application.
If you call this VI from the development environment and the VI is loaded in a LabVIEW project file (.lvproj), this VI returns the path to the folder containing the project file. If the project is not saved, this VI returns <Not a Path>.
If the top-level VI is not loaded in a project, the VI returns the path to the directory containing the top level VI. If the VI is not saved to disk, this VI returns <Not a Path>.
With this information I'd say you are using it correctly. BTW you never mentioned if the file is actually being created or not. If it is not I'd suggest just temporarily replacing that function with a path to a folder you know you can write to like C:\Temp and see if the files get created there.
Also I noticed that if there is an error with your TDMS open, or the List contents, then you won't know it, since that Error Out is unwired, it should be wired to the input of the Get Properties (or remove all of this since all you are doing is getting the properties but then doing nothing with it). If there is an error with opening the file this will tell you, if there is an error with writing the file, I am unsure where that would be seen other than the file isn't created.
If I drive my car to work and I didn't get into an accident, that isn't reason to not wear a seat belt. Similarly if I don't get an error when I run my code one way, it doesn't mean error handling isn't important, it just means I didn't get into an accident yet.
