Ni TestStand-Veristand Patch File

[Mapwar96]

Hi,

     I have to link NI Veristand with the NI Teststand. I'm having trouble installing the "ni-veristand-2017-steps-for teststand_8.1.0.173_windows_x64.nipkg" file using the NI Package Manager. NI package manager showed me some errors. An error screenshot is attached with the query. Please let me know if I missed any documents or other items. On my system, I had previously installed another patch file. That was removed.

[ZYOng]

What is your VeriStand, TestStand and NI Package Manager version?

[Scott_Richardson]

If you are double clicking on the package to install it, the shortcut to invoke NIPM application is likely not working. The command that should be running is:

"C:\Program Files\National Instruments\NI Package Manager\NIPackageManager.exe" install <path to package>

You can always install a single package with no external dependencies using nipkg.exe:

"C:\Program Files\National Instruments\NI Package Manager\nipkg.exe" install --accept-eulas --yes <path to package>

[Mapwar96]

I have the following software versions :

• NI TestStand 2017
• NI Veristand 2017
• NIPackageManager 23.5.0

[Mapwar96]

Hi, @Scott_Richardson I have followed the steps that you are suggesting to me, but still, I am facing the same issue. In the package manager's error log file, I also noticed a few error codes. The error screenshot and the error log file are both attached as attachments.

[Mapwar96]

 Why I didn't see this file on my system?? or shall I download or add it manually from other folder/other sources? 

[Scott_Richardson]

For the nipkg.exe command that I posted on 8/31/2023, it needs to be run in an elevated command prompt. The call to NIPackageManager.exe should prompt for elevation automatically.

[Scott_Richardson]

Regarding the cause of the errors in the log file is likely because of the lack of elevation when calling nipkg.exe because nipkg.exe needs to be able to open the installation database that NIPM maintains.

Regarding the PostInstallAction.exe error, that is caused by the package including an EXE that it schedules to be run at the end of installation, and that EXE for some reason does not exist. I do not have access to the source for that package to suggest next debugging steps.