02-12-2025 11:10 PM
Hello,
Installing Systemlink 2025 Q1 today with administrator privileges. Running install.exe "as administrator".
I can't get past this error:
Do I need to stop Systemlink first?
02-12-2025 11:16 PM
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
02-13-2025 08:54 AM
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
02-13-2025 10:01 AM - edited 02-13-2025 10:01 AM
I also recommend using the Windows Service Manager and stopping all of the SystemLink services prior to trying an upgrade.
02-13-2025 10:12 AM
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.
02-13-2025 11:11 AM
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).
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.
02-13-2025 03:11 PM - edited 02-13-2025 03:13 PM
@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.