LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI Error Reporting Interface 15.0 error when creating a LabVIEW 2014 installer package.

Solved!
Go to solution

I looked into this some more and the screenshot that I provided above is what's to be expected as 2014SP1 is from the 2015 disk set.  However, VIPM was the only NI related update that I had performed between the last time I built an installer and the present.

 

As I said, adding a 2015 RTE installer to my existing installation will not be accepted by my customer, so I have to find a way to roll this back.  Any input is appreciated.

0 Kudos
Message 11 of 24
(3,846 Views)

Yes, that did the trick for me.   Sí, eso hizo el truco para mí.

0 Kudos
Message 13 of 24
(3,711 Views)

Ran into this issue using LabVIEW 2012, upgrading is not possible so I'm stuck with LV2012.  I am upgrading a utility we distribute and during the installer build ran into this problem.  In another thread a poster mentioned they un-installed the JKI libraries and their problem went away.  That also is not an option since the previous programmer used the JKI libraries in the app.

 

The solution posted was to download the LV2015 RTE and install it, problem would be solved.  Not wanting to install a bunch of un-necessary components I took a slightly different approach.

 

1) Download the LV2015 RTE

2) Open the installer and when the WinZip window opens, un-check the "Run Setup" checkbox to prevent the install.

3) Navigate to the install folder, in my case it was

   C:\National Instruments Downloads\LabVIEW\Run-Time Engine\2015 (32-bit) f3 Patch\Standard\Products

4) Navigate into the \LabVIEW_Error_Report\ni_error

5) Double click ni_error_report.msi to install the missing component

6) Rebuild the target installer

7) Celebrate with a donut.

 

 

 

Posting to help the next guy who has his hands tied like me...

 

 

 

 

Message 14 of 24
(3,645 Views)

Great news Steve for sharing this shortcut....

The thing that I just don't understand is why this issue is there in the first place ?..

 

Any way enjoy your donut !! 😊

.donut platter.jpg

0 Kudos
Message 15 of 24
(3,638 Views)

I'm using Labview 2013 environment and trying to create an installer package also and I'm getting the same error. The solutions presented so far have not worked and I'm really trying to avoid uninstalling and reinstalling Labview. I'm not sure that will even fix the problem. This must be an NI bug in the installer. There should be a real solution for this from NI.

0 Kudos
Message 16 of 24
(3,610 Views)

The LV2015 runtime engine didn't work for me either.

 

Why isn't there just an installer for the NI Error Reporting Interface 2015?

 

I tried my LV2015 DVD and it's not on there, apparently. The downloaded installers mentioned above won't be accepted by the application builder. If I uncheck all the MAX5.5 related stuff, it stops asking for this. Maybe I just never built an EXE on this machine since I upgraded to MAX 5.5? Maybe I can use the MAX installer for this? But the device driver DVD wasn't accepted either.

 

I have every NI SSP 2015 DVD, but none of them have this installer?

 

I don't even want or need this stupid feature anyway. My target computer isn't even on the internet.

0 Kudos
Message 17 of 24
(3,280 Views)

I just purchased the Home Version, which is the 2014 LabVIEW version, and am running into this same problem. I have tried the LabVIEW_Error_Report "fix" from above, and am still getting the same error.

 

I was initially impressed that the Home version came with the builder. Now, not so much. I cannot imagine someone new to LabVIEW going through this, and seeing the lack of a solution in a three-year-old product is discouraging.

0 Kudos
Message 18 of 24
(3,235 Views)

Wow, Forgot to follow up with this thread, sorry about that... yeah the first time I built it, the error did not repeat so I figured it was good to go... that was not the case.  I did track this down to trying to include a USB-8451 driver (I2C module) with the installer.  Every time it would give me that error.  So the fix was to build it without it and pack the driver (zip) it with the installer.  As usual the clock was ticking so I had to keep moving forward.

 

I had 2 apps I built for distribution and did not have an issue when just distributing the app (no additional installers).  Hope this helps...

0 Kudos
Message 19 of 24
(3,211 Views)

Buena solución,

 

Yo he instalado el LabVIEW Run-Time Engine 2015 SP1 f11- (32-bit) 

que se encuentra en el siguiente link ( http://www.ni.com/download/labview-run-time-engine-2015-sp1/5841/en/ ) y me ha ido de maravilla.

 

Saludos

0 Kudos
Message 20 of 24
(2,555 Views)