NI Package Manager (NIPM)

cancel
Showing results for 
Search instead for 
Did you mean: 

An error occurred while installing the MSI at 'nisystemlink_message_brokeri.msi'.

Ragman --

 

I strongly suspect that the issue is NOT with the version of NIPM, but rather the version of GWeb.  Specifically there were a couple versions of that NI-systemlink-mesage-broker that had this issue or similar issues -- specifically around the 2022-2023 time frame.  For the most part the packages are self-contained lists of instructions, which will operate the same regardless of the NIPM version installed (with minor exceptions).  This particular package had an issue, so it won't matter what version of NIPM you use.

 

I believe the SystemLink Message broker is a "core component" of the GWeb, so add-ons would not effect whether this gets installed or not.

 

Take a look at specifically my posts earlier in this thread, and it should provide some guidance on what some of the issues might be. Specifically here:

https://forums.ni.com/t5/NI-Package-Manager-NIPM/An-error-occurred-while-installing-the-MSI-at-nisys...

and 

https://forums.ni.com/t5/NI-Package-Manager-NIPM/An-error-occurred-while-installing-the-MSI-at-nisys...

what the error might be.

 

 

I don't know what you had on your computer prior to trying to install this, but basically there's a bug where upgrading/uninstalling the message broker does not actually "clean-up" the system.  It can leave a registry key, file, or services installed.  Then when the new one is installed, it can't do what it needs to because the pieces are still around.

 

I think this issue was resolved in the newer versions of the package, but am not sure (which would be contained in some of the later versions of LabVIEW -- For instance I didn't see this issue when installing LV2024Q1/Q3)

 

Hope this helps.

0 Kudos
Message 21 of 26
(952 Views)

Thanks for your message! 

I have read through your previous messages, specifically about deleting the registry entries for HKLM\Software\Erlang registry key, deleting the "NI SystemLink Message Bus" service. I did not see any process called epmd.exe, but I went ahead and deleted the RabbitMQ folder in "Program Files/National Instruments/Shared".

 

However still getting the same error. This is a fresh PC to start with, so had no NI software installed. After a couple of attempts of installing, uninstalling, cleanup as above, I am still unable to get the GWeb 2022Q3 installed.

 

I understand what you are saying about NI PM 2025Q1 not the problem, but previously (around October 2024) I installed on two separate PCs the same GWeb 2022Q3 software without any install issues. Now the only difference is the GWeb 2022Q3 package installs NI PM2025Q1 instead of NI PM2024Q3 which worked before.

0 Kudos
Message 22 of 26
(941 Views)

Some progress...

I installed SystemLink first, then installed the GWeb development software.

With this, I did not get the error with NI-systemlink-message-broker).

 

Not ideal, but this could work for others in the same boat.

 

0 Kudos
Message 23 of 26
(935 Views)

Yeah, I don't typically recommend installing SystemLink on laptop/work computers.

A better option would have been to install either FlexLogger 2024 or LabVIEW 2024.

 

They would both include latest message broker (and connected packages)

0 Kudos
Message 24 of 26
(932 Views)

Thanks for all your help!

 

I do need to install SystemLink and NI Webserver on this machine as it is going to be server for the lab.

 

Do you know how I can get the NI SystemLink Tag Historian installed? I am not seeing it now on my latest install of SystemLink but I can see it on my development PC when I installed SystemLink in October last year (as shown in image below).

 

 

NI SystemLink Tag Historian.JPG

0 Kudos
Message 25 of 26
(927 Views)

Of course!

If you installed SystemLink Server successfully, the Tag Historian is installed by default. The SystemLink server installation has not been updated since Q4 of last year, so it would have been the exact same installation process as well (minus maybe a patch).

 

If you open the "SystemLink Service Manager" it should be listed in there -- also I think this is starting to go off topic for this particular thread, you can feel free to PM me directly if you have other questions (or you could always start a new thread).

0 Kudos
Message 26 of 26
(914 Views)