10-13-2010 03:18 PM
I had an executable and installer working that were built in LV2009. Since then I modified my source code and saved as LV version 2010. I rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that LV Runtime Engine 2010 was needed. So I tried to rebuild the installer using LV Runtime Engine 2010 as an Additional Installer. However, this build was unseccessful and I got a lenghty error msg that I don't understand (see attached).
Thanks in advance.
Solved! Go to Solution.
10-14-2010 12:48 PM
Check this KnowledgeBase article out... There's a couple possible solutions listed. Let us know if these don't work.
SDK Error Code -12 When Building a LabVIEW Installer or Installing LabVIEW
http://digital.ni.com/public.nsf/allkb/afc375154efbd6ae8625760b005fb723
11-17-2010 04:01 PM - edited 11-17-2010 04:03 PM
There are apparently other reasons for this to happen. This is on a 32 bit Windows XP system. I've installed the required libraries in the machine the builds are being created on. What am I missing here? The binary bit builds but the installer refuses to complete with the following error:
DK_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
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'Compressed Air System Panel' from: C:\Documents and Settings\pqladmin.PQLTEST\My Documents\builds\Compressed Air System Panel\Compressed Air System Installer\Volume\ 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 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
11-18-2010 12:54 PM
Couple troubleshooting ideas...
Do you have .Net 3.0 or later installed?
Do you have any virus/security software running?
Can you build any application or installer for a simple project?
Do you have any other security restrictions on your PC or network?
What version of LabVIEW is this in?
11-18-2010 01:38 PM
Couple troubleshooting ideas...
Do you have .Net 3.0 or later installed? >>>> Yes. The machine has 3.0 SP2 and 3.5 SP1 installed.
Do you have any virus/security software running? >>>>No.
Can you build any application or installer for a simple project? >>>>There are several projects in the same directory that have been built and seem to work fine.
Do you have any other security restrictions on your PC or network? >>>> No. This is using a local and network-wide admin account.
What version of LabVIEW is this in? >>>> LabVIEW 2010.
11-19-2010 08:40 AM
This Line:
"Copying distribution 'Compressed Air System Panel' from: C:\Documents and Settings\pqladmin.PQLTEST\My Documents\builds\Compressed Air System Panel\Compressed Air System Installer\Volume\ to: C:\Documents and Settings\All Users\Application Data\National Instruments\MDF\ProductCache\"
stood out since the compiler is pulling data from a folder asociated with another project rather than the one associated with with it." "Compressed Air System" is another project altogether. Why would the project file do this? Do I need to recreate the project altogether? Is the project file corrupted in some way? There is a project called "Compressed Air Panel" but the project I was trying to build was the "T5000 Client" project.
11-19-2010 09:13 AM
You may have accidentally cross-linked files in your project. It can happen when you are working on one project, realize you have already written a subVI in other project that will help you. You go and copy that to your current project, perhaps even rename it, but fail to copy over its subVI's, or use a copy of it while LabVIEW still thinks it is in the other project file's directory. Maybe the other project was open at the same time. It's hard to say.
You need close everything out on your PC. Only open the current project. Look for that VI in the VI hierarchy to see what VI's call it. One of them probably need to be updated to point to the correct location.
A good option is before you open your current project, temporarily rename the other project's top directory to something else. That way when you open the current one, any VI's looking for subVI's in the wrong project will fail to find the subVI and open broken. Then you can go and update the broken VI's so they point to the correct subVI.
04-04-2011 04:10 AM
04-04-2011 09:58 AM
I think the cross-link issue is present here also. In my case the issue was that the installer build was attempting to install components that were part of the old code that were not there. Make usre that you have opened and recompiled each sub-vi separately and that they work on their own if if the original code was created on a prior version of LabVIEW. This makes sense since if the builder sees the older compiled code as a reference within the project it may or may not know what to do withit without a complete recompile of the entire project as part of the dependancy tree. LabVIEW is pretty smart about these things if the project has a complete depedancy list but it can't figure out nested depths deeper than a single layer of dependancies or so any more than most compilers can. Make usre that the components that are included as given by the picture are all needed. The more complex the includes becomes the more likely you are to hit a snag.
04-05-2011 02:25 AM
Hi EWTech,
Thanks for your prompt reply. I have compiled all my code and saved. Still I see the similar issue. Here is the history of installation, I installed LV2010 first. midway through the development, I have upgraded to LV2010 SP1. I just downloaded the SP1 for LabVIEW only and installed.
"Copying distribution 'LabVIEW 2010 Service Pack 1 (SP1)' from: C:\National Instruments Downloads\LabVIEW\2010 SP1\ to: C:\ProgramData\National Instruments\MDF\ProductCache\"
From the above message (see below for entire message). LabVIEW is looking for the source of the runtime installer from C:\National Instruments Downloads\LabVIEW\2010 SP1\ . I can see the setup.exe available in this location. But still LabVIEW error says it can not find the path specified. I tried to reinstall SP1 also, but It did not work
-------------Here is the error message:----------------------
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 informationLoading product deployment informationLoading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'LabVIEW 2010 Service Pack 1 (SP1)' from: C:\National Instruments Downloads\LabVIEW\2010 SP1\ 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_CopyItemWindows function FindFirstFile returned an error. Error code: 3*** End Error Report************** Done building deployment
----------------------------------------------------------------------------------------------