NI Package Builder 20.6 Known Issues

Overview

This document contains the NI Package Builder known issues that were discovered before and since the release of NI Package Builder 20.6. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details

971897

Vague "Could not find file" Build Error Reported when Packed Project Libraries Bitness is Different than Package Builder

Package Builder reports a "Could not find file" error during build if a Packed Project Library's bitness is different than Package Builder's bitness and the versions of LabVIEW and TestStand used by Package Builder. 

Workaround:

Ensure that the library's bitness matches Package Builder's bitness.

Reported Version:

NI Package Builder 19.6

Resolved Version:

N/A

Added:

Mar 31, 2020

985732

After Resetting the Layout, Package Builder Opens Package Editor Panes in a Small Floating Window

Opening a package Editor pane tab by double-clicking on a package in the Packages pane after reseting the layout opens the pane in a small floating window instead of in the Editor pane.

Workaround:

Close solution and reopen.

Reported Version:

NI Package Builder 19.6

Resolved Version:

N/A

Added:

Mar 31, 2020

1096381

Discovery Exclusion of Deployment Utility Directory Fails

The Discovery Exclusion file contains "[TestStand Public]\\Components\\Tools\\Deployment Utility\\.*" in the [Exclude Paths] however adding the C:\Users\Public\Documents\National Instruments\TestStand 2019 (64-bit)\Components\Tools directory as an input item will still pull in the Deployment Utility directory and its contents. 

Workaround:

Replace the "[TestStand Public]" token in the path with the absolute path of the TestStand Public directory on the building system.

Reported Version:

NI Package Builder 19.0

Resolved Version:

N/A

Added:

Nov 14, 2020

1410093

Installers built by Package Builder do not install

Package installers created with Package Builder fail to install when the installer is built on a system with Package Manager 20.7 and the installer includes a package built using Package Manager 20.7.
The installation displays the following message: "A package you selected, or one of its dependencies, requires the latest version of Package Manager to continue with installation."
Package Manager 20.7.1 fixes this issue, and requires rebuilding affected installers.

Workaround:

Install Package Manager 20.7.1 on the build system and rebuilt the installer.

Reported Version:

NI Package Builder 20.6

Resolved Version:

N/A

Added:

May 7, 2021

1436537

Installers built by Package Builder might incorrectly exclude dependent packages

Offline installers built by Package Builder that include packages from NI installers on disk can incorrectly exclude dependent packages, which results in the following error messages during installation: "A required package could not be found: The package 'package-name' requires package 'dependent-package (>= version)' that has an architecture compatible with this operating system."

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI Package Builder 20.6

Resolved Version:

N/A

Added:

May 7, 2021

1461850

Custom executes error during installation when arguments contain quote characters

Package Builder incorrectly creates the instructions file for a package when the arguments for a custom execute contains quote (") characters. The custom execute fails when Package Manager executes the command because quote characters are incorrectly expanded as "&quote;".
For example, configuring a custom execute to call a batch script as shown below returns the error "The executable returned error '1' after running the custom execute command."
    Root: [System (32-bit)]
    Relative Executable Path: cmd.exe
    Arguments: /c ""%Program Files_64%\MyScriptFile.bat" "parameter 1" "parameter 2""

Workaround:

Downgrade to and build the package using Package Builder 20.5.

Reported Version:

NI Package Builder 20.6

Resolved Version:

N/A

Added:

Jul 13, 2021

1367327

Building a local repository incorrectly attempts to download dependent packages from NI when the packages exist in the Package Manager cache

When Package Builder builds a local repository and its dependent packages exist in the cache for Package Manager on the system, Package Builder incorrectly attempts to download the packages from NI, and the build fails if ni.com is not accessible. The resulting error is -16079, "cannot get package dependencies", with the details stating that "the network is down, unreachable, or has been reset. (Could not resolve host: download.ni.com)".

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI Package Builder 20.6

Resolved Version:

N/A

Added:

Jul 13, 2021

1371798

Building a local repository that contains a package with a missing dependency reports an unexpected error

When building a local repository that contains a package with a dependency that is not found, the failing build reports "an unexpected error occurred" and that an "object reference not set to an instance of an object".

Workaround:

Fix the missing dependency and rebuild the local repository.

Reported Version:

NI Package Builder 20.6

Resolved Version:

N/A

Added:

Jul 13, 2021

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

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).