Error source distribution building

Similar Questions

• Is it possible to include the file lvprog in a source distribution build specification

  It seems to me that a full source distribution includes the associated project files but I don't see that it is possible to do. I missing something or do I just have to continue to, outside of LabVIEW, high zip folder that contains everything?

  I think you are talking about the *.lvproj (not *.lvprog).

  No, it is not possible. I think it was possible in the past (LV2009 and earlier versions) and I already complained that elsewhere long ago.

• error generating a source distribution

  I get the following error when generating a source distribution in LabView 8.6:

  Error 1 has occurred to AB_Destination.lvclass:Copy_File.vi-> AB_Source.lvclass:Copy_SourceItem.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller

  Hi RBFOLS,

  Thanks for the post and I hope that your well.

  Have you been movement screw around because you changed the build / did you take a few screws a another version of LabVIEW?

  I would recommend Delete the construction specifications and all files created by built so far. "" I would compile then mass the llb (screws using your) Tools "Advanced" mass compile.

  This error can be caused if you have named your executable with a character of invalid filename as a carriage return, or one of the following characters: \ /: *? " <> |. If the specified file name contains one of these characters, remove it and you should be able to build your executable without problem.

  Another point - which path names you use, make sure you the correct paths.

  If no joy, which was the full error message?

  Remember, if your component dynamically all live you must include the manually in the support screw.

  Hope this helps,

• RT VI does not source distribution after reboot

  Here is a strange...

  I have a very complex application.  It runs great development environment.  It also runs great as a Starter (no GUI) rtexe.  When I build a source distribution and deploy a path of RT controller...

  VI Server invoke the method shows NO errors but the VI does not seem to be running. If I open a project, right-click on the target and click 'Connect', suddenly the invoke begins to work.  I think there must be a way to configure the settings of VI for the RT controller sur-boot server, but I don't know how it's done, or why I would not get an error before selecting the connection in a project.  Any ideas?

  Thank you

  XL600

  
  

• problem of visarc in the source distribution

  I am trying to build a distribution from source to a project in LabVIEW 8.6.1.  I need to build the source distribution so that I can password protect all VI in the project (about 1200).  When I try to compile the source distribution I get the following error message.

  

  As you can see the source file does not exist because the path: C:\Documents and Settings\Program NIUninstaller Instruments... does not exist.  So, I created this path and place the visarc file where LabVIEW thinks it should be.  When I Isaiah to compile the source with the wrong path distribution I get the following error message:

  

  Once more the following path does not exist: Program Files: \Nationa lnstruments\LabVIEW 8.6...

  I don't know how to create this way false because he seems to treat the program as its own hard drive files.

  The next thing I did was reinstall DAQmx 8.9 as the name of the file is visarc, I don't know that it is connected to DAQmx but the visarc makes me think it might be.  DAQmx reinstalling does not fix this error.

  I should also add that I was able to build a very good three weeks ago source distribution.  During the last three weeks the code was treated by myself and two other developers.  I had seen problems with other developers link dll from their office of vi in the library, and when I pulled it back on my machine, I have been unable to build a source distribution, because their DLLs have been at a different path.  I solved this problem of rebind each Subvi to the dll in the correct path.  Could be a similar problem where one of the other developers visarc stored in C:\Documents and Settins\Program files... and I just need to recreate a link to the visarc file?  I don't think so because I don't think "recreate a link to the visarc file" is since then.  I'm open to any feedback.

  Thank you!

  Here is a solution provided by an EA:

  Hi Jon,

  The following information should help you to resolve the error you see

  LabVIEW VIs point to the rc files that are not in the vi.lib.  This means if you move the VI on disk (upward in a folder, in a folder, another drive), then the path that he stored in the rc (relative path) is no longer correct.  The application builder will recognize that the rc file will have two different routes (the one which is correct and which is not).
  Once two different paths are recognized source distributions will not be built successfully.  To correct this problem, follow these steps:
  1. If you have any previous version of LabVIEW installed temporarily
  Rename the folders of their resources.  Directories of resources can be in the labview\resource directory.
  2. Add massCompAll = True in the file LabVIEW.ini version of LabVIEW
  used.  The file is located in labview\LabVIEW.ini.  LabVIEW must be closed when you change the LabVIEW.ini file.
  3. launch LabVIEW, mass compile the project, and then try the build.
  4. exit LabVIEW and difficulty of any renamed resource records again to their
  original name.
  5. remove the massCompAll = True token in the LabVIEW.ini file once the
  compilation of mass is over.
  Note: Rename files from older versions of LabVIEW resources is critical because the token defined otherwise has a chance to cause the vi.lib of the different versions of LabVIEW to be reticulated

  Meghan
  Technical sales engineer
  National Instruments

• Source Distribution packaged vs project library

  I design my architecture for a project, and I want to use plugins for future expansion. Most of the information I found recommended the use of baskets library project for each plugin. But once in a while I find someone who is recommended to use the source distribution. I intend on creating this software to end users who do not have a development environment and who are not able to modify the code.

  So, I have a few questions.

  1. What is the difference between the source distribution and the project libraries packaged?
  
  
  2. What are the benefits of one over the other for plugins?

  Source distribution contains the source. It allows the end-user upgrade from the source of their version of LabVIEW (envinroment development only) since the source is dependent on version, and if the files are saved with the code were met, they can work in an envinroment of execution to the version of LabVIEW they were last updated in. However, the distributions of this nature seem to have several files to deploy. One of the main reasons to prefer this method is due to complications of "chaining" library dependencies of project packaed which we are stuck with until NEITHER arrives with a type of 'solution' for the control of this.

  The project packaged libraries are built (compatible execution) which do not require the environment and are generally single-file development which makes them easier to deploy. However, they are built to a specific version of LabVIEW. One of the main reasons for choosing this method is version control (files have version information) as well as ease of deployment (single file).

  At the end of the day it depends a lot on your end user in my opinion. Management of multiple files is a pain of a source distribution point but then so is chaining builds for libraries in the project packed and the problems of name-spacing inevitable that comes with it. Managing dependencies is never easy, and there is no easy fix for this solution in LabVIEW.

• How can I include all the VI that are listed in the hierarchy of VI for a source distribution

  I'll send my request to another developer. To do this, I used the source distribution function. But if I generate the files I miss the VI they are stored in the form of instrument drivers. How can I include, too?

  Walter wrote:

  I'll send my request to another developer. To do this, I used the source distribution function. But if I generate the files I miss the VI they are stored in the form of instrument drivers. How can I include, too?

  This is exactly yhe reason I'll go through and save screw driver to subfolders in my application directory. In this way, I can keep the NCC updated with a complete set of code including any mods, I do the driver (usually change of reentrancy).

  But if you don't take this approach, you will have to send you a colleague from the same packeage installing driver allowing you to put it on your machine.

  Ben

• After making some changes I sometimes get the error message "cannot build a review because of a program error? Any suggestion would be appreciated.

  After making some changes I sometimes get the error message "cannot build a review because of a program error? Any suggestion would be appreciated.

  Molloy10 wrote:

  After making some changes I sometimes get the error message "cannot build a review because of a program error? Any suggestion would be appreciated.

  What changes?

  What program?

• * ERROR *: file d:/build/ob/bora-127388/bora/vim/lib/gvmomiMOMgr. c: lin

  Hi friends:

  I m automation ESX 4.0 with vix api 1.6.2... When I connect to the server I get this error:

  ERROR*: file d:/build/ob/bora-127388/bora/vim/lib/gvmomiMOMgr. line c: 212: failed assertion: (priv-> updatesListener == NULL) abandonment...

  I read in other threads and disconnect me properly the host, I have reinstall the server, etc... but I have can´t ignore this error... What can I do?

  Thank you!!

  What you write it in? C++, C#? If you're not do whatever it is threaded, then you should be able to get it to some stable level by closing all handles and logout (you think you are, but you are not), so it's a bug in your code. If you do this on multiple threads to several virtual machines, it will not work with 1.6.2 due to known bugs. If you write it in c#, use VMWareTasks and save yourself to treat the headaches with handles - all that needs to be closed is IDisposable.

• Error code install Build-12 when copying distribution

  Hello to you all, useful forum fans!

  I have problems of construction of a Setup program for my product now that I upgraded to LabVIEW 8.5.1 2010.  My project is an executable version, and then 3 built installer who put a different value in the registry that indicates the level of the executable permissions: Basic, full and complete.

  When I complete Isaiah to compile the version, I get the following error:

  CDK_Build_Invoke.VI.ProxyCaller > CDK_Build_Invoke.vi > CDK_Engine_Main.vi > IB_MSI.lvclass:Build.vi > IB_MSI.lvclass:Engine_Build.vi > NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi

  Adding files to install
  Makes adding files
  Preparing to build the deployment
  Copy of the products of distributions
  Copy distribution 'Williams International - Ultimate Engine Maintenance Terminal (WI_EMT)' to: C:\CP356\WI_EMT Ultimate Installer\ to: C:\Documents and Settings\All Users\Application Data\National Instruments\MDF\ProductCache\
   
  **************
  Error: Windows SDK function returned an error. (Error code - 12)
  The system does not have the specified path.

  **************
  Error details:
  Error to the MDF API function: _MDFDistCopyList_CopyItem
  Windows as FindFirstFile function returned an error. Error code: 3
  Final report of the error
  **************
   
  Deployment of the completed building

  The weird part is the path "to leave" does not exist, but C:\CP356\ contains the files in my project (including several subdirectories).  But even if she did, I have no idea why the Ultimate version is referenced when I build the full version.  I just tried to build Setup ultimate and got the same error.

  Unknown, this error disappears if I stop wanting to include NI-VISA Runtime 5.0 in the section other installers of my Installer.  The only other "extra install" I checked is the runtime LabVIEW 2010.  The VISA duration is required for my product, so I can't just leave it unchecked.  Another clue is that installation location of execution VISA of the Source is listed as D:\, my DVD player.  But even when I put the DVD of device drivers in the drive, I get the same error during construction.

  I tried to look into the DVD device drivers, but it is said that the VISA Runtime 5.0 is already installed on my computer; I forgot the exact path that he enrolled, but I can get it again if it would help someone.  But I couldn't figure out how to change the location source for him ask to get this installer locally.

  Based on the posts that I found in this forum of error code - 12, I also created a new Build specification for the full installer and set the same options as above, in the case where something has been corrupted when I updated, but it doesn't seem to make a difference.

  I'd appreciate a lot any idea that anyone has on how to resolve or work around this problem!

  Thank you

  -Joe

  Hi jmorris,.

  Rather than reinstall the NI-VISA Run-Time, we actually want to reinstall the entire pilot. Go ahead and go into Add/Remove programs and uninstall the NI-VISA entries. Then download the installer of NI-VISA from here and install. This should update the path location in the application builder. Then try building your application to see if you get the same error.

  Paul M

• Live control error 2983 while building an exe which has source

  Hello

  I am tyring to generate an exe for a code that has the control code source screw inside. I get error 2983 while running the exe. I did some research and found that on the three parameters that must entered in the ini file. I did this and the NI_SCC_P4CMD.lvlib also added to the dependency. I still get the error. don't know what I'm doing here. Here's my variables in the ini file

  SCCConfigData = 'TRUE; TRUE; »
  Necessarily SCCProviderName = "command line".
  SCCProviderLocation = "P4CMD".

  people of Nevermind. I added the file to the list always included instead of the .lib file and it works great!

• Unlock source distribution

  So I have a bunch of configuration files that are stored in a different location from the application, so I created 2 built, one for the .exe and distribution from a single source for the configuration files. The installer works well such things as well as copies of their respective filders in an orderly manner. So far so good.

  The problem: the ini files - get administrator rights and I can not unlock in the Setup user interface. Users must be able to edit the files. Ideas?

  /Y

  Well, I created a solution, but I'm not very happy about it, I think there must be a lighter way on this subject.

  I created a vi which runs a system with a command attrib exec. It is compiled into an exe in a separate build definition. It is installed in the same location as the main user interface and in the installation program, it is defined as running after installtion.

  Is this really the best way?

  Why can't I just throw a system as part of the installation command but only compiled of vi? Why should I install the exe, why not a 'walk only with installation?

  /Y

• Get errors trying to build ASDOC for a library

  Try to build ASDOC documentation for a library and get errors on some classes.

  Error: Could not resolve < s:SolidColorStroke > to a component implementation

  Error: Could not resolve < s:SolidColor > to a component implementation

  Error: Could not resolve < s:Sequence > to a component implementation

  ....

  Of course, the library compiles fine and works fine as well. Only asdoc gives the above errors.

  Here are the arguments passed to asdoc:

  -source-path "${workspace_loc: / FLEX44D}.

  -Clément

  -doc-classes FLEX44D

  -main-title "Flex44D library".

  -window-title "Flex44D Library Documentation.

  -output "${workspace_loc} / FLEX44DDocs".

  -namespace http://flex44d.skunkwerks.ca flex44D - manifest.xml

  -doc-namespaces http://flex44d.skunkwerks.ca 

  keep-xml = true - jump-xsl = true

  No idea what could cause the above errors? Bizarre and asdoc chokes on these classes to spark.

  Am I missing any argument?

  FYI: using 4.5.1 with AIR 2.7 SDK.

  TIA

  Julio

  So after some struggle to find a solution to my problems, I looked at the sdk asdoc/build.xml and noticed some special name used spaces. I solved my problem by adding the references to namespace following asdoc command line:

  namespace-+= 'http://ns.adobe.com/2009/mx-mxml', ' / Applications/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/projects/mx/manifest.xml.

  -namespace = "http://www.adobe.com/2006/mxml", "/ Applications/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/mxml-manifest.xml.

  namespace-+= "library://ns.adobe.com/flex/spark", "/ Applications/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/projects/spark/manifest.xml.

  namespace-+= "library://ns.adobe.com/flex/mx", "/ Applications/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/mxml-manifest.xml.

  namespace-+= 'library://ns.adobe.com/flex/spark-mobilecomponents', ' / Applications/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/projects/mobilecomponents/manifest.xml.

  namespace-+= 'library://ns.adobe.com/flex/spark-dmv', ' / Applications/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/projects/spark_dmv/manifest_spark_dmv.xml.

  May not need all these namespaces, but they have made the round. After you have added the above errors are gone.

  Are 4.5.1 sdk path in OS X, you may need to adjust your OS + sdk.

  Hope this helps someone else

  Julio

• Weird error for a build specification

  I deleted some files in my project, and all of a sudden my generation specifications no longer work:

  

  If I choose Properties to 'view', I get the error message:

  

  Choose "build together" ' Building specifications ' apparently still works. I tried to delete all the project files and make a new project, but something is always wrong. Clues?

  OK, I threw all the files, make a new directory, rebuilt, and now it works. Don't know what was wrong.

• Error trying to build the cRIO RT application

  Hi all

  I'm trying to build an executable to run my cRIO-9022 project on a computer without labview and receive the following error message when you try to build:

  "

  Error 1 has occurred to copy in AB_Engine_Copy_Error_Files.vi-> AB_RTEXE.lvclass:Copy_Error_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_RTEXE.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

  Possible reasons:

  LabVIEW: An input parameter is not valid. For example if the input is a path, the path can contain a character not allowed by the operating system such as? or @.
  =========================
  NOR-488: command requires GPIB controller charge controller. »

  I ran the program from a computer with labview for the cRIO and it works very well.  I've attached a screenshot of my main block diagram because he said it could be a bad path?  Any advice?  And it comes to labview 2011.

  Thank you

  If you're still having problems, you can ensure that you don't have spaces or special characters in one of your names in VI. And check all references to the paths absolute or relative to your subVIs.

  The Advanced tab of the Build executable window has a few options that you can try to change. You can uncheck 'Copy error code files' and check the 'use LabVIEW 8.x file layout' options. A final step would be to turn on debugging see if that clears the error message.