SystemLink Forum

cancel
Showing results for 
Search instead for 
Did you mean: 

Package deployment failed through SystemLink

Hi,

 

I tried to deploy an application (Windows 10) that I packetized through SystemLink. After getting past the initial hurdles (finding out which package couldn't be found and add a feed that could contain it) (there should be an easier way to add feeds of package dependencies, hope it's on the road map in the not so far future) it started installing my application, ultimately ending in the following job error:

[
   "Traceback (most recent call last):
File \"C:\\Program Files\\National Instruments\\Shared\\salt\\bin\\lib\\site-packages\\salt\\minion.py\", line 1674, in _thread_multi_return
ret['return'][ind] = func(*args, **kwargs)
File \"C:\\ProgramData\\National Instruments\\salt\\var\\cache\\salt\\minion\\extmods\\modules\
ipkg.py\", line 491, in install
info={'errors': errors, 'changes': ret}
salt.exceptions.CommandExecutionError: Problem encountered installing package(s). Additional info follows:

changes:
----------
ni-daqmx-labview-shared-docs:
----------
new:
17.6.0.49152-0+f0
old:
ni-device-monitor:
----------
new:
17.0.0.49152-0+f0
old:
ni-error-report-x86:
----------
new:
18.0.0.49152-0+f0
old:
ni-error-reporting-interface:
----------
new:
18.0.0.49152-0+f0
old:
17.0.0.49152-0+f0
ni-mxlc-core:
----------
new:
17.5.0.49152-0+f0
old:
ni-opc-support:
----------
new:
17.0.0.49152-0+f0
old:
ni-systemlogging-utils:
----------
new:
18.0.0.49152-0+f0
old:
ni-traceengine:
----------
new:
18.0.0.49152-0+f0
old:
ni-visa-errors:
----------
new:
17.5.0.49152-0+f0
old:
ni-visa-passport-enet-serial:
----------
new:
18.0.0.49152-0+f0
old:
ni-visa-passport-gpib:
----------
new:
18.0.0.49152-0+f0
old:
ni-visa-passport-remote:
----------
new:
18.0.0.49152-0+f0
old:
ni-visa-passport-serial:
----------
new:
18.0.0.49152-0+f0
old:
ni-visa-passport-tulip:
----------
new:
18.0.0.49152-0+f0
old:
ni-visa-passport-usb:
----------
new:
18.0.0.49152-0+f0
old:
ni-visa-shared-components:
----------
new:
5.10.0.49152-0+f0
old:
errors:
- Error -125083: An error occurred while installing a package: ni-ede (17.0.0.49153-0+f1)



Additional error information:

Error -125530: An error occurred while installing the MSI at 'niedei64.msi'.
", false, null ]

The application depends on:

- LV 2016 run-tiime

- Daqmx 18+ run-time with configuration support

- VISA 18+ run-time 

 

A manual try from NI package manager on the target resulted in an installed application that also works like expected including all hardware dependencies.

 

I have noticed it before that a package didn't install right through the SystemLink interface, but could be installed directly from the target's NIPM.

Regards,
André (CLA, CLED)
0 Kudos
Message 1 of 6
(5,375 Views)

Is this issue fixed in the latest version of SystemLink?

Or is it still under investigation?

 

Thanks.

Regards,
André (CLA, CLED)
0 Kudos
Message 2 of 6
(5,299 Views)

I suspect this might have been a glitch during the install process when trying to download the dependencies from ni.com

Was this a one off install? In that case could you retry the install process from SystemLink?

If that does not work, could you try installing the dependencies separately first, to see if the problem is isolated to one of them, and then install the app you created?

 

 

Thanks,

Cosmin.

0 Kudos
Message 3 of 6
(5,295 Views)

Hi Cosmin,

 

Thanks for the reply. I just updated to 18.2. I will keep the issue in mind and report back if I see it again.

Regards,
André (CLA, CLED)
0 Kudos
Message 4 of 6
(5,291 Views)

Try opening the NI Web Server Configuration utility.  Click "Reset to defaults" in both the "NI Alarms and Notification Services" as well as the "NI Dashboard Builder" sections and then click Apply.

 

I would then suggest logging out of the web interface and logging back in to see if that improves things.

0 Kudos
Message 5 of 6
(5,286 Views)

I ran into this same issue recently.  The problem occurs if you don't include ni-certificates since they don't get automatically installed as a dependency, but when not included our silent install fails.

 

If you include ni-certificates when you initially deploy any NI Driver it should work or install it first.

Message 6 of 6
(4,873 Views)