NI Package Builder 19.1 Known Issues

Panoramica

This document contains the NI Package Builder known issues that were discovered before and since the release of NI Package Builder 19.1. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Contents

Document Organization

This table is recommended for use in helping determine if an issue has been reported to us, and is also recommended for users wanting to skim the document to learn of potential issues they may face with Package Builder during development.

Contacting NI

Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.

Known Issues by Date

The following items are known issues in NI Package Builder 19.1 sorted by Date.

135887 If a custom execute references an executable that is not on the system, NIPM does not report that it failed to find it but reports a vague error.
135891 Custom executes cannot perform operations on any files installed to the temporary (%temp%) directory.
135941 You get Error -19024 when building packages in which a TestStand sequence file calls a LabVIEW project that is missing files.
252783 Error -16024 may occur when performing discovery on input directory with a long path.
252770 Adding a Root Drive as an input causes unexpected results
195048 Solution Package shows as external package after clicking Show Additional Sources



ID Known Issue
135887

Return
If a custom execute references an executable that is not on the system, NIPM does not report that it failed to find it but reports a vague error
Package Manager reports "error occurred while installing a package: (pkg). Additional error information: An error occurred while running the custom execute queue 'pre.'

Workaround: To resolve the error, locate the missing executable and update the reference in the custom execute.

Reported Version: 19.0    Resolved Version: N/A    Added: 05/20/2019
135891

Return
Custom executes cannot perform operations on any files installed to the temporary (%temp%) directory.
When NI Package Manager installs files to the Windows temporary directory, the files are immediately removed once installation completes.

Workaround: Use an installation directory that is not the temporary directory if the files are to be used once installation is complete.

Reported Version: 19.0    Resolved Version: N/A    Added: 05/20/2019
135941

Return
You get Error -19024 when building packages in which a TestStand sequence file calls a LabVIEW project that is missing files.
When building a TestStand sequence that calls a LabVIEW project, if that project has any missing items it will give "Error -19024 The following projects are open in the LabVIEW development system. Close all projects before creating a deployment." even though the LabVIEW project is not open.

Workaround: Ensure that any LabVIEW projects called by TestStand sequence files have all of their items and files.

Reported Version: 19.0    Resolved Version: N/A    Added: 05/20/2019
252783

Return
Error -16024 may occur when performing discovery on input directory with a long path
When performing discovery on an input directory that has a very long path sometimes an Error -16024 may be thrown with the following description "An error occurred while discovering dependencies of input files: 'Object reference not set to an instance of an object.'"

Workaround: Simplify the path to the input directory

Reported Version: 19.1    Resolved Version: N/A    Added: 09/25/2019
252770

Return
Adding a Root Drive as an input causes unexpected results
When adding a Root Drive letter as an input item and performing discovery can cause multiple discovery errors, and will not discover all directory contents

Workaround: N/A

Reported Version: 19.1    Resolved Version: N/A    Added: 09/25/2019
195048

Return
Solution Package shows as external package after clicking Show Additional Sources
When adding a package to an Installer or Feed using the Package Selector Drop Down on the installers and Repositories pane, a solution package will display under solution packages initially, but will display under Packages From Other Sources after selecting Show Additional Sources in the drop down.

Workaround: Simplify the path to the input directory

Reported Version: 19.1    Resolved Version: N/A    Added: 09/25/2019

Document last updated on 10/23/2019

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).