LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

SDK Error -12 in Build Distribution Kit

Solved!
Go to solution

Build Distribution Kit fails with SDK Error -12 when I try to build a distribution that needs non-cached file (see attachments). The build succeeds if it is pared down to where it does not need any files from a CD or DVD. 

 

Operating system is Vista 64.  CVI is version 2009. 

 

Tested on a different machine with XP SP2 and CVI 2009 with same Error results. 

 

This is a project that i have built many times in recent versions of CVI but not yet in version 2009. 

 

LabView indicates SDK Error -12 during a build may be due to virus protection or to to net Framework earlier than 3.0.  I checked the net Framework version, its OK, so I temporarily un-installed virus protection but the problem persists.

 

Download All
0 Kudos
Message 1 of 11
(5,168 Views)

Immediately after you run into this error, please check your temp directory (e.g. c:\users\<username>\AppData\Local\Temp) for a file named distBuildDbg.log and post it back here. Also, could you try building your distribution with only NI USI or NI Distributed System Manager selected? If you can build with one of these, it would indicate something specific to the driver/component that you're actually trying to build with.

 

Mert A.

National Instruments

0 Kudos
Message 2 of 11
(5,160 Views)

Here is the log. After reading the log, I looked for the file LION05\Data\Eng_Control\Elite LabVIEW Driver\distribution\Volume\bin\p28\LVBrokerAux71\LVBrokerAux71Deu.mst. It is not at that location was not found in a search of the bin directory.


Since it appeared that the problem occurred in a an instrument driver that I created (and have used successfully for many years), I uninstalled the driver and then reinstalled it. The same problem occurred.


It is interesting that this problem appears differently if I pare down the install. I selected Runtime5 rather than the FULL DAQmx and the build reportedly succeeded while using some files from the DAQmx August 2009 DVD. A copy of that build log is also attached. Curiously, the same file was not found and threw a similar error into the error report, but the build reported success.


I don't know what is meant by NI USI or NI Distributed System Manager so i need a little more guidance to complete those steps.

0 Kudos
Message 3 of 11
(5,085 Views)
The logs are quite large to the message failed to post with both attahced.  Here is the log from the failed build with the extension changed to txt.
0 Kudos
Message 4 of 11
(5,080 Views)
The build log from the reportedly successful build it too large to attach (13+Megs).  I can make if available by ftp if you really need it.
0 Kudos
Message 5 of 11
(5,077 Views)

Search the following directory for any files with "broker" in the name, and please zip them up and post back here:

 

[Program Files]\National Instruments\Shared\MDF\Manifests

 

It may be that you ended up with a bad version of the 7.1 Broker Aux manifest file.

 

Mert A.

National Instruments

0 Kudos
Message 6 of 11
(5,047 Views)
Here are the Broker files.  The Build logs are also in the zip.
0 Kudos
Message 7 of 11
(5,037 Views)

The log that had the successful build actually had information from seven different builds, some which were failures, which is why you saw the error in that log, too. If the error occurs, it always causes a build failure. The error comes from trying to copy LVBrokerAux71 (which is a dependency product) into your distribution. It is a dependency of the full DAQmx product, but not the Runtime 5 flavor.

 

The manifest for LVBroker71 (NI LVBrokerAux71 {36DC540B-3062-4538-B1D1-E367BC9F47FC}.xml) specifies that three language transform (.mst) files ought to be found next to the .msi file. CVI tries to copy LVBroker71 from your Elite LabVIEW Driver distribution, but for some reason, the transforms are not present in that distribution. I have no idea why that might be. Is it possible someone manually deleted all of the other language transform files to make the distribution smaller, thinking that no other languages would be needed?

 

In any case, I've attached the three .mst files that are needed. If you put these in the \\LION05\Data\Eng_Control\Elite LabVIEW Driver\distribution\Volume\bin\p28\LVBrokerAux71\ directory, it ought to solve your problem.

 

Mert A.

National Instruments

0 Kudos
Message 8 of 11
(5,023 Views)

Mert,

 

That solved the problem.  Thanks much for your help.

 

I do feel some frustration with this.  First, this project did build successfully on a previous version of CVI.  It is extremely unlikely that the missing files were removed.  I am the only one at this company that might do that.  Also, I'm frustrated that I need to keep a pile of DAQmx CDs and DVDs at hand to feed every new build that I do.  I always cache the needed files but inevitably a new file will be required from a CD months and sometimes years old. 

 

Once again.  Thanks for your help. 

0 Kudos
Message 9 of 11
(5,017 Views)
Solution
Accepted by topic author CreviceDweller

I can appreciate your frustration, so I'll see if I can offer some explanations and suggestions.

 

If the distribution built fine previously, either LVBrokerAux71 was not being included, or it was being sourced from a different distribution that had all the language transform files. The first case could be true if you added or changed the flavor of DAQmx you are packaging in. From the sounds of it, that's not the situation. The latter case could occur based on new components being installed on the system, affecting the source selection algorithm.

 

Presumably, if you're caching all the required parts when you build, you shouldn't need to keep any disks at the ready for the most builds. Only when you select new/additional products for inclusion in your distribution, or install/upgrade NI software/drivers on the system could you be required to provide different disks. Many times we have heard frustration about keeping old disks around, but without some sort of automatic driver download framework (unfortunately doesn't exist), it's the only way to make sure you're distributing the same stuff that's installed on your system. Since you're using version 2009, you should at least be getting a distribution selection dialog at the beginning of the build that gives you some flexibility in the disks you have to provide. 

 

Glad to hear you're fixed up now. Please mark the thread "solved," if that is the case. Thanks.

 

Mert A.

National Instruments

0 Kudos
Message 10 of 11
(5,011 Views)