Linkar Suite 2.3.7

Linkar saves configuration data in a single XML file. This includes details about licence/registration, schema details, Manager location and access, plugins, and Profiles and EntryPoints.

In Windows, the installation process and Linkar MANAGER save configuration data here:

%ProgramData%\KOSDAY\LinkarSuite\Config.xml

In Linux and macOS, the installation process and Linkar MANAGER save configuration data here:

/etc/KOSDAY/LinkarSuite/Config.xml

At the end of the installation, the Manager service may not start. During the OnStart phase, the service attempts to bind a socket listener to the defined Manager host:port. If this fails the server immediately stops.

The configuration file includes this node for the Manager:

<MANAGER USE_HTTPS="False"

 SSL_CERTIFICATE_FILE="cert.linkarsuite.com.pfx" SSL_CERTIFICATE_PASSWORD=""

 STATISTICS_ENABLED="True"

 CHECK_UPDATES="True"

 LISTENER_IP="localhost"

 LISTENER_PORT="11200"

 LISTENER_HTTP_PORT="11201"/>

We strongly discourage the use of "localhost" and "127.0.0.1". This can lead to a condition noted in Network Issues.
We do recommend using the system's hostname. The URL used by the MANAGER will be http://thishostname:11201.
The hostname must resolve to localhost for the server being installed. A service cannot be started in another system.
The hostname must also resolve through DNS if using the Manager from another workstation.

Edit the configuration file and change the LISTENER_IP value to the local host name.

Save the file, then click the Linkar MANAGER icon on the desktop to attempt a restart of the service.

If that does not work, re-edit the file and change the value to "127.0.0.1", save, and retry.

If the Manager service is still not starting, consider the other fields:

•Are ports 11200 or 11201 (or the ports you specified) blocked in any way for local or remote access?

•Note the value of USE_HTTPS, False or True (casing is significant). Is the browser in agreement with that setting?

Permissions

If the service fails to start, the issue could be with Permissions on the user starting the service.