Troubleshoot Runtime Server Start

Port Number Already in Use

If the Runtime Server fails to start or restart, and if the server log file lists the failure dfwlpListenAttr_connattr(wlp), then another application might be using the server port number. Reassign the server to an unused port number. For more information about default port numbers, see Default Ports.
If the server log is not created, then follow these steps if your server installed on Windows:
  1. Open the Windows Event Viewer.
  2. Select the Application event type.
  3. Click the Source column, to sort the events based on the type of source.
  4. Search the Source column for DataFluxDMS. Typically, two such events are logged for each time period. If no details are found in those two log events, then look for a log event with the source SAS. One such message will include the following message:
    WARNING: Messages have been logged to
    the file named 'C:\Documents and Settings\LocalService\Application
    Data\SAS\LOGS\DFINTG~1.EXE.1854.21CBDA9C.log'
On UNIX or Linux, errors are written to the stdout location of the shell from which the Runtime Server or Design Server was started.

Server Dependency

If your Runtime Server fails to start or restart, you might need to resolve a server dependency. The SAS Metadata Server must be fully operational before the Runtime Server can start. This dependency reflects the requirement that the Runtime Server retrieves several configuration option values from the SAS Metadata Server at start-up.
To resolve the server dependency, you can use one of the server management applications or commands in your operating environment. In the Windows operating environment, you can execute the following command:
sc config "name-of-Runtime-service" 
      depends= "name-of-metadata-service"
The services names are provided in the server properties, and they are not the Display Names, as shown in the following example:
sc config "dfx-POServer-server1" 
      depends= "SAS [Config-Lev1] SASMeta - Metadata Server"
In the sc config command, the quotation marks are required. Also, the depends argument uses no blank space before the equal sign and requires a blank space after the equal sign.

OpenSSL Not Found

The SAS Visual Process Orchestration Runtime Server does not start if it is configured to use SSL and if OpenSSL is not found. OpenSSL must either be identified in the PATH environment variable or stored in the directory install-path/bin.