"file not found" error in VI Logger when running an imported VI Logger task

Question

I'm having trouble getting all of my imported tasks to run in VI Logger.
I'm using VI Logger 2.0, with an SCXI-1100.  The data acquisition tasks I import run fine.  One of the VI Logger tasks I've imported runs OK, but the other one gives an error:
"Engine Error!
Error Code = 7
LabView: File not found.  The file may have been moved or deleted, or the file path might be incorrectly formatted for the OS."
If I create a new VI Logger task, the new task works OK.  And my 1st VI Logger task to be imported works OK.  So I know my setup mostly works.  But our company has never been able to figure out importing tasks very well, so I'm looking for help.
Question 1: What file is LabView looking for?  I've checked my Export path and database path, and they are identical in both the working task and the non-working task.
Question 2: Where else might I look for the difference between the 2 VI Logger tasks?  Neither task uses any weird characters in the name, both have analog input channels and calculated channels.  And I've mixed and matched the data acquisition tasks with no change (the good VI Logger task will run with either data task, the bad VI Logger task won't run with either data task), so I'm pretty sure the problem is in the VI Logger task, and not the data task.  I've also tried importing the 2nd task on its own, as a separate import function, but that gave the same error.
Thanks for the help in advance,
Jake

Answer 1

Hi Spex,
I can import the VI Logger task OK (from another PC running VI Logger 2.0), but I can't run the task.  I've attached the file.  The "1 channel" task runs OK.  The "x-probe" task starts, takes 1 or 2 data points, then hangs for a few seconds, then pops up the "file not found" error. The data acquisition taks run OK, so I don't think they're the problem.
This file I've attached includes 2 good data tasks ("1 channel" and xprobe"), 1 good VI Logger task ("1 channel"), and my non-working VI Logger task ("x-probe", which works fine on the PC it was exported from).
I have also tried exporting the non-working VI Logger task on its own, and it still imports OK, but still doesn't run, and gives the same error.
Thanks,
Jake
Attachments:
configData1.zip ‏353 KB