Hi, The error seems that the assigned port is not able to communicate to the sas web application. You can ping the assign port from compute server Or you can follow the below steps: To resolve a connection-failure error, perform the following steps: 1. Verify the protocol and port configuration for SAS Content Server in metadata. a. Log on to SAS Management Console using the sasadm user ID. b. On the Plug-ins tab, select Environment Management ► Server Manager. c. Right-click SAS Content Server. The, in the right pane, right-click Connection: SAS Content Server and select Properties. d. In the Connection: SAS Content Server Properties dialog box, click the Options tab and verify that the protocol and port number values on that tab are correct. Note: For a non-secure, server-layer configuration (, the correct protocol is HTTP. For configurations that are enabled with Secure Sockets Layer (SSL), the correct protocol is HTTPS. If SAS Content Server is configured using an external URL that points to an external reverse-proxy server of an F5 load balancer, the content server's proxyName, proxyPort, and scheme definition values should match those that are in the HTML tag in the server.xml file for the SASServer_1 web application server. 2. Verify that the SAS® Web Application Server (SASServer1_1) services are running and that the SAS Content Server repository starts without any errors. To do that: a. Review the SAS SASServer1_1 log file (server.log) to verify that there are no errors during start-up. The log file resides in SAS-configuration-directory/Lev1/Web/WebAppServer/ SASServer1_1/logs/. b. In the log file, also search for a message similar to the following to confirm that the services start successfully. 3. Review the SASContentServer9.4.log file to verify that there are no errors. The log file resides in SASconfiguration-directory/Lev1/Web/Logs/SASServer1_1/. In the log file, also search for the following message to confirm that SAS Content Server repository services start successfully: INFO org.apache.jackrabbit.core.RepositoryImpl - Repository started (5115ms) Server startup in 979797 ms WebDAV Enablement of the Server Fails When WebDAV enablement of the server fails, you receive this error message: SEVERE: Server is not WebDAV enabled! To resolve this error, perform the following steps: 1. Determine whether SAS Content Server in SAS Management Console is configured to use one-time user ID and password authentication instead of SAS token authentication. If the configuration is for a one-time authentication, the password is not valid in certain cases. After the initial request, authentication fails during cookie handling because the password that is passed is no longer valid. To determine which type of authentication you have: a. Log on to SAS Management Console using the sasadm user ID. b. Click the Plug-ins tab and select Environment Management ► Server Manager. c. Right-click SAS Content Server in the right pane of the application window. d. Then, right-click Connection: SAS Content Server in the right pane and select Properties. e. In the Connection: SAS Content Server Properties dialog box, click the Options tab. Verify that the value is Authentication Type, which should match to the SCHEMA= value in the web application server's server.xml file. For more info please refer to the documentation: http://support.sas.com/resources/papers/sas-9-4-content-server-troubleshooter.pdf
... View more
