Components
Replication and Deployment Utility (RAD)
I'm somewhat perplexed as to why your create image call doesn't show up in I/O trace. I'm wondering if it could be erroring out before it makes it to the actual tracing code. Looking back through the RAD source code the only other problem I could think of is if LabVIEW is having any problems creating the temporary folder that the image is initially created in before it moves the image to your specified image folder.
If you look at the source you will find a call to Generate Tempory File Path.vi. I noticed this VI didn't have the error cluster, so in theory if LabVIEW failes to create a temp folder you won't see an error popup until create image tries to use that path. You may want to try and wire the error cluster to this VI and see if it is failing or run Generate Temporty File Path.vi on its own to see it works or not.
See JoshuaP you made the same misstake we/I did too. That VI does not "create" anything, and the way it is constructed it will loop UNTIL you get an error out (which is used to indicate that a new unique path has been generated). As far as I can tell, every other part of RAD assumes that the path out from this VI is VALID (e.g. folders exist etc.) but they don't because they are never created.
Once properly wiring the error terminal in Generate Temporary File Path.vi, it errors out on first call which happens as shown in your screenshot above, in the "Init - Configure Settings" case.
Error 7, when trying to create an "appdata\local\temp\ folder.
I must admit I am confused as to the purpose of the "Generate Temporary File Path.vi" and the way it is used later in RAD. The name implies it generates temporary FILE paths, but the way that path is used in RAD is as a FOLDER path, and the users are not taking steps to ensure the folder tree/path actually exists, which it doesn't since the vi is creating a file path..
A tad better would be if the Generate temporary file path made sure that the path up to the intended file-name existed and maybe a conditional input to make it generate temporary file OR folder path and again making sure the path output is actually "generated" or valid. I also noticed that instead of using the existing NI Library function to make sure the string is a valid file-name string, they did a limited reg-ex, and they did this on the VI input string inside the whileloop. This expression only needs to run once.. I replaced it with a wrapped version of the vi.lib\Utility\libraryn.llb\Is Name Multiplatform.vi and I attached the wrapper to this message. Whats REALLY interesting is that this Generate Temproary File Path.vi IS A MEMBER of that SAME library!! I find that sort of ironic.
My modified version of the generate temporary file path is attached... Not sure if someone could mark that VI in the libraryn.llb for review to at least move the string check outside the while-loop and maybe even replace the reg-ex with a call to the "is name multiplatform.vi" from same library?
Note when running this debug session I used an sbRIO-9606 that I had on hand as my usual 9014 was unavailable.
This is the point of error and all pertinent input information:
rad_retrieve image wrapper.vi calls "Create System Image.vi" which then throws error -2147467259 but with no error in io-trace.
The temporary folder Temp\lvtemporary_174026.rad exist and also contains the (empty) folder "imageDir" and lvappimage.info (see contents of this file below).
The target settings and AppImage Properties are (partially) shown in screen-shot:
The IO trace is still not containing the expected command, probably because the locked NI VI is erroring out prior to that point but I attach it still, just in case.
[RTAD Info]
RTAD_Version = "5.5.2"
[Application Image]
Name = "test 7"
Version = "1.0.0"
Description = ""
Key = "{2FC5D7BD-5ABD-7BE1-B3CF-1EB5581C8A98}"
Model = "sbRIO-9606"
Chassis = "Not Available"
Time = "02/10/2014 11:57:03 AM"
Retrieve = ""
Deploy = ""
InstalledSoftware = ""
NumBitFiles = 0
