Package Builder Error -16078: Cannot get packages from NI Package Manager cache.

[MOBA-User]

1. I attached the file.
2. Poorly it is a complex solution, so at the moment it runs only on my Laptop. We are going to set up a virtual machine to build our solution in the next few weeks.
3. I don´t think so. Most of them are files on my Laptop. (What do mean with symbolic links?)
4. I´m using a normal Windows User with Admin-Rights

5. That was a good idea. (Why didn't I think of that?) Our package TS_Public caused the error, so i started to remove some of the dependencies. It seems the missing package is the 'Labview Runtime (64-Bit)' Version 17.6.4.49153-0+f1. Oddly enough i could find it under 'Add dependencies...' -> Installed Packages. Also the package manager got it in its List.
We need this runtime to run some of our older tests on the test system.

Thanks for your help.

[MOBA-User]

Okay, the reinstalling of this package don't solve the error. It is still missing when i try to build the repository...

[Scott_Richardson]

Looking at the list of packages in your C:\ProgramData\National Instruments\NI Package Manager\packages directory, I do not see the ni-labview-2017-runtime-engine package and some of its dependencies. I do see it in the .\downloads directory which is likely from the building of the installer.

You could execute the following two commands to download the packages from the ni.com feed. The first command may fail if the feed is already registered with that URL. Let me know if it fails or not. The second command will download the packages directly to the NIPM directory. After downloading packages, you could try the build of the repository again. If still fails, see if the error log contains any more details, and try to eliminate solution content to see if the failure is the same or some other dependent package.

Commands:

nipkg.exe feed-add --name=LV2017 https://download.ni.com/support/nipkg/products/ni-l/ni-labview-2017-runtime-engine/17.6/released

nipkg.exe download -all-deps --destination-dir="C:\ProgramData\National Instruments\NI Package Manager\packages" ni-labview-2017-runtime-engine

[MOBA-User]

Okay, after the two commands (btw. there is a '-' missing in the second one) the runtime package is in the packages folder. Now the error is:

===== 2023-Jul-18 08:06:04.214121 =====
Exception in ni::pkgclient::TransactionBase::StartInternal. Error code: -125024
Request type: 26
-125024: Datei kann nicht geöffnet werden: \\?\C:\Users\Public\Documents\Test\MATS2 Repository (13)
File: source\nipkg_client\pkgsolv\Checksum.cpp
Line number: 57

(File could not be opened)

If i remove the dependencie 'LabVIEW Runtime (64-bit)' Version: 17.6.4.49153-0+f1, it build the repository.

[Scott_Richardson]

Sorry for the delayed response. Still very confused on this still. I did notice that you recently installed NIPM 23.5.

1. Can you run the command "nipkg list-installed" and share the output?
2. Could you share the NIPM log file (%localappdata%\National Instruments\NI Package Manager\Logs\NIPkgLogs\NIPkgLog*.txt) associated with the failure to build?

[MOBA-User]

Hi,

don´t worry about the delay. Since we found the missing package, it is not longer top priority. Here are the two requested files.

Thanks for your help.

[Scott_Richardson]

OK, I compared the packages.txt file to the installed.txt file and I am see no packages missing in the cache for the dependency list of LabVIEW 2017 64-bit runtime.

I am seeing a new error -125002, which is an invalid handle, which appears to be different than what we saw before.

Asks:

1. Can you share in %localappdata%\National Instruments\NI Package Manager\Logs\
   1. errorlog.txt
   2. UnhandledException.log
2. You said, "Since we found the missing package, it is not longer top priority", so is knowing that the runtime is related to the error somehow allowing you to workaround something about this build?

For completeness, below are the missing packages from the cache that are installed, but are not dependencies of the LabVIEW 2017 64-bit runtime:

• ni-assistant-framework-labview-2014-support_17.0.0.49153-0+f1
• ni-assistant-framework-labview-2014-x86-support_17.0.0.49153-0+f1
• ni-assistant-framework-labview-2015-support_17.0.0.49153-0+f1
• ni-assistant-framework-labview-2015-x86-support_17.0.0.49153-0+f1
• ni-assistant-framework-labview-2016-support_17.0.0.49153-0+f1
• ni-assistant-framework-labview-2016-x86-support_17.0.0.49153-0+f1
• ni-assistant-framework-labview-2017-codegen-x86-support_17.0.0.49153-0+f1
• ni-assistant-framework-labview-2017-support_20.0.0.49152-0+f0
• ni-labview-2015-runtime-engine-resource_15.1.1.49152-0+f0
• ni-labview-2015-runtime-engine-x86_15.2.0.49153-0+f1
• ni-labview-2017-runtime-engine-resource_17.1.0.49154-0+f2
• ni-labview-2017-runtime-engine-x86_17.5.1.49152-0+f0
• ni-labview-2017-scripting-codegen-x86_17.0.0.49152-0+f0
• ni-lv-web-server-labview-2015-runtime-engine-x86-support_15.0.1.49152-0+f0
• ni-lv-web-server-labview-2017-runtime-engine-x86-support_17.0.1.49152-0+f0
• ni-mkl-2015_15.0.1.49152-0+f0
• ni-realtime-nbfifo-labview-2015-support_15.0.1.49152-0+f0
• ni-ssl-labview-2015-runtime-engine-x86-support_15.0.1.49152-0+f0
• ni-ssl-labview-2017-runtime-engine-x86-support_17.0.1.49152-0+f0
• ni-vipm-helper_17.0.1.49152-0+f0
• ni-vipm_17.0.2.49153-0+f1
• ni-web-pipeline-17.0_17.0.0.49152-0+f0

[MOBA-User]

There are only the attached files in %localappdata%\National Instruments\NI Package Manager\Logs\ 

The Workaround is to install the Labview Runtime manually and remove it from the repository. 🙂

[Scott_Richardson]

1. Can you share the file listing of the repository output directory after a build failure? I want to see what has been copied to the directory prior to the error occurring.
2. Can you share the WinInst package database located here: "C:\ProgramData\National Instruments\NI Package Manager\Agents\wininst\installed.dat"?

If the above does not yield more information, we might have to rely on adding additional logging to one of our NIPM DLLs for you to use.

[MOBA-User]

Hi,

here are the two requested files. I had to add the .dat-File to a .zip-archiv.

Still thanks for your help.