To begin first verify that the PolySpace server is configured and running properly. To do so:
For Windows:
1. Launch the Remote Launcher Manager tool from the Start menu or by running:
C:\PolySpace\PolySpace_Common\RemoteLauncher\PSTRLManager.exe
2. Check that the configuration is correct
3. Confirm that the log file shows that the service is started by clicking "View Log"
4. If there are any errors or if you are unsure that the service started, click the "Start Daemon" button to restart the service.
For Solaris/Linux:
1. Verify that there is a polyspaced process running
2. Check the log file: /var/PolySpace/polyspaced.log to see that Remote Launcher is started and that there are no errors.
3. If there are any issues, try resetting the Remote Launcher by running the script:
/usr/local/PolySpace/PolySpace_Common/RemoteLauncher/bin/setup-remote-launcher
4. Once reconfigured you can run the same script with the -start-service flag to restart the service:
/usr/local/PolySpace/PolySpace_Common/RemoteLauncher/bin/setup-remote-launcher -start-service
Once you have determined that the service is up and running on the PolySpace Server, check to make sure that the client is configured to point to the correct port on the PolySpace Server. To do so:
1. Open the client Launcher
2. Go to the Options menu to Preferences (R2010a or prior: Edit menu to Preferences)
3. Go to the Remote Launcher tab
4. Choose the option to "Use the following server and port" and enter in the PolySpace Server hostname and port number
5. Press OK to set the PolySpace server
Once set, try running the job once more. If the job still fails, contact the Installation and Licensing Team here:
