NI Package Manager (NIPM)

cancel
Showing results for 
Search instead for 
Did you mean: 

Error installing NI-XNET 20.5.0 package

Hello,

 

I've been having a stubborn problem with installing VeriStand 2020 on my work laptop. Specifically, the download fails when it reaches the portion where it tries to install XNET 20.5.0. I've experienced this while running both the online and offline installations.

 

az143_0-1609786981658.png

 

I've copied snippets from the NIPM and MSI error logs below:

 

Exception in ni::pkgclient::TransactionBase::StartInternal. Error code: -125083
Request type: 30
-125083: An error occurred while installing a package: ni-xnet-runtime (20.5.0.49567-0+f415)
File: source\nipkg_client\pkgclient\PluginInteraction.cpp
Line number: 258

Additional error information:
-125530: An error occurred while installing the MSI at 'xnetRuntime64.msi'. Service 'NI-XNET IP Stack' (nixntipstackd) failed to start. Verify that you have sufficient privileges to start system services.
File: E:\dev\_r\1\nipkg\source\shared_agents\WinInstall/ErrorHandler/ErrorInfo.h
Line number: 102

 

11:16:36.400968 WIA: About to install MSI | path: C:\Users\z#m14028\AppData\Local\Temp\nipkg-e41d-318c-ca0e-2eb1\data\xnetRuntime.msi | cmdLine: REBOOT="ReallySuppress" PROMPTROLLBACKCOST="D" NIMETALANGID="9" NIPKGLAUNCHED="1" NIINTERNETCONNECTEDTOMICROSOFT="YES" NIRUNNINGINSILENTMODE="" NIPKGPROCESSID="9964" NIPMLANGUAGECODE="en" REINSTALLMODE="vemus"
11:16:49.966247 WIA: MSI installation is complete | returnCode: 3010 | path: C:\Users\z#m14028\AppData\Local\Temp\nipkg-e41d-318c-ca0e-2eb1\data\xnetRuntime.msi
11:16:49.966247 WIA: About to install MSI | path: C:\Users\z#m14028\AppData\Local\Temp\nipkg-e41d-318c-ca0e-2eb1\data\xnetRuntime64.msi | cmdLine: REBOOT="ReallySuppress" PROMPTROLLBACKCOST="D" NIMETALANGID="9" NIPKGLAUNCHED="1" NIINTERNETCONNECTEDTOMICROSOFT="YES" NIRUNNINGINSILENTMODE="" NIPKGPROCESSID="9964" NIPMLANGUAGECODE="en" REINSTALLMODE="vemus"
11:17:37.733619 WIA: Detailed error message from MSI Engine: Service 'NI-XNET IP Stack' (nixntipstackd) failed to start. Verify that you have sufficient privileges to start system services.
11:17:43.466745 WIA: MSI installation is complete | returnCode: 1603 | path: C:\Users\z#m14028\AppData\Local\Temp\nipkg-e41d-318c-ca0e-2eb1\data\xnetRuntime64.msi
11:17:43.467746 WIA: MSI installation failed | returnCode: 1603 | path: C:\Users\z#m14028\AppData\Local\Temp\nipkg-e41d-318c-ca0e-2eb1\data\xnetRuntime64.msi
11:17:43.467746 WIA: About to remove (rollback) MSI | path: C:\Users\z#m14028\AppData\Local\Temp\nipkg-e41d-318c-ca0e-2eb1\data\xnetRuntime.msi | cmdLine: REBOOT="ReallySuppress" PROMPTROLLBACKCOST="D" NIMETALANGID="9" NIPKGLAUNCHED="1" NIINTERNETCONNECTEDTOMICROSOFT="YES" NIRUNNINGINSILENTMODE="" NIPKGPROCESSID="9964" NIPMLANGUAGECODE="en" REMOVE=ALL
11:17:59.207085 WIA: MSI removal (rollback) is complete | returnCode: 0 | path: C:\Users\z#m14028\AppData\Local\Temp\nipkg-e41d-318c-ca0e-2eb1\data\xnetRuntime.msi
11:17:59.207085 WIA: Error -125530! An error occurred while installing the MSI at 'xnetRuntime64.msi'. Service 'NI-XNET IP Stack' (nixntipstackd) failed to start. Verify that you have sufficient privileges to start system services.\|\|Details:\|MsiInstallProduct returned 1603.\|An error occurred in OnTransactionStep for transaction type 'install'.\|\|Error Context:\|NIPkg::Agents::WinInstall::Installer::Install: Installing a package\|NIPkg::Agents::WinInstall::Installer::InstallWIAPackage: Installing a WIA package
11:17:59.331086 FA : ===== API BEGIN OnTransactionEnd ==========
11:17:59.332089 FA : [ BEGIN == Running 0 custom executes in postall queue in the following order. ]
11:17:59.332089 FA : [ END == Done running custom executes ]
11:17:59.333088 FA : About to close database
11:17:59.351087 FA : Done closing database
11:17:59.351087 FA : ===== API END OnTransactionEnd ==========
11:17:59.351087 WIA: ===== API BEGIN OnTransactionEnd ==========
11:17:59.351087 WIA: RunCustomExecutes() called to run queue 'postall'. Skipping because there are no custom executes to run.
11:17:59.352088 WIA: About to close database
11:17:59.369087 WIA: Done closing database
11:17:59.369087 WIA: ===== API END OnTransactionEnd ==========
11:17:59.369087 RFA : ===== API BEGIN OnTransactionEnd ==========
11:17:59.371086 RFA : About to close database
11:17:59.387087 RFA : Done closing database
11:17:59.387087 RFA : ===== API END OnTransactionEnd ==========
11:17:59.401087 CLILIB: An error occurred while installing a package: ni-xnet-runtime (20.5.0.49567-0+f415)

 

What's curious is that the logs seem to be calling out an insufficient privileges issue despite the fact that I've run the installer as admin on an admin account as well as a regular user account. I'm really hoping there is a solution besides re-imaging my laptop.

 

Any help would be greatly appreciated!

 

-Gil

0 Kudos
Message 1 of 10
(3,495 Views)

I am having the same issue as well. Did you ever find a fix/workaround?

0 Kudos
Message 2 of 10
(3,372 Views)

Sorry for the delay in replying. We are aware that some people are encountering this issue but have been unable to reproduce this in house and haven't been able to communicate a workaround. 

 

As the original poster's logs show, at the end of the installation process the XNET installer attempts to start a service. On some systems that fails because of missing permissions. As far as I understand this failure triggers rollback of the installation so ignoring it and rebooting isn't an option.

 

We don't yet know why those permissions would be missing or how to restore them. If your PC is managed by an IT department, our best guess is that it is a policy applied by them. If you can confirm that, please share back in this thread what that policy is. 

 

We intend for all NI software to install without unusual permissions and are working on a fix to install successfully in this scenario. I don't have a timeline yet for when that will be available. If you are unable to adjust the permissions your only certain solution is to roll back to XNET 19.0.

 

As a sanity check, could you open an command prompt as administrator and try something like:

net stop spooler

 

If that fails with "System Error 5" that would at least confirm that you don't have service management permissions as an administrator and further confirm root cause.

 

Sorry for any frustration this is causing.

NI Software Engineer - RIO
0 Kudos
Message 3 of 10
(3,286 Views)

CORRECTION: You can roll back to XNET 20.0 to address the issue. This issue was introduced in XNET 20.1. 

NI Software Engineer - RIO
0 Kudos
Message 4 of 10
(3,261 Views)

I encountered this error with the same XNET 20.5 package and others (Diadem 2019 and up, some versions of LV Runtime, etc.).

 

The issue is that some NI installers are setting up their services to use their own log on accounts (e.g. NI LXI Discovery service log on is NT SERVICE\niLXIDiscover). My IT department (and presumably others) has a policy blocking the NI installer from starting services that use these log on accounts.

 

The only workaround I've found is to manually change the service account to "Network Service". This is a service account built into Windows. This works until the next NI update that resets the service account back to "NT Service\...".

 

This workaround does not work if the installer tries to start the service as part of the install process. Since that causes a rollback, I cannot manually change the new service to use the "Network Service" account. If the installer does not try to start the service, the install presumably will succeed and I can edit the service account log on before starting the software.

Message 5 of 10
(3,126 Views)

Thanks for sharing that information and workaround. We are actively working on a solution that will address the install process. We'll have to take a look at that service account problem. Do you happen to know how that IT policy is applied? If it's a domain policy, which one?

NI Software Engineer - RIO
0 Kudos
Message 6 of 10
(3,103 Views)

It's a domain Group Policy. See the attached presentation with my findings/research (this was from the DataFinder service failing to start, but I assume this is also the root cause of the XNET driver failing to install).

Message 7 of 10
(3,093 Views)

That is the same issue I had as well after I had to rollback to install FlexLogger 2020R2. I noticed that it tried to log in as NTService\... for the NI PSP Service locator, at I had to change the NTservice to a local service. I suspected that it was doing the same thing in the install for XNET as well. Is there any type of timeline for NI to have a workaround or fix to resolve the install issue?

Message 8 of 10
(3,039 Views)

The installer fix should be public by the end of this month as XNET 20.5.1

 

The fixed installer will still create a "Virtual Service Account" for each service but wont attempt to start any of them which will allow installation to complete. We are still evaluating options for environments where those accounts are blocked from running tasks.

NI Software Engineer - RIO
0 Kudos
Message 9 of 10
(3,033 Views)

For anyone using VeriStand that was running into this NI-XNET installation error, VeriStand 2020 R5 includes the NI-XNET 20.5.1 patch. VeriStand 2020 R5 is now installable from NIPM and ni.com

 

VeriStand 2020 R5 also includes various new features, some of which are described in the manual

Brian.D
NI Product Owner
VeriStand
Message 10 of 10
(2,867 Views)