OpenLab CDS 2.6. - Connection Issue

Assuming it is just the client that has changed it's name. Do the following:

1. Windows Icon>Agilent Technologies>OpenLab Configuration
2. Enter the hostname of the server, click connect
3. Enter the username and password of an admin user
4. Untick the "Register as Instrument Controller" if it is ticked
5. Click "Register"

That should do the trick.

Assuming it is just the client that has changed it's name. Do the following:

1. Windows Icon>Agilent Technologies>OpenLab Configuration
2. Enter the hostname of the server, click connect
3. Enter the username and password of an admin user
4. Untick the "Register as Instrument Controller" if it is ticked
5. Click "Register"

That should do the trick.

Just tried it, but didn't worked although popup appeared. And indeed it's just the client, not a controller. 

Adding some more information about this issue:

When trying to launch an instrument, the following error message pops up "Unable to connect to instrument server"

In the Activity log it shows "The session connection to instrument controller 'XXX' for instrument 'YYY' has been lost"

We have also noticed that there are 2 files in this folder "C:\ProgramData\Agilent\AcquisitionSecureFolder" that contain the old hostname

OLDHOSTNAME.domain.com.pfx

OLDHOSTNAME.domain.com.secret

Has the name of the Instrument controller changed also? Please check with IT that they haven't done anything else, like modify the network etc.

When you say it didn't work, what did happen? It should pop open the window and after you click Register what did it do? You have to close all the open OpenLab Windows/Control Panel etc. Preferably restart the PC, so that it can implement the changes.

Hello,

Since this is a client server install, I would suggest opening a ticket with the informatics group. This could be a certificate or other issue caused by the name change or something on the computer changed at the same time as the name change.  https://servicedesk.li.agilent.com/support 

Marty

Hello,
Finally we were able to resolve, for some reason the scheduled task that is supposed to generate the certs at startup was failing. Recreating and running the task fixed the certificate after rename issue, and now the client is able to connect to the instrument servers