Error 1 when building my application in Labview 2010 Version 10.0f2

I am getting the following error trying to build my application in Labview 2010 Version 10.0f2 and I get the following error:
Error 1 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Method Name: Linker:Write Info To File
I have searched and can find no real sollutions to this problem. I did the updates and still nothing. Now I can't even build an app with Laview 8.6. I reference several .NET items and refuse to rebuild each and every one of them. My only option at this point is to uninstall all Labview and then reinstall 8.6 so I can do something.
Help if you can.

Hello RBrown
I am really sorry for this inconvenience! This is a known issue.
Can you please attempt the following for me:
When you are building an application, under Advanced please check the last box "Use LabVIEW 8.x file layout"
If that doesn't work, you may need to rebuild the LLB in a separate directory with new names, and use it as the build inclusion.
Here are some forum posts strictly for your information:
I have found users that have had similar issues. I am trying to make this workaround work for you.
http://forums.ni.com/t5/LabVIEW/error-1052/m-p/912192
This is a known issue that some customers have already commented on:
http://forums.ni.com/t5/LabVIEW/NI-Please-don-t-put-illegal-vi-names-in-your-toolkits-thanks/m-p/745...
I have filed a corrective action for this issue and I will add you to the list of individuals who need this issue resolved.
Sincerely,
Greg S.

Similar Messages

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

Error message when building an application for Labview PDA

When using LabView PDA module to build an application for a PDA target, I receive the following message: "Error building executable. Unable to create file". Why is this happening?
When looking at the error log, it reads "The system cannot find the file specified."
This happens even when looking at one of the Labview PDA example VI's, so it is not a result of the VI containing functions of features not supported by Labview PDA.
When installing Labview PDA, I installed files as follows, and in this order:
(i) Labview 7.1 (installed previously)
(ii) Microsoft eMbedded Visual C++ 4.0
(iii) Microsoft eMbedded Visual C++ 4.0 SP 3.0
(iv) Microsoft SDK for Windows Mobile 2003-based Pocket PCs
(v) Microsoft ActiveSync 3.8
(vi) NI Labview 7.1 PDA module for PocketPC
(vii) DAQmx Base 1.0 for PDA or later
Any ideas?

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Error when startup WPF Application with Crystal Report !

Hi!
I have an error when build & run a WPF Application with Crystal Report. Can anyone help me ?
First, I created 2 project, one is the WPF Application & one is Shell Start Up project (to show loading screen, then show main window when loaded, is WPF Application too)
WPF Application:
/// <summary>
    /// Interaction logic for MainWindow.xaml
    /// </summary>
    public partial class MainWindow : Window {
        public MainWindow() {
            InitializeComponent();
           // crViewer is SAPBusinessObjects.WPF.Viewer.CrystalReportsViewer
            crViewer.ViewerCore.ReportSource = new CrystalReport1(); // Assign report to viewer
Shell Startup:
[STAThread]
        public static void Main(string[] args) {
            AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);
            Application app = new Application();
            ShowLoadingWindow(); // Show loading screen
            MainWindow mw = new MainWindow();
            mw.Show();
            app.Run();
        static void CurrentDomain_UnhandledException(object sender, UnhandledExceptionEventArgs e) {
            // Exception was throw here
And here is the exception & it's stack trace
Message: Object reference not set to an instance of an object.
Stacktrace:
at SAPBusinessObjects.WPF.Viewer.ViewerCore.<>c__DisplayClass1.<set_ReportSource>b__0()
   at SAPBusinessObjects.WPF.Viewer.DelegateMarshaler.<>c__DisplayClass29.<QueueOnThreadPoolThread>b__28(Object )
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

As far as I know the error is typically due to the fact that I'm trying to address an object that has not been set. E.g.; this could be due to bad scoping, bad inits/constructs, trying to access a member of a class without instance object and so on. I suspect this is a design \ code issue. You might be able to confirm this using [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx].
Other than that, I'd recommend creating a phone case here:
http://store.businessobjects.com/store/bobjamer/en_US/pd/productID.98078100?resid=S6I@hgoHAkEAAGsiyVkAAAAR&rests=1282226845369
- Ludek

When building an application unit tests are added to a support directory

Why are unit tests (.lvtest files) added to a support directory when building an application? I cannot find a way to exclude them from the support directory.

I'd imagine this is happening to you because they are in the "Dependencies" section of your project file (*.lvproj). Is this correct?
If so, you should add them to your project file somewhere. Then you will be able to prevent them from being installed. In my experience LabVIEW grabs files it thinks are nesecary from the Dependencies list and installs them in a support directory.

Get_Block Error when installing an application

Hi all,
I tried to recover a backup I had made some days ago, and I got the following error when installing the application:
Error GET_BLOCK Error.
ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 34, column 68: PLS-00103: Encountered the symbol &quot;&amp;&quot; when expecting one of the following: ) , * &amp; = - + &lt; / &gt; at in is mod remainder not rem &lt;an exponent (**)&gt; &lt;&gt; or != or ~= &gt;= &lt;= &lt;&gt; and or like like2 like4 likec between || multiset member submultiset <pre> &lt;br&gt;begin &lt;
I looked in the .sql application and searched for the "&quot;" or even for the symbols &" and I found nothing. I checked the character set and it seems right, the application is in UNICODE-UTF8 and the database is in UTF8 as well. I'm working with APEX version 4.1.1 and apex listener 1.1.
Has anyone got this error before, or does anyone have a tip on where to investigate?
Thanks in advance.
Elena.

For those who have gotten this error as well..
The problem was in the buttons Expand /Collapse that I had in some trees. I had them with a redirect url pointing to a javascript code like this:
javascript.apex.widget.tree.expand_all('id');I changed these buttons, I set an action "Defined by a Dynamic Action". This DA is called when the button is clicked and executes this javascript code:
apex.widget.tree.expand_all('id');Now it works. Hope it can help someone.
Elena.

Error When building ess/tra/tre and ess/tra/tre/trs DC's

I had customized the ess/tra/tre and ess/tra/tre/trs DC's and had them working, but I do not know what I did or what happened that am now getting the following errors when building, can anyone help tell what the problem could be?
Error
-     The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel. Fix the classpath then try rebuilding this project.
-     HDI_HNS15.02_Desstratresap.com
Error
-     This compilation unit indirectly references the missing type com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel (typically some required class file is referencing a type outside the classpath)
-      InternalVcTreReview.java
-      HDI_HNS15.02_Desstratresap.com/gen_wdp/packages/com/sap/xss/tra/tre/vc/review/wdp
-     line 0

For anyone who might need to know, I managed to fix this by adding tra to the required projects on the build path. On the Navigator View, right click -> Properties -> Java Build Path -> Projects tab -> check dependant project.

Icon path restricted error when building release version for ipad3

Hi,
i get the following error when building the release build ipa file for ipad 3: "The path icon.png is restricted. If you were trying to package Icon.png you should correct the case." In debug mode everything works. My icon is under assets folder and added in the app-xml with:
<icon>
<image72x72>assets/icon_72.png</image72x72>
</icon>
Did I missed something in configuration? Seems to be that the problem is known but cant find a solution for it. If i try to packegae per command line despite the fact building works I could not install the app. When I change the icon tag to use no icon everything works fine. Any ideas?
Greetz and thanks in advance!

I solved it. When you export the release build you can choose package contents to be compiled in the ipa. When I tried to add an icon at first I named it icon.png, which seems to be a reserved name. The configuration to include this icon.png was still saved though i deleted it. Wired... After unchecking the ceckbox for icon.png not to be compiled in the ipa, the release build was build.

Wdapi900.dll error on windows 7 while running labview 2010 executible

Hello All,
I am trying to run a "1.exe" on a windows 7 PC created from a Labview 2010 version.
It gives me a following error
"The Program cant start because WDAPI900.DLL is missing from your computer"
However the previous version of labview 2009 "2.exe" file works absolutely fine on the same Windows 7.
I tried running the Labview 2010 "1.exe" file on Windows Vista and it runs absolutely fine.
Any ideas?

I created another .exe file from LV 2010 and ran it on win7 PC.
It ran perfectly fine.
The difference between this file was, i was just using a serial port for communication.
On the other program i was using a winI2c interface along with options to choose from NI 8451 and serial interface.
The error messages i am getting are as attched.
Error 1 is the 1st message i get as soon as u open the program.
After pressing OK, i get a bunch of other error messages as shown in Error2.
I have already installed latest Win-I2CUSB on win 7 machine.
Attachments:
error.jpg ‏30 KB
error2.jpg ‏14 KB

HT1926 I am getting an R6034 error when I attempt to download the latest version of iTunes. What does this mean?

I am getting an R6034 error when I attempt to download the latest version of iTunes. What does this mean?

Click here and follow the instructions. You may need to completely remove and reinstall iTunes and all related components, or run the process multiple times; this won't normally affect its library, but that should be backed up anyway.
(99885)

I'am getting an update error when am trying to upgrade to newer version (4.3.2)..the error message content shows that i tunes could not back up the i pod,because the back up was corrupt or not compatible with ipod..can anyone help me out to fix this issue

I'am getting an update error when am trying to upgrade to newer version (4.3.2)..the error message content shows that i tunes could not back up the i pod,because the back up was corrupt or not compatible with ipod..can anyone help me out to fix this issue

Hi,
Try here: http://support.apple.com/kb/HT1808.
Hope this helps!
---likeabird---

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Any ideas?
Scientia est potentia!

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Error when building Installer with USI 1.5.0 with Labview 8.5

I used to build an installer with Labview 8.2 and included this additional installer USI 1.5.0 but now with labview 8.5 it gives me an error:
"Locate the "NI LabVIEW" distribution. LabVIEW needs to copy a component installed or updated by the distribuiton to conitnue building the installer"
Any advice

Hi reza_sed,
Thank you for contacting National Instruments. When you get this message, are you prompted for a location of this installer (CD drive or something)? Sometimes if components are installed together, certain dependencies are created. You might be able to add the installer to a LabVIEW 8.2 installer with no problem, but the installer cannot be found when using a different version of LabVIEW. You might try uninstalling USI, then copying the install files from the CD or from our website to your hard drive and then installing from there. Then, you should be able to include the additional installer.
Another thing that may be happening is that the LabVIEW Run-Time Engine you have for 8.5 does not support NI-USI. The full version of the Run-Time Engine supports NI-USI, but the web browser only version does not. Make sure you select the full version when installing.
Donovan

How to fix error 0x8ABC7004 in labview 8.5? i am also getting error while building my application? help

I AM FACING THIS ERROR CODE WHILE BUILDING MY APPLICATION IN AN EXECUTABLE.
The VI is broken. Open the VI in LabVIEW and fix the errors.
D:\JUICE EXTRACTION only ethernet\VI\Scada.vi
<Call Chain>Error 1003 occurred at AB_Application.lvclasspen_Top_Level_VIs.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Page_Preview.vi
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>>Open and verify that it is runnable.
my email id is [email protected]

hi ravenas,
thanks for the reply.
anyways, is it possible that whenever guest logins into the system, the windows page bounds configuration like front panel bounds in labview be fetched so that the same will be configured to the vi's front panel programatically.
by doing this the windows components will automatically get hide.
or is there any better solution.
reply
thanks
samriddh sarbalhi
[email protected]

Error 1 when building my application in Labview 2010 Version 10.0f2

Similar Messages

Maybe you are looking for