Building installer [installanywhere]

Hi folks.
I have developed applicatoin with JRE and JMF.
Abound 2 months ago I downloaded installanywhere from www.zerog.com and built installer.
It was very nice, I included jmf .dll-s and since theres internal JVM I could easily use Object Serialization.
Problem is, that zerog does'nt offer free version anymore. I even suspected that maybe I remember something incorrectly - but no - I found install i've built 2 moths ago, isntalled it to my machine and everything worked.
Now meanwhile I 've this free version of installanywhere [that i used 2 moths ago] is gone from my harddisk.
So can anyone help me out and tell me if its possible to get this free version if IA, or suggest any other good installer builder for my requirements ( need internal JVM, or else im gonna have problem with object serialization).
thanks.

I have the free version installed, but have lost the setup exe too...
Hope they make it available again.
Install4j doesn't seem free either.
I've tried NSIS (nsis.sf.net): open source window installer through Maven (maven.apache.org), it generates me an exe which install the jar etc, but doesn't include a JVM. If no JVM is found it does open a browser window from were to download Java.
There is an issue in Maven's NSIS plugin to include a JVM in the NSIS script

Similar Messages

I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
Solved!
Go to Solution.

Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
You can find more details about this issue in this KB:
KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
And for keeping a copy here is more info:
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Best Regards
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Geting error when build installer

I'm getting Error 33 and dotnet x86 ni language pack error and build stops
how can I solve this issue?
Building executable is fine, but the problem occurs during building installer.
Please advice
regards
Pierre Tannoury
Pevatech International S.A.R.L

thanks for helping,
i still receive another messages but the dotnet error message is gone
please see below the building status and what's errors remaining
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
*** Error: Fatal runtime error. (Error code -10)
*** Error Details:
Access violation! Structured exception code 3221225477
*** End Error Report
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(819): IInstallerError 108
Problem with updating Part DataSocket64.msi.
*** End Error Report
Done building deployment

Project Build Installer Properties Slow to load, (Maximum vi size)

I have a LabVIEW Project with 450Mbytes of source code, and drivers. The Project was originality in LabVIEW 2009. I upgraded to LabVIEW 2011.
Now the Project Build > Installer Properties Menu is about 10x slower than was in LV 2009.
I've done a mass compile, resolved all error messages in the Project, yet 2011 is still 10x slower than 2009.
The 2011 Project will build an functional exe, and a functional installer given enough time (like 15 minutes). During that time the computer is locked up, no other applications are functional.
The Computer is XP, dual Core, 2.5GHz, 4Gbytes Ram, 4Gbyte Page File.
The NI Support Desk is saying (quote) >>>> seem that the requirements for LabVIEW 2011 are different than the requirements for LabVIEW 2009 <<<<<
Suggestions ???

Does the procedure take 30 minutes or 15 minutes (first post)? Also, what is it about the installer build spec that requires further modification after you modify your exe build spec? If the exe is included in the installer, the installer build will automatically re-preview the included exe to get an updated list of files to include next time the installer is built. So unless you need to modify something about the installer spec and not the included source files, no edits would normally be required after changing your exe (or other included source files).
Keep in mind, the previewing of the exe will take about as long as it takes to build the exe -- it's computing a list of the files that would be built without actually creating the files. A data point of interest is how much longer it takes your exe to build, comparing 2009 to 2011. Does your exe take 10 times longer to build in 2011? Longer exe build times mean longer preview operations in Installer Builder.
Another thing to check is which distributions you're including on the Additional Installers page. Are more distributions being included in the 2011 build? Did the distributions change significantly in size since 2009?

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Could JavaFX Scene Builder installation depend on JRE_HOME setting?

Hello,
I have no privilege to install software in company computer so I copied Jre7u3 (Java Runtime 7 Update 3 ) folder from home to the company and set JRE_HOME for user variable. It still shows following info when installing Scene Builder.
No Suitable 32-bit Java Runtime Enviroment (JRE) has been found.
You should install:
- Java 6 Update 29 (32-bit) or above
OR
- Java 7 Update 2 (32-bit) or above
Could JavaFX Scene Builder installation depend on JRE_HOME setting or any other solutions exit for this issue? Thanks.

Surprising. Your hardware should run Scene Builder without any trouble.
With Java 7 U5 I run SceneBuilder 1.0 b44 on Win XP 32-bit and 1 G of RAM, with -Xmx1024m.
Aren't you facing an issue with Java ? do you run successfully other Java applications of a comparable size ?
You may also download the Scene Builder samples: according you've Ant and FX handy you can run them command line.
For what is about removing or modifying the -Xmx option the answer is no, this can't be done in this release.
Regards

Bug in the flex builder installer

I found a bug in the Flex builder installer, while someone
tried to install Flex on top of our EasyEclipse eclipse distro.
I am making a post here since I could not find a way to
report a bug anywhere on the Adobe web site :-\
So the bug is that the installer is looking for an eclipse
installation that is packaged exactly like the Eclipse platform,
but also specifically checks for the presence of features named
org.eclipse.rcp and org.eclipse.platform.
Yet the flex features themselves do not care about other
features only about the platform plugins to be present, as it
shoudl be.
It is considered a bad practice by the Eclipse platform team
to have a dependecy on features, and it is recommended to use
instead plugin depdencies.
See
http://wiki.eclipse.org/index.php/Version_Numbering#Versioning_features
As a result, Flex cannot be installed anywhere but on a vanilla
Eclipse.
EasyEclipse does not ship the base features of the Eclipse
platform, yet all the Flex plugins dependencies are statisfied.
See our forum for more details:
http://sourceforge.net/forum/message.php?msg_id=3982548

Getting back to the original message in this thread, I want
to post an update about what I learned on digging deeper. The Flex
Builder 2.0.1 Plug-in version does not require a vanilla eclipse to
install into, but it does impose some minimal constraints. Before
release, we installed FB 2.0.1 Plug-in successfully with several
customized Eclipse configurations, including RSA7 and BEA, each of
which uses a different folder configuration for its product
extension point.
I took a close look at the dependency list for our FB 2.0.1
features, and these have been plugin-based dependencies all along,
not feature dependencies. I understand why it might appear as if
they're feature-based though, because our installer requires that
the feature named org.eclipse.platform be present.
We have the installer look for that feature, because that's
the way Eclipse's update manager reports what's already installed
and available. Eclipse's commandline API for updates only provides
Feature info, not Plugin info:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/mis c/update_standalone.html
The FB Plug-in installer checks for the existence of
org.eclipse.platform so that we have some assurance that the
version of eclipse proposed is at least version 3.1.2 or higher. In
our next release, we'll explore alternate way of gleaning this same
information, with the intention of allowing plug-in installs into
products such as EasyEclipse that don't include any Eclipse
features in their products.
C. Agruss
quote:
Originally posted by:
pombreda
I found a bug in the Flex builder installer, while someone
tried to install Flex on top of our EasyEclipse eclipse distro.
I am making a post here since I could not find a way to
report a bug anywhere on the Adobe web site :-\
So the bug is that the installer is looking for an eclipse
installation that is packaged exactly like the Eclipse platform,
but also specifically checks for the presence of features named
org.eclipse.rcp and org.eclipse.platform.
Yet the flex features themselves do not care about other
features only about the platform plugins to be present, as it
shoudl be.
It is considered a bad practice by the Eclipse platform team
to have a dependecy on features, and it is recommended to use
instead plugin depdencies.
See
http://wiki.eclipse.org/index.php/Version_Numbering#Versioning_features
As a result, Flex cannot be installed anywhere but on a vanilla
Eclipse.
EasyEclipse does not ship the base features of the Eclipse
platform, yet all the Flex plugins dependencies are statisfied.
See our forum for more details:
http://sourceforge.net/forum/message.php?msg_id=3982548

Does not represent a valid JavaFX Scene Builder installation

Selected location ...JavaFX Scene Builder 1.1 does not represent a valid JavaFX Scene Builder installation
Anyone else seen/get this error in Netbeans 7.3 Beta2 when they try to attach Scene Builder in the options screen?
Is there a work around?

My guess is that you run on Windows: the interoperability between NB 7.3 and SceneBuilder 1.1 on this OS has been fixed a little after NB 7.3 Beta 2. If you use the current daily NB 7.3 Developer Build it will solve your issue.

Problem of build installer

Hi!
I have got LabVIEW 10 and I need create build installer. But I don't build installer and have error 12 occured at CDK_CreateNewWizard_Invoke.vi.ProxyCaller.....
Thank!
Attachments:
ошибка.jpg ‏88 KB

Error code 12 might be something that needs to be looked at.
But hey have you tried THIS.
Let me know the progress.
=========================================
Please remember to accept a solutions and show your appreciation by giving Kudos to helpful messages...
Mangesh D.
CLAD | Project Engineer
==
VIPM, LabVIEW 8.2, 2009, 2011SP1, 2012, 2012SP1, 2013, cRIO,cDAQ, PXI, ELVIS, Multisim, Smart Camera....

LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

I'm having a problem building an installer in LabVIEW 2011SP1.
It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
Now when I try to build the installer I get "The build was unsuccessful."
Possible reasons: Error generating preview for My Application 3.1.7.
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** Error Details:
Error in MDF API function: _MDFCommon_GetNextLogMessage
Error in MDF::GetInstance - MDF static instance is not initialized!
*** End Error Report
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I do have the LabVIEW 2013 discs but didn't install it.
I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
So now I need to distribute 2 runtimes with my application?!?!
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

"Find Resources" does not work after Application Builder Installer

I use Lv Full 6.1 / Appl.Builder 6.1
VISA:"Find Resources" acts properly as long as a built application is installed on a PC that has LV installed.
as soon as only the runtime eng. is installed no resources are found.
Who helps?

Thank you Dennis for your reply. I tried to install the VISA runtime engine via the "Run executable after installation" but it appears to run the Visa-runtime-engine-installer before ending the application installation. So I had to run that installer manually. Nevertheless you pushed me in the right direction.
THANKS

Error -12 when building installer

OS: Win7
LabVIEW: 2012 SP1
I am having issues with the application builder while trying to build an installer.
The installler has the following "Aditional Installers" selected:
LabVIEW Runtime Engine
NU USI 2.0.1
NI DAQmx Core Runtime 9.8
NI DAQmx MAX Configuration 9.8
NI VISA Runtime
If I remove the "NI DAQmx Core Runtime 9.8" & "NI DAQmx MAX Configuration 9.8" then the installer builds without error. How can I get it to succesfully build with these selected?
I have upgrated the DAQmx from 9.5.5 to 9.8 and performed a mass compile but no luck.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
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
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 'SiriusXM Mad Max' from: C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
Solved!
Go to Solution.

Siriusly wrote:
Copying distribution 'SiriusXM Mad Max' from: C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
It looks like your installer build is trying to pull the "SiriusXM Mad Max" distribution from an unusual temp location. If this distribution was hiding inside a 7zip file and has since been altered or deleted, that we certainly confuse the installer builder. Do you know if this distribution contained the DAQmx installers you are trying to build with?
Here are a few things you could try if this is the case.
1. If an installer build ever suceeded while pulling source from this temp location, the location may have been saved as known good source. To undo this saved information, you can delete the file at C:\ProgramData\National Instruments\MDF\Bin\MDFInfo.xml
2. If C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ is a valid path on your machine, try moving or renaming this folder. This should cause the installer builder to prompt you for source media. This prompt window will allow you to configure which distributions you provide as source for the build (depending on the version of the installer builder tool installed, you may have to click "No" to the question "Do you have all of these installers?" to get to the configuration page).
3. Install the latest version of the installer build tool. A new one released with LV 2013, and it should be available to download either through NI Update Service or on the web somewhere
4. All else fails... post your full installer build log! LabVIEW generates this for us at %temp%\LVProjectName_InstallerName_build.log

Error during Extension Builder installation on Mac OS

I downloaded extension builder 2.1 trial version from adobe website: Extension_Builder_2_1_LS1_trial.dmg
When I try to install it, at the end of the installation process, during "validating packages" process it stops and shows me "The installation failed. The installer encountered an error that caused the installation to fail. Contact software manufacturer...".
1. System: OS X v. 10.9 (mavericks)
2. I have Flash Builder 4.7 premium installed on my computer.
3. I have Photoshop CC installed on my computer.
What may be the cause of installation errors?
What do you suggest?
Is there any other version of Extension Builder than I could try to install?

This is not an Adobe error message. Please check your system to rule out any environmental issues such as insufficient hard disk space (2G or so needed after you copied the installer since it will need to unpack some installation files), pending system reboot, download file corrupted etc. then retry installation.

Error usingEXE/Building Installer, and cFP .iak error

I built my app and created an .EXE, however when I run it, I get the error(see image error1.jpg) "Cannot Load the browse dialog. Some necsessary components are missing.to correct the problem, reinstall the driver software that is associated with this control." when I try to bring up the Filedpoint browse dialog. This when ra on the computer with LV8.5 full devel. version. If I just run the VI, everything works fine.
Also, when I try to build an installer, I get these errors: (see image)
And then the final question, whenever I shut down labview, I have to open MAX, create a new .iak file, "find devices" for each FP-device and then press "start" so I can see the current values. Then I have to remove the FPdevices from my project, and readd them (new targets and devices), (importing the Fieldpoint configuration does not work). then it all works again untill I close labview. might it be associated with the fact that I cannot save the config file in the project? (see image) when I close the window again, the configpath is gone and when I clock add it says "warning, error saving file".
thanx.
Anders
Message Edited by Tohatsu on 02-13-2008 04:07 AM
Attachments:
error21.JPG ‏74 KB
config.JPG ‏58 KB
error11.JPG ‏43 KB

I've just found temporary (let's say) solutions:
About my exe:
test editor for cFP, so I have to allow user to set cFP chanel (let's say DO1), set description, and create table of boolean values.
I want to use cFP "Browse" dialog, but:
there is a VI called "FP get Configuration Info.vi" (Functions>>Measurements I/O>> FieldPoint>> Advanced>>cFP Get Configuration Info)
Set path to *.iak file, define configuration name, communication resource (MAX's cFP name) and device name (l.s: cFPAI-111@3) and operation get item list (long string)
It will get us all input adreses at module cFP-AI-111 and next module and so on...
So user will operate at ring or listbox to select cFP channel what is, hmm... proper solution when he isn't connected to cFP at my exe.
Regards
Mikrobi (Zbigniew St. Sobków)____________________________________________________________
"You can lead a horse to water, but if you can get him to float on his back you've got something."

Error-33 building installer

I am done with a project and I am trying to build an installer for it. I have not been successful. I have all the files needed inside the project. I tested it and run the main Vis and there's no error. But when Im trying to build the installer, I select my source files and se the Additional installers to automatic selection I get this error each time:
Forgive me if it's too long! can someone explain to me what that means.
CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> AB_CreateNewWizard_Invoke_CORE.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:MDFDistCopyList_CopyItem.vi
Loading product deployment information
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
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
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Error in MDF:istributionSourceCollection::LoadDist
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\LabVIEW_RT_TraceToolkit_Support_90\LabV90\RTETT_LV_90.msi
Path of part in product: LabVIEW_RT_TraceToolkit_Support_90\RTETT_LV_90.msi
*** End Error Report
Done building deployment

In regards to needing to put in the CDs, LabVIEW will ask you to do so unless you actually transfer the installers to your computer. When you install LabVIEW, it uses the installers on the CD to install to your machine. It won't copy the installer files to your computer by default, as this would waste several GBs of space. You would have to physically copy them from the disk or download them from ni.com/donwloads to get them on your desktop. (This is true for any program, which is why you need installation disks to install or build installers unless you have the installer files on your computer.)
In regards to the error, which XML file in the link I posted previously matched yours? Revision A or Revision B? Can you please post the precise error with Revision A replacing your XML file and the precise error with Revision B replacing your XML file? I would expect the file paths listed to be slightly different.
Could you also post the precise path of the "NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml" file on your computer?
Regards,
David R
Applications Engineer
National Instruments

Building installer [installanywhere]

Similar Messages

Maybe you are looking for