Why aren't the command line utilities working?
Posted by John Villanueva on 23 March 2016 07:17 AM

When a command line utility fails to execute and instead generates an "Error connecting to server" or asks for the configuration file path, chances are you have yet to run the manager-configuration utility (for MFT Server versions prior to 9.3) or the js-client-configuration utility (for MFT Server 9.3 and higher).

To remedy this problem, 

  • for versions prior to 9.3: Just run the manager-configuration utility using the same parameters you used when you issued the server-configuration utility. For example, if you executed server-configuration likeso:
    • ./server-configuration -host -port 10880 -rest.port 11880 -user admin -password secret, then you should use the same parameters for manager-configuration.
  • for versions 9.3 and above: Just run the js-client-configuration utility using the same user and password parameters as the ones used in js-addadmin and the same host and port parameters as the ones used in js-server-configuration. For example, if you executed js-addadmin and js-server-configuration like this:
    • js-addadmin -db -username admin -password admin -sa
    • js-server-configuration -host -port 10880 -rest.port 11880, then run js-client-configuration like this: 
      js-client-configuration -host -port 10880 -user admin -password admin

In Windows installations, you don't run server-configuration in the command line. In this case, the parameters you'll need for the manager-configuration utility are the same parameters you used during the GUI-based installation. Specifically, the parameters you entered in Figure 178 here:

(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.

Help Desk Software by Kayako fusion