LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trouble compiling a project

Solved!
Go to solution

Hi,

 

today I upgraded from LV 2013 to 2015 SP1. Adterwards, I tried to compile several of our programs in our project.

The simpler program compiles fine without any problem, but the more complex program fails to compile. It tells me

 

----

Es ist ein Fehler aufgetreten. Weitere Informationen erhalten Sie über "Details".

(An error has occurred. Get further informations via "Details".)

 

Über den unten befindlichen Link gelangen Sie zur Support-Seite für den Application Builder. Nehmen Sie folgende Angaben zu Hilfe:
(Via the link below you can get to the support sitefor the Application Builder. Use these data:)


Fehler 1055 bei Eigenschaftsknoten in VISL_findDependentVISvr.vi->VISL_findAndProcessVISvrList.vi->VISL_detectAndCopyVISvr.vi->AB_Engine_Copy_CustomIOServer_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller

Mögliche Ursachen:

LabVIEW:  Ungültige Objektreferenz.

 

(Possible reasons: LabVIEW: Invalid object reference.)

Now I fail to understand what could be wrong here – in LV 2013 it compiled fine, and I don't know which reference this information refers to.

 

The references in my code are fine (otherwise it wouldn't run), but rather I think that has to do with some references in the compiler code. But which ones?

Can anybody enlighten me (or at least tell me which information I need to provide)?

Thanks a lot in advance!

0 Kudos
Message 1 of 6
(3,632 Views)

Well, lets check the install first.  Open NI License manager, Expand LabVIEW 2015sp1, Expand Modules and see if there is a green or gold fill in the checkbox here

Capture.PNG


"Should be" isn't "Is" -Jay
Message 2 of 6
(3,627 Views)

Thank you for your answer. Yes, I have a dark green checkbox there, so the licensing supposedly is not the problem.

 

(Besides, I think if it was the problem, 1. the smaller/simpler program wouldn't have compiled as well, and 2. I would hoped to get a clearer message than this.)

0 Kudos
Message 3 of 6
(3,620 Views)

Did you change the LabView from 32-bit LabView to 64-Bit LabView  on your software update? I have found that not all 32-bit dlls made it to the 64-bit version. All so did you do a mass compile of you project files? 

0 Kudos
Message 4 of 6
(3,584 Views)

@Dave_Brandt wrote:

Did you change the LabView from 32-bit LabView to 64-Bit LabView  on your software update? I have found that not all 32-bit dlls made it to the 64-bit version.


Alas, that's not the reason as well. Currently, I am stuck to use the 32 bit version, as we use some proprietary DLLs which are only available under 32 bit, so we even cannot change.

 

All so did you do a mass compile of you project files? 

I did a mass compile, which didn't help as well.

0 Kudos
Message 5 of 6
(3,561 Views)
Solution
Accepted by topic author glglgl_de

I still haven't found out what's really the reason for this all, but I have found a solution:

 

Until now, I used LabView classes in my program, because I have used some humidity sensors which were accessed in different ways. Depending on which sensor was detected on program start, the one or other class was chosen and used throughout the program.

 

As we don't use two of the three sensor types any longer, I have changed the program to use the code for the third kind of sensor directly and throw the classes over board. That fixed the problem.

Thank you all for you effort to help!

0 Kudos
Message 6 of 6
(3,558 Views)