I keep getting error 1017 when building

[remywizard]

I am trying to compile an exe for my project and I keep getting this error.  The description is: " VI has been modified on disk since it was last loaded or saved"  Which is not very helpful, because I have saved everything and nothign has changed.  I have tried using the save all, and doing the cntrl + shift and clicking on the arrow, and resaving everything but I keep getting this error.

Also, the error always seems to occur on one of my shared variables.  The variable is variant and is type - single-process.  Is there somethign with shared variables that you have to do in order to comile?

Thanks.

[Caseyw]

Off hand, I am not sure exactly what is causing this error when building your EXE. It would help if you could provide some additional information on exactly what you are doing when the error occurs, and on the error message itself. Does the error occur when you click on the "Build" button? Would you be able to attach a screenshot of the error message?

You also mentioned that this issue may be related to shared variables; is there information about a specific shared variable that appears in the error message you are receiving? I am sure that we can work together to determine what is going on here.

Regards,

Casey Weltzin
Applications Engineer

National Instruments

[AdDekkers]

Hello,

I have the same problem with my labview8.21 .exe build!

I also have a shared variable in the build.

After pressing "build" the code of the shared variable is recompiled and i get the "error 1017".

Regards,

Ad Dekkers

[remywizard]

I can not duplicate what happens right now, because I created a work around.  I just took out the shared variable that it gave the error on, and it is working fine.  If I can create the error again I will make a screen shot.

But the error was: "Compilation failed see details"  and the details said "Shared Variables_Params.vi has been modified on disk"  and I have tried saiving it and savign the project but nothing seems to work.  And the variable is aa single-process variant.

What I am doing when it occurs is I right click on my build exe task in the project and click on build, and it starts building and once it gets to that variable it stops and gives me that error message.

Thanks,

[Caseyw]

Thank you for your posts; I am definitely going to see if I can figure out what is going on here. I have a question for AdDekkers; what type is your shared variable (that seems to be causing the build issue)?

I will try to build an EXE from a VI containing a shared variable (of different types for now), and see if the error occurs on my end. Does every VI that you try to build (containing shared variables) give the same error? Are you using other shared variables in your application that do not give the error?

Regards,

Casey Weltzin
Applications Engineer
National Instruments

[remywizard]

I tried creating a separate app that uses shared variables and I couldn't get the error to repeat.  I also had the error occur on a shared variable that was a double I believe.

The error does not occur on any other VI except for the shared variable vi.  I also had other shared variables in my app that didn't throw the error.

I will keep tryign to get the error to occur again.

[AdDekkers]

Hello Casey, The shared variable is a cluster with 3 clusters in it with a enum typedef + 2 double's. I am also taking out this shared variables to be able to go on ! Regards, Ad Dekkers

[Caseyw]

Since neither of you can seem to reproduce the issue when creating a new VI, would you be able to send me your problem code (stripped down as much as possible)? If I can reproduce the problem on my end, then I can notify our R&D team and hopefully fix the issue in a future version of LabVIEW.

I would also appreciate it if you could let me know if you are ever able to reproduce the build issue consistently. Coming up with a simple example showcasing the problem would definitely help me to diagnose what is going on, and move forward with resolving the issue from there.

Regards,

Casey Weltzin

Applications Engineer

National Instruments

[AdDekkers]

Hereby an example with the error.

Regards,

Ad Dekkers

[Caseyw]

Thank you for the very helpful example. I have been able to reproduce the problem, and I have forwarded your code to our R&D team for investigation. I will keep you posted as soon as I hear back, and hopefully we will see this issue fixed in a future version of LabVIEW!

Regards,

Casey Weltzin
Applications Engineer
National Instruments