This document contains the Package Manager known issues that were discovered before and since the release of Package Manager 20.7. 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 |
|---|---|---|---|
| 1240996 |
Dialog reporting internal error can appear after successfully installing individual packageAfter selecting Open on a package file (.nipkg) in Windows Explorer and installing a package, Package Manager might display an error dialog with the text "An internal error occurred. The PackageTransaction is currently in a Transaction." Workaround: Ignore the error dialog. |
Reported Version: Package Manager 20.6 Resolved Version: N/A Added: N/A |
|
| 1374463 |
A failure to update a feed prevents subsequent feeds from updatingLaunching Package Manager and the top level path or uniform resource identifier (URI) for a feed is invalid in the feed pool, Package Manager displays the message, "Failed to update all feeds", with additional error information "The feed URI '<feed path>\Packages.gz' is invalid." When this error occurs, Package Manager skips updating subsequent configured feeds. Workaround: Correct the top level path or URI for the invalid feed, or remove the invalid feed from the feed pool. |
Reported Version: Package Manager 20.0 Resolved Version: N/A Added: N/A |
|
| 1410093 |
Installers built by Package Builder, LabWindows/CVI and Volume License Manager do not installPackage installers created with Package Builder, LabWindows/CVI, and Volume License Manger 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. Workaround: Install Package Manager 20.7.1 on the build system and rebuilt the installer. |
Reported Version: Package Manager 20.7 Resolved Version: N/A Added: N/A |
|
| 1415193 |
Newly build deployment installers do not installer Win7 32-bitAfter the release of Package Manager 20.7 on April 9, 2021, building 32-bit deployments in LabVIEW, TestStand, NI Package Builder, or LabWindows/CVI on 64-bit OS internet-connected systems create package installers that might fail to install on 32-bit OSes. Attempting to install the built deployment will result in the installer reporting that it is unable to locate ni-package-manager (or other Package Manager packages) with a compatible version and architecture. Note: deployments built before April 9, 2021, are not affected and should still install successfully. Workaround: Refer to the NI KnowledgeBase at www.ni.com/kb/ and enter the title "NI Package-Based Distribution Built on 64-Bit Computer Fails to Install On 32-Bit". |
Reported Version: Package Manager 20.7 Resolved Version: N/A Added: N/A |
|
| 1430830 |
Installers run using --quiet or --passive option fail with error code -125813 when installation requires removal of a packageWhen an installer requires removal of a package during installation, using the --quiet or --passive command line options always fail with error code -125813. Workaround: There is currently no known workaround for this issue. |
Reported Version: Package Manager 20.6 Resolved Version: N/A Added: N/A |
|
| 1436537 |
Installers built by Package Builder and Volume License Manager might incorrectly exclude dependent packagesOffline installers built by Package Builder and Volume License Manager 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: Package Manager 20.6 Resolved Version: N/A Added: N/A |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
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