SystemLink Forum

cancel
Showing results for 
Search instead for 
Did you mean: 

SystemLink 19.5 doesn't automatically start NI COBRA Naming Service

Solved!
Go to solution

Both an upgrade to SystemLink 19.5 and a new installation into Windows Server 2016 where no NI products were previously installed has resulted in a problem with the NI COBRA Naming Service not being automatically started.  This results in the error "Could not connect with the server" with the detailed error message "Bad Request: EXCEPTION: CORBA::TRANSIENT (TRANSIENT)" or "Bad Request: EXCEPTION: CORBA:SystemException (BAD_PARAM)".  You must manually start the service.

 

How can the NI COBRA Naming Service service be configured to start automatically?  

 

Full details about the installation, the error, and how to manually start the COBRA Naming Service can be found at the link below:

http://www.savvydiademsolutions.com/blog.php?topic=blog-systemlink#StartNiCobraNamingSvc 

 

0 Kudos
Message 1 of 4
(2,374 Views)
Solution
Accepted by topic author markwkiehl

Solved!  See the link below for instructions on how to resolve this problem.

http://www.savvydiademsolutions.com/blog.php?topic=blog-systemlink#StartNiCobraNamingSvc 

0 Kudos
Message 2 of 4
(2,296 Views)

Hello Mark,
I have also the problem with the NI CORBA Naming Service and want to test your documented solution. The link to your blog entry doesn't work anymore ;-(

Is there an other possibility to get your recipe for solving this situation

 

BR

Detlef

0 Kudos
Message 3 of 4
(643 Views)

Hello, Thanks for the solution but the link didn't work properly. It is only showing 404 error. Kindly do the needful. Thanks in advance

0 Kudos
Message 4 of 4
(411 Views)