Dear Community
We are using Labview since Version 7 and are always building applications using the application builder and then build installers.
We often have had problems with the application builder but these where all possible to solve up to know.
As you can imagine our projects has also been grown so now it is relatively big with a lot of netwok shared variables (approx 100) and corresponding typedefs.
So currently the status is even not describeable as it is so wide spread.
On one hand it is not possoble to build the application because every time the error 1502 is coming up.
I already did the recommendations of the knowledge base article.
http://digital.ni.com/public.nsf/allkb/8683D4C66F5CA50E86257341007CF34D
So this is one problem.
The other one is especially on windows 32 bit and LV2015 32bit where the build application says it could not open a control because it was made with LV2014 , so a newer LV version namely 2015SP1 is in the runtime not able to open a vi or ctl which is 100% LV2015sp1 and says it is 2014 and could not be opened.
This is only the case in 32bit runtime engine.
This is also in a support loop of NI but it seems either they know something is fundamentally wrong on the 2015SP1 "f1 and f2" or they don't want to solve the problem of their up to know NI happy customer.
I know this is a confusing thread. If we use the code where the runtime engine says it could not be opened and press canel everything is working fine. The problem is in this buld application there are about 20 vi's or controls to be canceled during startup till the application is working.NOT ANY SOFTWARE USER LIKES THIS WAY TO START HIS APPLICATION.
Finally I attach some error messages which came up till these problems are here.
I also want to mention that these problems are not limited to a single Computer so it is not the typical (Windows is corrupt driver is wrong and so aon story)
Thank you for some comments
Best regards
Gernot