LabVIEW 2017 Build error #1 - The icon could not be written to the application???

[nelg87]

I've been a LabVIEW user for over 10 years from version 8.2 on.  I recently installed LV2017 and boy!, am I dissapointed on the many compatibility issues it's shown thus far!! 😞  I can't seem to build ANYTHING in LabVIEW 2017 since installation and what's worst it also broke my LabVIEW 2013 where I can't any longer build with that either.  The current error I'm getting right now it's when I attempt to do a simple exe build.  It's giving me the following error:

The icon at C:\Program Files\National Instruments\LabVIEW 2017\appLibs\lvapp.ico could not be written to the application. Verify the icon is at the expected location. If using the default icon, please contact National Instruments technical support with this information.

C:\Program Files\National Instruments\LabVIEW 2017\appLibs\lvapp.ico

I'm using the default NI icon.  I tried using my own icon and get the same error.  This shouldn't be this hard.  Does anyone know why I'm getting this error and how to solve it?

Thanks! 

[aeastet]

I got this issues once when I was using a non default Icon. I did not have it in the project file when I when to build the application. I figured that giving the location when I added the custom Icon was enough, but I ultimately had to add the icon file to my project to get it to build.

[MichaelB123]

Hi nelg87,

I am sorry to hear that you are having a frustrating experience with LabVIEW 2017. I know it is never fun to encounter errors which hinder progression.

This issue is likely related to the location of your application build folders. Try the following steps:

• Make sure the build location of your program is not open in Windows Explorer
• Don't reuse the same build folder for multiple versions of the same application. If you need to update and re-build a project, use a new folder name.
  • This can be done using Version Tags to automatically append a version number to the folder name.
• If you aren't using version tags, un-check Auto Increment Version Number in the Version Information tab of the Application Builder

If you are still having issues I would recommend opening up a service request with our support team. We want to do our best to alleviate any frustration by helping troubleshoot your issues with our products.

Michael B.

Applications Engineer

National Instruments 

[nelg87]

Is the "Version Tags" a feature of LabVIEW?  How do you set it up?  Or are you just saying to change the name of my build folder with the current version?  Because I already do that.

[MichaelB123]

I was referring to putting a tag next to the Build Specification Name as described in this article: http://ae.natinst.com/public.nsf/webPreview/617928B8E8DE3B6C86257CC400429194?OpenDocument

However, changing the name should have the same effect.

If these steps are still not fixing the issue, then you should open a service request in parallel to this forum post. This will provide the quickest resolution time.

Michael B.

Applications Engineer

National Instruments 

[MichaelB123]

I realized the link I provided in my last post, may now be broken. Here is the fixed link: http://digital.ni.com/public.nsf/allkb/617928B8E8DE3B6C86257CC400429194?OpenDocument

Michael B.

Applications Engineer

National Instruments 

[Blueside]

This is a very late response to this query and is an FYI.  I got this error message all of a sudden for project that built no problem just the week before.  So I went through what I had changed and the only thing I'd done was I added a silver style boolean button with a gear wheel icon on it that I wanted to use for a system settings option on my front panel.  I also played a little with the custom nature of the button (to no good effect) and even type def'd it - maybe not a good idea.

When I got around to the build I got the build Error #1 error message above but figured I'd see what happened if I swapped my new shiny silver boolean for a boolean of my own design  - not as fancy as the one with the icon but given the nature of the error message I figured I should go back a step....and rebuild

So far so good - it worked and I got the exe built (phew!). 

So be careful when you add certain types of 'fancy' buttons to your application and tinker with them.  And also of course when doing lots of editing even if its just a button change tweak - keep an uo to date backup and build the application frequently.  Isn't hindsight a great thing. Maybe I got lucky.