SystemLink Forum

cancel
Showing results for 
Search instead for 
Did you mean: 

Systemlink 2025 Q1 installation cannot complete because of ni-corba-namingservice install error

Hello,

 

Installing Systemlink 2025 Q1 today with administrator privileges.  Running install.exe "as administrator".

 

I can't get past this error:

 

ChrisFarmerWIS_0-1739423273512.jpeg

 

Do I need to stop Systemlink first?

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

0 Kudos
Message 1 of 7
(261 Views)

I just realised this has happened to someone else before, but no reply:

 

https://forums.ni.com/t5/SystemLink-Forum/Corba-namingservice-error/td-p/4346528 

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

0 Kudos
Message 2 of 7
(257 Views)

Hi Chris,

 

My first instinct is to try to install just that package, excluding dependencies, in a DOS shell.  First check the exact name of the package you have stored locally, looking in this folder:

 

"C:\ProgramData\National Instruments\NI Package Manager\packages\"

 

You screenshot indicates that you should see something like this:
"ni-corba-namingservice_25.0.1.49157-0+f500_windows_x64.nipkg"

 

I recently installed SystemLink Server 2025 Q1, and I have this one:

"ni-corba-namingservice_25.0.0.49265-0+f113_windows_x64.nipkg"

 

I'm not sure what to make of the difference there.  Anyway, grab the exact name you see, and make sure it's in these 2 DOS commands, which you need to run one after the other in a DOS shell with admin rights:

 

"C:\Program Files\National Instruments\NI Package Manager\nipkg.exe" repair --exclude-dependencies --simulate "C:\ProgramData\National Instruments\NI Package Manager\packages\ni-corba-namingservice_25.0.1.49157-0+f500_windows_x64.nipkg"

 

"C:\Program Files\National Instruments\NI Package Manager\nipkg.exe" repair --exclude-dependencies "C:\ProgramData\National Instruments\NI Package Manager\packages\ni-corba-namingservice_25.0.1.49157-0+f500_windows_x64.nipkg"

 

The first command is just being careful, checking in simulation mode, but all the installer experts I've ever talked to swear by it, so I recommend to run that first to make sure there are no hiccups in your syntax.

 

Out of the box question: are you wanting to use the TDM features in SystemLink?  The Corba layer is only used for those modules, and I don't know if it even installs if you don't include the TDM modules in your installer configuration in the NI Package Manager.

 

Let us know what happens,

Brad Turpin

Principal Technical Support Engineer

NI / Emerson

Message 3 of 7
(225 Views)

I also recommend using the Windows Service Manager and stopping all of the SystemLink services prior to trying an upgrade.

Message 4 of 7
(214 Views)

Not sure if there is value to obtain the MSI log for this failing package to help debug the issue. You could follow the instructions in Generating and Locating NI Package Manager Error Logs for obtaining MSI logs, try to install again to reproduce the error, and then review new log files created and post back to this forum thread.

Scott Richardson
https://testeract.com
Message 5 of 7
(210 Views)

Hey Chris,

 

I know there are a few other posts already, but here is a "best practices that we've learned over the years" checklist for in-place upgrades (that I hopefully get turned into a KB soon).

  1. Check general system health
    1. Verify ample disk space
    2. Verify license is not near expiration
    3. Verify SSL certificates are not near expiration
    4. Capture the TDM User Account currently configured
    5. Capture the TDM Index and Cache locations
  2. Stop the NI Web Sever
    1. Open the NI Web Server Configuration UI
    2. Switch to the Control tab
    3. Click the Stop button
  3. Turn off the SystemLink Service Manager and NI System Message Bus
    1. Open Services
    2. Find the NI SystemLink Service Manager service
    3. Right click and select stop
    4. Find the NI SystemLink Message Bus
    5. Right click and select stop
    6. Verify in the SystemLink Server Configuration UI that all services have stopped
  4. Turn off other (TDM or client) Windows Services in Windows “Services” dialog
    1. “NI CORBA Naming Service”
    2. “NI PSP Service Locator”
    3. “NI Salt-Minion” (if present)
    4. “NI SystemLink Forwarding Service” (if present)
    5. “NI SystemLink TDM Account Service”
    6. “NI SystemLink TDM Database Service”
  5. Take backup of key SystemLink config directories:
    1. "C:\ProgramData\National Instruments\Skyline\Certificates"
    2. "C:\ProgramData\National Instruments\Skyline\Config"
    3. "C:\ProgramData\National Instruments\Skyline\HttpConfigurations"
    4. "C:\ProgramData\National Instruments\Skyline\Install"
    5. "C:\ProgramData\National Instruments\Skyline\RabbitMQ"
    6. "C:\ProgramData\National Instruments\salt\conf\pki"
    7. "C:\ProgramData\National Instruments\Web Server\config”
    8. "C:\ProgramData\National Instruments\Skyline\SkylineConfigurations"
    9. “C:\ProgramData\National Instruments\salt\conf\pki”
  6. Take backup of key Web Server config directories
    1. "C:\Program Files\National Instruments\Shared\Web Server\certs"
    2. "C:\Program Files\National Instruments\Shared\Web Server\conf"
    3. "C:\ProgramData\National Instruments\Web Server\config"
  7. Take a system snapshot if you're installed on a VM
  8. Take backup of Postgres data directory if installed locally
  9. Take backup of Mongo data directory if installed locally
  10. Run upgrade via NI Package Manager
  11. Restart the machine
  12. Verify all services come up Live

If you run through these steps, and are still running into issues, please forward along the logs that Scott recommended and we'll take a dive into those next.

Cheers!

TJ G
Message 6 of 7
(202 Views)

@Brad_Turpin wrote:

Out of the box question: are you wanting to use the TDM features in SystemLink?  The Corba layer is only used for those modules, and I don't know if it even installs if you don't include the TDM modules in your installer configuration in the NI Package Manager.

 


Initially I just selected ALL (so yes, tried to install TDM features), and after hitting this issue several times, the last install we did last night we deselected the TDM features almost by accident and now it's installed ok!  We don't need it right this moment, so we'll keep it uninstalled.

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

Message 7 of 7
(185 Views)