GUI launch on client results in "No controlling server set" error
In some cases ''Invalid Arguments'' may be shown.
The NVBU server name may be missing or incorrectly defined in the gui.cfg file on the client.
In order for the client to control a server GUI, a server name needs to be provided. Also that server must be known to the client and accessible.
- Edit ~NetVault\config\gui.cfg
- Check the value under [Servers]
- Name = should match the machine name of the NetVault server as listed in on NetVault Configurator machine tab.
Example:
[Servers]
names=BAKBONE
Note that the client on which this is performed must have access to the specified server and must be able to contact it. Check its NV_HOME/etc/machines.dat to see if there is a stanza for the NVBU server with a contact address. If the server information is not available on the client, adding that client as a client to the server will facilitate the necessary hand shake and exchange of information.
There might be special circumstances where the NVBU server does not have a GUI and there are no clients added yet. In this particular case, you can use the nvclientadd command found on the NVBU server under NV_HOME/util, to add your first client so you can control the server's GUI from that client. By adding the first client to the server, both machine will exchange the necessary contact information, and the client will be able to control the server GUI.
BakBone SFDC Solution Number: 00000200
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center