Thin Client fails to launch server program and the error "connection failed, unable to start remote process" is displayed.
This error is caused by permissions, system resources and other reasons. Ensure that the working directory specified for the Alias exists and that the correct permissions are set. Check the AcuRCL configuration file (acurcl.cfg) to ensure the correct path specification is set for SERVER-RUNTIME. This must be set if the remote runtime is installed in a different directory than AcuRCL. Ensure that the remote runtime has a valid runtime license. If many instances of the server application are running successfully, this indicates a lack of resources on the server.