Home Support Documentation Bugs

NI Package Builder 2022 Q3 Bug Fixes

Created Jun 22, 2023

Overview

The following items are notable issues fixed between the release of NI Package Builder 20.6 and NI Package Builder 2022 Q3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI Package Builder.

Bug Number

Legacy ID

Description

Details
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:

NI Package Builder 2022 Q3

Added:

May 5, 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:

NI Package Builder 2022 Q3

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:

NI Package Builder 2022 Q3

Added:

Jul 13, 2021
2143723

Package Builder reports error when building a package using TestStand 2021 and LabVIEW 2019 and newer

Building a package reports the below error if the package contains a TestStand sequence file with steps that call LabVIEW code modules, and Package Builder uses TestStand 2021 and LabVIEW 2019 and newer.

"Error -16048: Error occurred during staging in the Package Builder support for TestStand. LabVIEW: (Hex 0x623) You cannot open a packed library saved in a version earlier than the current version of LabVIEW."

Workaround:

This issue is fixed in NI Package Builder 2022 Q3 Patch 1.

Reported Version:

NI Package Builder 2022 Q3

Resolved Version:

NI Package Builder 2022 Q3 Patch 1

Added:

Nov 18, 2022

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

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