Jump to content

Deleting a key containing values corrupts the installer build specification


Recommended Posts

Hi,

 

I found this bug in LV 2011 SP1 and it was reproduced in LV 2012 by an NI application engineer who filed CAR #385212 for it.

 

Basically, if an installer build specification has values under a key that you've created in the "Registry" section and that you delete the key without having deleted all the values before the build will fail.

The solution is either to recreate all the same keys and values and delete each value before deleting the keys or edit the lvproj file with a text editor to remove all the lines corresponding to the values and keys your want to get ride of.

 

The error I was getting when the build was failing was : 

 

*** Error: An internal tool or library returned an error. (Error code -21)
Error adding registry key:  Name: name_of_value
**************
*** Error Details:
Error in MDF API function: _MDFBuildDevPart_AddRegKey
nmdkAddRegKey returned error code 26051
*** End Error Report

  • Like 1
Link to post
Share on other sites
  • 6 months later...

Thank you for reporting this Antoine - this answered my problem and I got the installer build fixed!

I solved this the second way, went to the lvproj file. It may be helpful to know that the lines you must be looking for will contain some of these strings:

<Property Name="RegDest[0]

<Property Name="RegDestCount"

<Property Name="RegGroup[0]

<Property Name="RegGroupCount"

-- by deleting all the properties starting with these tags I was able to get a working installer build.

You want to take a backup of the project file first of course :thumbup1:

Edited by JaakkoK
  • Like 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Jim Kring
      [Update: NI Bug 974336]
      There seems to be a bug in the coercion of data to variant when a cluster contains a single element that is a variant. (original post here).
      Note: This bug appears to be very old, going as far back as LV2012. This has been reported to NI in the LV2020 Beta forum. I don't have a Bug ID / CAR yet.
      Coerce to Variant Fail (LV2019).vi


       
      Note that adding another element to the outer cluster causes the problem to go away.


    • By ShaunR
      Maybe others have seen this but I only became aware of it recently so I apologise if there is already a CAR for it.
      The following demonstrates a difference in behaviour between LabVIEW 2017 and previous versions (back as far as 2009, maybe further).
      The VI registers an event when it starts (in the timeout case) and generates a user event when the Increment button is pressed.
      The expected behaviour is that the counter will increment by one every time the button is pressed. This is the case for LabVIEW versions prior to 2017. In 2017, the user event is never fired, nor is there an error emitted by the generate user event.
      To get the VI to operate as expected in 2017; change the event refnum tunnel to a shift register. This seems to indicate that the refnum prototype is stomping on the dynamically allocated reference whereas in previous LabVIEW versions it would not. Note also, that when using the shift register, the cases do not need to be "wired through" as would be expected with similar functionality in a normal case statement.
      evnt.vi
    • By A Scottish moose
      Hey everyone,
       
      I am working on a backup function for a test executive.  The backup uses the 'class to XML' vi to create an XML string and then save it to a file to be reloaded later. All of my test specific information lives in the class (or one of it's children).  I like this functionality because it makes backup and reload brainless.  It just works.... until now... I've got a test class for my current tester that's grown rather large.  Everything works fine, until the tester loads some waveform data into either of the waveform arrays.  Without data in this field the class reloads just fine, otherwise if fails and says the XML is corrupted.
       
      As you can see in my backup vi I have built in a work around that flattens the waveform arrays to strings, drops them back into the class private data, deletes the waveform arrays and then writes the class.  This works! Much to my surprise both waveform data and the rest of the class data are written to file and reloaded without error.  
       
      Does anyone have any knowledge or experience with this? 
       
      Cheers,
       
      Tim


    • By Stobber
      If I create a DVR in a dynamically launched VI, the DVR ref goes stale when it's passed back to the caller. Anybody know why? See the attached code (LV15) for an example.
      I don't want to use the ACBR node right now because I want to set some control values of the VI ref on a different diagram than the one that will run it. (I just want to pass the VI ref between calling diagrams, not all the values that'll be passed into it.)
      DVRtest.zip
    • By drjdpowell
      OpenG’s Trim Whitespace fails on a string of all whitespace, if set to trim the front only.   It returns the last whitespace character.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.