LabVIEW build Error 1 occured at NiFgen Configure Frequency.vi

Trying to rebuild the executable of a LV6.1 project, previously built on another computer (which crashed this week). Reinstalled development system on a replacement computer and now get this error message when I try to build. The application runs without problem in the development environment on the new computer.

It seems that the problem is limited to a single VI. Can you build the VI in another executable? On a long shot you might want to press control-shift-runarrow on the top level VI to perform a binary recompile of the code. Changes are you will see nothing happen.

Similar Messages

  • Another Compiler Bug (message: An internal build error has occurred... Unknown Flex Problem)

    I was fighting with this problem for a few days. Finally I've got it resolved. I want to describe it and fill in BUG in the bug report, but I am not sure about Adobe support options. So, I am putting bug report here.
    1. ASSUMPTION: All problems which compiler reports as unknown problem are the real compiler BUGs/Problems. Eventually MXML compiler/ActionScript compiler should be able to take C++ or FORTRAN code or an aribitrary text and nicely tell "Error: It is not ActionScript (Flex) code" or "the code is corrupted from Line so and so...". When compiler crashed, it is most probably due to one of the states not handled (or not handled correct). Keeping this in mind I assume, that my code has nothing to do with the compiler crash.
    2. PROBLEM Description.
         - I tried to port our internal project from Flex3.5/Flex Builder 3 to Flex4.1/Flash Builder 4.
         - After checking out and trying to build code I start getting weird problems like Error 1037: Packages cannot be nested.
         - After cleaning and compiling project by project, walking up dependency tree, I was able to get rid of this problem.
         - On last Project I've got another problem (An internal build error has occurred... Unknown Flex Problem). Which I stuck with for a while.
         - When I checked log file I found following messages:
    ============================================================
    !ENTRY com.adobe.flexbuilder.project 4 43 2010-12-21 15:45:24.353
    !MESSAGE Uncaught exception in compiler
    !STACK 0
    java.lang.ClassCastException: macromedia.asc.parser.InputBuffer cannot be cast to flex2.compiler.as3.CodeFragmentsInputBuffer
    at flex2.compiler.as3.AbstractSyntaxTreeUtil.lineNumberToPosition(AbstractSyntaxTreeUtil.jav a:1266)
    at flex2.compiler.mxml.ImplementationGenerator.generateBinding(ImplementationGenerator.java: 569)
    at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetupFunction(ImplementationG enerator.java:863)
    at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetup(ImplementationGenerator .java:812)
    at flex2.compiler.mxml.ImplementationGenerator.generateInitializerSupportDefs(Implementation Generator.java:1878)
    at flex2.compiler.mxml.ImplementationGenerator.generateClassDefinition(ImplementationGenerat or.java:1044)
    at flex2.compiler.mxml.ImplementationGenerator.<init>(ImplementationGenerator.java:206)
    at flex2.compiler.mxml.ImplementationCompiler.generateImplementationAST(ImplementationCompil er.java:499)
    at flex2.compiler.mxml.ImplementationCompiler.parse1(ImplementationCompiler.java:197)
    at flex2.compiler.mxml.MxmlCompiler.parse1(MxmlCompiler.java:168)
    at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2871)
    at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2824)
    at flex2.compiler.CompilerAPI.batch2(CompilerAPI.java:446)
    at flex2.compiler.CompilerAPI.batch(CompilerAPI.java:1274)
    at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1496)
    at flex2.tools.oem.Application.compile(Application.java:1188)
    at flex2.tools.oem.Application.recompile(Application.java:1133)
    at flex2.tools.oem.Application.compile(Application.java:819)
    at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:344)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(A SApplicationBuilder.java:276)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplication Builder.java:127)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:190)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:7 4)
    at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectB uilder.java:480)
    at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuild er.java:306)
    at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncremen talBuilder.java:157)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
    at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516)
    at org.eclipse.core.internal.resources.Project.build(Project.java:94)
    at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:221)
    at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162)
    at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38 )
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    !SESSION 2010-12-22 09:48:27.766 -----------------------------------------------
    eclipse.buildId=M20100909-0800
    java.version=1.6.0_16
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Framework arguments:  -product org.eclipse.epp.package.jee.product
    Command-line arguments:  -data C:\Client_Flex4 -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
    ================================================
    3. RESOLUTION/WORK AROUND
         - I was able to get this problem cleared by putting compiler option for Flex Application projects:  -keep-generated-actionscript
    4. SIDE NOTE
      I do not really see putting this compiler option as the solution and living with the mistery is making me fill a bit bad.

    Hi Faser,
    I just tried it on Vista with our latest FB Plugin build but
    I was unable to reproduce your issue with the following setup:
    - FB Plugin build installed by Administrator account user
    under her Documents folder
    - Administrator account user can launch, create Flex projects
    under her own workspace without any problems
    - Standard account user can launch the FB Plugin build (need
    Admin's password) and create Flex project (default location) under
    his own workspace
    If your setup is different, can you please log a bug at
    http://bugs.adobe.com/flex.
    Be sure to include what build you are using, whether it's
    reproducible, the detail of the setup, etc...
    thanks,
    Sharon

  • App. builder Error 1003 occurred at ..... internal.llb

    Hi,
    I have an RT application that uses three FPGA PXI-7831R. The application was created with LabVIEW 7.0. We upgraded to 7.1, then to 7.1.1. We followed the instructions for 7.1.1, mass compile LabVIEW and mass compile our own code.
    For the FPGA I had to create projects. I built the loads for each of them, updated the Open FPGA References in the RT code and then I was easily able to build an EXE with application builder. However, that load contained errors, so I had to debug it. I changes aliases in the FPGA projects, recompiled the 3 FPGA loads and refreshed their references in the RT code. I was able to debug the code and solve all my problems. That load would run with LabVIEW environment, downloaded to the RT target.
    However, with application builder, when I compile that new load, I get: Error 1003 occurred at … internal.llb… The VI is not executable. I verified the VIs and their arrows are not broken. I already had "BldApp.RemovePolyVIsandTypedefs=False" in LabVIEW.ini. I opened my RT top level VI and performed ctrl-shift-run and LabVIEW becomes not-responding, taking 99% of the CPU, in that state for 90 minutes. I repeated that with a lower level VI containing FPGA Read/Write Control and got the same behavior, ctrl-shift-run makes LabVIEW to process I don't know what until I kill it. I could repeat that on 2 more PCs. However, it is ok if I do that with a VI not containing FPGA references.
    The VI stated to be non-executable contains call to FPGA Read/Write Control. I removed these calls to debug and I got the same Error 1003 on the next VI containing an FPGA Read/Write Control. Are there some known issue with application builder and accessing FPGA with LabVIEW RT 7.1.1?
    Thanks!

    Hi, AvernaFrca
    You shouldn't have any problems when creating an EXE in LabVIEW that calls the Open FPGA VI Reference or the Read/Write Control VI. There are a few KBs online that relate to that error number, but it seems that you have read them already, because the suggested fixes are to mass compile (or do Ctrl + Shift + R) and that doesn't seem to fix it for you.
    In your case, I would recommend you to make sure that your VIs are not corrupted. The easiest way will be to create another FPGA VI that you could call from a brand-new host VI. It can be something as simple as just do A + B. If that does work, then it might be a problem with your current VIs and it might be a good idea to recompile them, just to make sure. Hopefully that will take care of it. If the error is still present, then the problem might be the actual Read/Write Control VI, and we will have to fix or replace it with a new one.
    I hope this helps! Let me know if you have any additional information.
    GValdes

  • An internal build error has occurred. Right-click for more information

    Greetings!
    We are using Eclipse 3.4 or 3,5 with Flash 4 plugin and Flex SDK 3.3.0.
    Project set comprises several, more than a couple dozen, dependent  Flex and Java projects.
    Time-to-time we run across an internal build error on all Flex projects.
    The stack trace where topmost entries are:
    So far we did not find how to get around the problem except delete project set and start from
    scratch.
    Pleas help!
    !ENTRY com.adobe.flexbuilder.project 4 43 2010-07-23 14:40:38.353
    !MESSAGE Uncaught exception in compiler
    !STACK 0
    java.lang.NullPointerException
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.applySettings(ASBuilder.java:3 25)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.setup(ASApplication Builder.java:67)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.setup(ASItemBuilder.java:5 4)
    at com.adobe.flexbuilder.project.compiler.BuilderFactory.createBuilder(BuilderFactory.java:8 0)
    at com.adobe.flexbuilder.project.compiler.BuilderFactory.createBuilder(BuilderFactory.java:5 9)
    at com.adobe.flexbuilder.project.compiler.BuilderManager.getBuilder(BuilderManager.java:192)
    When it happens you can not open project "Properties | Flex Compiler"  dialog because error
    message pops up saying "The currently displayed page contains invalid values."
    I am not sure how "an internal build error..." relates to "...displayed page contains invalid values"
    but  it worth to mention anyway.
    Thanks for your help.

    Getting the same error and deleting bin-debug files doesn't help. All switch statements have a case so that isn't an issue either.
    Says to right click on the error for more info but that brings ups broken webpage.
    Adobe I think you really rushed Flash Builder out to fast.  These weird errors and the namespace debacle is just totally unprofessional.

  • LabVIEW Build Error

    I attempted to build an existing LabVIEW project for deployment on a new computer.  This is the first time I have built this project under Windows 7 and LabVIEW 2012 SP1.  The build did not complete and the following message was received:
    "CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    Validating...
    Copying files...
    Scanning files...
    Updating files...
    Build complete successfully.
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'NI-488.2 for Windows, Version 3.1.1' from: C:\ProgramData\National Instruments\Update Service\Installers\NI_20130308_0954\Updates\NI-488.2 3.1.1 3.11.99999\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
    Copying distribution 'NI-DAQmx 9.6.2' from: C:\ProgramData\National Instruments\Update Service\Installers\NI_20130308_0954\Updates\NI-DAQmx 9.6.2 9.62.49152\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
    Copying distribution 'NI-SWITCH 4.6.1' from: C:\ProgramData\National Instruments\Update Service\Installers\NI_20130308_0954\Updates\NI-SWITCH 4.6.1 4.61.49152\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
    Building deployment
    Copying setup files
    Setting merged database information
    Setting product information
    Setting developer part information
    Starting final build
    Validating...
    Copying files...
    Scanning files...
    Updating files...
    Creating merged database...
    Creating installer files...
    Build complete successfully.
    Copying additional setup files
    *** Error: Windows SDK function returned an error. (Error code -12)
    Error accessing a resource module "Z:\Projects\CP-26\LabVIEW Code\Builds\CP-26 Installer\Volume\supportfiles\customResource0012.dll".
    *** Error Details:
    Error in MDF API function: _MDFBuildDist_Build
    Error in MetaToolbox::UpdateResourceString.
             strId: 2; New String: CP-26 Program Installation (Database Version); LangId: 12
    Windows function LoadResource returned an error. Error code: 193
    *** End Error Report
    Done building deployment"
    Please advise.  Thanks.

    Hi Double_D,
    Are you trying to build an EXE or an Installer? You may need to ensure that dll links are linking correctly. Which version of LabVIEW was this project originally developed? That may also be an issue. Especially if you are changing LabVIEW versions, Operating Systems and .NET versions. Here is a document that dicusses some possibilities of the error.
    http://digital.ni.com/public.nsf/allkb/AFC375154EFBD6AE8625760B005FB723?OpenDocument
    Ryan
    Applications Engineer
    National Instruments

  • Error -107413504​0 occurred at tkds30xx Configure Acquisitio​n Type.vi

    I am trying to use a TDS-3034B scope with LabView. I use one of the example on the driver, but I have this error in the first block.
    Error -1074135040 occurred at tkds30xx Configure Acquisition Type.vi
    But I don't find this erro in the help.
    Sorry for my English
    Thanks for your help.
    Best regards, Yiye

    Hi,
    Check this thread to see if it applies: http://forums.ni.com/ni/board/message?board.id=170​&message.id=74570&requireLogin=False
    If not reply to this thread for more help
    P.M.
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion

  • Labview Builder Configuration

    Hello,
       Can the Labview builder that makes a exe be configured to copy over support files to the destination of where the exe is located? If so, how is it done?
    Regards,
    Kaspar
    Solved!
    Go to Solution.

    That is the job of the installer that you create.

  • Internal Build error after creating a new project

    I just installed Flex using the plugin install to Rational
    Software Architect v7.0 (Eclipse 3.2) on Windows. The system
    requirements page says Rational Software Architect is supported.
    when I create an MXML application, I immediate have an "Internal
    Build error has occurred message. It tells me to check the log
    file" But I'm not sure where that is.
    My MXML file only has the following code:
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="
    http://www.adobe.com/2006/mxml"
    layout="absolute">
    </mx:Application>

    Please see the suggested solutions in the following docs.
    Entity Maps Not Defined For Attachment Error When Selecting A Deliverable (Doc ID 358385.1)
    Corrupt Personalization - No Entities Found Entitymaps Not Defined For Attachment Item (Doc ID 1085011.1)
    R12:Supplier Page Unexpected Error: 'No Entities Found EntityMaps not Defined for Attachment Item' (Doc ID 1361320.1
    Geography Hierarchy No Entities Found, EntityMaps Not Defined For Attachment Item (Doc ID 831088.1)
    Depot Repair Bulk Receiving Error: "No entities found, entityMaps not defined for attachment item" (Doc ID 1357977.1)
    Thanks,
    Hussein

  • Error 7 occurred while building source distribution in labview 8

    I can build exe file and  installer for my project. But while trying to build source distribution i got an error. Error description is as follows:
    Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux.

    Hi Andy,
    FYI, initially part of this project was developed in LabVIEW 7.1 and now I have
    converted all the project files to LabVIEW 8.0. This was done by mass compiling and
    saving all the VIs.
    It is possible for me to build source distribution for some other programs. But I got the error while building source distribution for my current project. Same error was generated even while previewing the source distribution. This project contains some dynamic VIs. I had included them under the dynamic VIs and support files while creating EXE file. While building source distribution, i got an error message saying that :
    "Unable to generate preview. An included VI or one of its dependencies does not exist. Open all Startup/Exported/Dynamically called VIs, recompile them  (Ctrl-Shift Click the run arrow), and save them to update their dependencies.
    \\Source code\Controls\Tests\Battery Current Calibration\Battery Current Calibration1.ctl
    <Call Chain>Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine_Preview.vi -> SDBUIP_Build_Rule_Editor.vi -> SDBUIP_Item_OnDoProperties.vi -> SDBUIP_Item_OnDoProperties.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux."
    For this error I rename the control, relink it in the code, and save the VI. Now I got an error message indicating different control. I was totally confused by this behaviour. What is the problem? Why the problem occured? What procedure to follow to avoid these kind of errors in future? I would be thankful, if I can get answers for my questions.
    Thanks in advance.
    Ramasamy.

  • Error 1 occurred while building source distribution in labview 8.2.1

    I can build exe file and  installer for my project. But while trying to build source distribution on RT i got an error. Error description is as follows:
    Error -1 occurred at Invoke Node in SDBUIP_Build_Invoke.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_CreateNewWizard_Invoke.vi->SDBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
    When i click generate preview, i got an error.
    Unable to generate preview. Invoke Node in ABAPI Dist read linkages.vi->ABAPI Dist Cmp Settings to Disk Hier.vi->ABAPI Get Settings From File2.vi->SDBEP_Invoke_Build_Engine_Preview.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_Item_OnDoProperties.vi->SDBUIP_Item_OnDoProperties.vi.ProxyCaller
    Thanks in advance.
    Poolsak T.
    Attachments:
    rt_deploy2.zip ‏34 KB

    Hi,
    I would first try mass compiling the vi's within your project to ensure there aren't any unresolved conflicts. Moreover, it's intersting that you can create an application without problems but upon building a distribution, things go awry.
    Do the vi's run on the RT target without error? Does the application run on the target without error? Or do they run on your host just fine and its when you attempt to deploy on to your RT target that this error occurs?
    Let's see where this gets us.
    Cheers,
    Emilie K | National Instruments

  • Error 7 occurred at Open VI Reference with Application Builder

    Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
    "Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

    Dear Sir;
    There are two things that are good to try:
    First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
    Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
    .llb file to compile.
    Regards

  • Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi- Dist Build LLB Image.vi- Dist Build App Image.vi- Build Application.vi

    When trying to build  an application using labview 7.1 and windows XP,  I get the error
    Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
    I've tried the crtl-shift-run as well as  a mass compile and I still get the error.
    Any ideas?
    Thanks,
    Mike

    Hopefully this thread, or this KB article might help.
    It seems like this could come from a lot of things, but there's suggestions in those which might lead you in the right direction
    Message Edited by Day on 09-22-2006 02:07 PM

  • Opening Build Specificat​ion - Error 7 occurred at Get LV Class Default Value.vi

    I recently ported my project to a new PC. Everything seems to run fine uncompiled, and I am able to build an executable without issue. However, my build specification shows up in the project explorer with question mark next to it. When I try to build again or edit the properties I get a popup with the information below:
    Error 7 occurred at Get LV Class Default Value.vi
    Possible reason(s):
    LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
    =========================
    NI-488: Nonexistent GPIB interface.
    Complete call chain:
    Get LV Class Default Value.vi
    AB_UI_Initialize_Framework.vi
    AB_UI_FRAMEWORK.vi
    AB_Item_OnDoProperties.vi
    AB_Item_OnDoProperties.vi.ProxyCaller
    LabVIEW attempted to load the class at this path:
    <Empty Path>
    I've seen messages from people getting the same error when trying to run a compiled executable, but mine actually runs fine. I am just unable to open the build specification to rebuild or edit its properties.

    This application is for a Windows machine, and I am not using the Report Generation Toolkit. However, I shut down my computer last night and when I booted it up this morning my Build Specification now opens fine and I am able to edit it. My only thought as to why it occured in the first place is that I had added several files to user.lib and instr.lib and restarted LabVIEW, but it appears that it required my computer to be restarted as well.

  • Error 1073807202 occurred at Property Node (arg 1) in VISA Configure

    I am working with the 30-day evaluation version of LabVIEW
    (Version 9.0 32-bit).  I am attempting to perform the serial loopback test
    described in NI's Developer Zone Tutorial, executing Basic Serial Read and
    Write.vi.  When I click the Run arrow a dialog box appears with the
    following legend:
    "Error 1073807202 occurred at Property Node (arg 1) in VISA Configure
    Serial Port (Instr).vi>Basic Serial Read and Write.vi.  LabVIEW: VISA or
    code library could not be located.  ...required drive not installed..."
    I can find the "smplserl.vi" driver in the /examples folder on my PC.
    What's wrong?

    Did you do a search for that error? Install NI-VISA.

  • Build error after upgrading from 8.2.1 to 8.5 "Error 1055 occurred at Invoke Node..."

    After upgrading to 8.5, I'm getting the following error when trying to build an EXE:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.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:  Object reference is invalid.
    I have been building this application for both Windows and Mac OS, and I even get the same error when building the .app on an Intel Mac.
    Things that I've already tried:
    * Mass-compiling all my code
    * Created the project from scratch
    * Enabled each panel of the "diagram disable structure" one at a time and compiled again
    Any ideas?

    Hi Travis,
    Ben’s advice if definitely the best place to start. Error 1055 is a very general LabVIEW error for “Object reference is invalid.” The cause is usually a bad install where important LabVIEW function aren’t placed in the right directory or aren’t installed at all.
    Charlie M. CLD

Maybe you are looking for