Why do I sometimes get a ”failed to deploy” error message when downloading an executable on a CRIO?

[Terje]

Sometimes, when I try to download my executable, I get a “failed to deploy” error message. (See attached image) Why is that? Doesn’t the deploy action only copy files to the CRIO? How can that fail?

Terje

[JackLF]

Could you post the contents of the deploy status window? (You should be able to select and copy the text.) 
Also, what version of LabVIEW are you seeing this?

Message Edited by JackLF on 12-11-2007 07:26 AM

[Terje]

Hi Jack and thank you for your reply

The contents of the deploy window is as follows:

Deploying RT CompactRIO Target  (successfully deployed target settings)

Deploying NI_Variable_RT.lvlib 

Deploying RR lib.lvlib 

Deploying RR lib.lvlib:Number of Samples 

Deploying RR lib.lvlib:Data 

Deploying RR lib.lvlib:Sampling 

Deploying RR lib.lvlib:Sampling rate 

Deploying RR lib.lvlib:DAQ Error 

Deploying RR lib.lvlib:Number of samples pr buffer 

Deploying RRTarget (failed to deploy)

Download completed with errors.

I use LabVIEW 8.5

Terje

[JackLF]

Just to clarify -- "RRTarget" is the name of your application?  What kind of things are in your application's Build Specification?  Does it fail everytime or at random?  What type of RT target are you using?

For the most part, you are correct -- it's just going to transfer the files and deploy any dependencies (such as variables).  The two things I can think of off-hand that might cause this scenario are that LabVIEW was unable to find a DLL needed by the application in order to deploy it with the app or for some reason (though this would be unlikely) it was unable to close any remaining references to an existing startup application on the RT target.  Most things that can go wrong should give you a conflict to resolve before it gets this far.

[Terje]

Hi,

Yes, RRTarget is the name of my application and my target is a CRIO-9002.

The error is not random. In a certain setup of my application the error occurs, but I have not yet been able to pinpoint what components in whet setup that makes the error occur.

When I press the run arrow, the application works just fine. When I build the executable, I get no errors, but when I deploy the application, the error occurs.

In the build specification I have only selected my top level VI and the rest is the default settings.

I tried to deselect the “Enable debugging” in my build specification and then the application was deployed without any problems!!

Any ideas?

[JackLF]

Interesting.  I'm not aware of anything that disabling Allow Debugging would impact, though I will double check.  Nothing else changed between the two builds?  That setting should just change how LabVIEW compiles the VIs that are in the application (so they will include remote debug panels, etc).  So long as the build succeeds, I don't believe it should care how it was built in order to do deployment.

Another clarification: was this project upgraded from a previous version or created from scratch in 8.5? 

One other thing you might try is to "clean" the build spec output and force it to rebuild completely.  Right click on your startup application's build spec and select "Explore".  You should see the output folder where the app is stored (most likely just a "depinstr.bin" file and a "c" folder that contains all the deployable files).  You can delete or rename the files, then go back to LabVIEW and Build the app again.