NI Package Builder 2022 Q3 Known Issues

Overview

This document contains the NI Package Builder known issues that were discovered before and since the release of NI Package Builder 2022 Q3. 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

2029454

Package Builder must exit due to an expected error after dismissing the activation dialog for TestStand

When NI Package Builder requires TestStand to build a package and TestStand is not activated, Package Builder displays an activation dialog for TestStand, and after closing the activation dialog Package Builder reports an unexpected error occurred, and allows you to save the solution file before requiring that the application exit.

Workaround:

Activate TestStand, or select the option "Remind Me When Expired" to prevent Package Builder from displaying the activation dialog during the TestStand trial period.

Reported Version:

NI Package Builder 20.6

Resolved Version:

N/A

Added:

Jun 17, 2022

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

2061233

Building a package with TestStand and LabVIEW files errors on Unicode localized Windows OS

The below error can occur on a Unicode OS, such as Simplified Chinese, when building a solution with a package that contains a TestStand sequence file that calls a LabVIEW code module, and the directory paths to the solution or the files in the package contain Unicode characters.

"Warning 16049: The Package Builder support for TestStand failed to load and has been disabled in this instance of Package Builder.  Error -375003 occurred at Unflatten From JSON in NIPBSupport2017.lvlibp:StageDistribution.vi->NIPBSupport2017.lvlibp:StageDistribution.vi.ProxyCaller."

    Workaround:

    Perform the following steps to enable the "Use Unicode UTF-8 for worldwide language support" OS setting:
    1. Open the Windows Language settings.
    2. Click on the "Administrative language settings" link under "Related settings" to display the "Region" dialog. 
    3. Click "Change system locale..." button to the "Region settings" dialog. 
    4. Check the "Beta: Use Unicode UTF-8 for worldwide language support" checkbox.
    5. Click "OK" to close.

    Reported Version:

    NI Package Builder 20.6

    Resolved Version:

    N/A

    Added:

    Jul 18, 2022

    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:

    Oct 7, 2022

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