Build error

[Miha_Vitorovic]

In the build log just before the error is the last VI (yours) that LabVIEW was processing before this error occured. This isthe one that needs "fixing".

Br, Mike

[Alain_S · Accepted solution]

Titou's first idea was closest of all suggestions

I delete the 3 project files (MyProject.aliases, MyProject.lvlps and MyProject.lvproj) and create a new project with the same vi's, typedef's, .... ... all in the same folder.

No more errors while creating the EXE file 🙂

[SSRaza]

I have a Shared Variable published by a Shared Variable Engine on a remote node. I would like to diagrammatically access the alarm limits , of that Shared Variable. But using property node on remote machine i got this error. 1967362032. Can anybody tell me how to do this in better way

[Nico_support]

Hello SSRaza,

At the following link you can find more information about the error -1967362032:

http://digital.ni.com/public.nsf/allkb/96C5B8A73F624996862576CF00611A41?OpenDocument

"Shared variable alarm properties are only accessible from the PC hosting the shared variable. There is, however, a workaround. It is possible to view and read properties using a DataSocket Read or DataSocket Write VI"

At the following link you can find more information about DataSocket: http://digital.ni.com/public.nsf/allkb/8D2FE9AC6ACB8B3F862571B0007FAECA?OpenDocument

Also on our website ni.com, there is extra information when you search on DataSocket

Kind regards,

Nico Lammens

NIBE AE

[Vladiator]

Unfortunately it did not help me with the same error. Any other ideas?

[Vladiator]

---

@Nico_support wrote:

At the following link you can find more information about DataSocket: http://digital.ni.com/public.nsf/allkb/8D2FE9AC6ACB8B3F862571B0007FAECA?OpenDocument

---

Getting Error vieweing the document: "You are not authorized to view this document"

[ThiCop]

Hello Vladiator,

Which type of error are you getting?

What does your code look like?

[RN888]

Thanks 🙂

Turning on the build log identifies the file causing Error 56003.

Otherwise you are working in the dark

[richardscheff]

This may or may not help anybody.  I had a SFVA Sound and Vibration Analysis Toolkit that would cause a build error.  I had tried mass compile and repairing the toolkit.  Neither worked.

I had built multiple versions revisions of software, and suddenly it stopped working.

I decided to run the offending vi.  And the error being thrown matched a similar error I would get with an empty array.  So I changed the default control array from empty to having a single element.  Then the software compiled without a problem.

I am not sure if changing the array made the difference or just changing the file and saving it again.  Again recompiling it and saving it did not fix the problem.

[B_Strange]

I had a similar issue. Turns out my project was referencing some vis that were not on disk. Even though they had no callers, the build would not execute and the error message was maddeningly vague. Only once I opened the build spec, changed something and then tried to save it did I receive a notification that some referenced vis were missing.

After deleting them, the build worked fine!