LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

CVI 2013 executable does not exist?

Ocassionally, I get teh following error on some (not all) of my CVI 2013 projects:

 

"the specified executable does not exist"  See the attachment.  If I simply make the project again (or again), the error eventually resolves itself.  Any ideas?

 

 

0 Kudos
Message 1 of 22
(5,981 Views)

Greetings.

 

When you say that you make the project again, are you talking about recompiling/rebuilding?

 

Regards,

 

Brandon V.

Applications Engineer

National Instruments 

0 Kudos
Message 2 of 22
(5,937 Views)

Sorry, yes that's what I meant.  I simply CTRL+M or enter Debug repeatedly and the problem goes away.

 

 

0 Kudos
Message 3 of 22
(5,922 Views)

When does the error get thrown? Also, is your data being stored locally or on some sort of network location?

0 Kudos
Message 4 of 22
(5,902 Views)

Hi ElectroLund,

 

Are your project files on a network location? If you get this error in the future, can you check whether a built executable exists in project folder? 

 

Thanks,

Daniel

Daniel Dorroh
National Instruments
0 Kudos
Message 5 of 22
(5,901 Views)

Thanks guys,

 

So I am working locally.  I check out my project to a local folder from our SVN.

 

The error first is thrown when I click the Debug green icon.  I simply click it again and usually by the second time it builds correctly.

 

For what it's worth, I don't believe I ever saw this in CVI 2012.  I'm only now seeing it with 2013.

0 Kudos
Message 6 of 22
(5,897 Views)

Does this only happen right after you check out your project?


Thanks,
Daniel

Daniel Dorroh
National Instruments
0 Kudos
Message 7 of 22
(5,893 Views)

Hmm, that's an interesting thought.  I'll pay closer attention, but I don't believe it's that predictable.  It seems to be relatively random.

0 Kudos
Message 8 of 22
(5,890 Views)

Ok, after working a few hours on a checked-out project, I can confirm that in about 2 dozen build/debug cycles in a 2 hour period, I had this error one time out of the blue.  It wasn't on a fresh checkout, just right in the middle of my developing.

0 Kudos
Message 9 of 22
(5,884 Views)

Hi, all,

 

I'm facing this same problem (but very rarely) - and I suppose this is and I suspect that it is associated to multicore processor configuration of local machine.

Changing from dual-core (HP 8530p) to new DELL Vostro 3560, i7-3612QM @ 2,1 GHz I encounter this and also another weird behaviour (e.g.).

Have no idea to overcome this.

 

George

0 Kudos
Message 10 of 22
(5,869 Views)