BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
aj34321
Quartz | Level 8

Hi All,

 

I'm trying to validate the Content server from SAS Management Console. It throws below error:

 

INFO: Starting simple validation for WebDAV server (level 1) - ping
SEVERE: Connection timed out: connect
SEVERE: java.net.ConnectException: Connection timed out: connect

 

Request if you can help me resolve this.

 

 

Thanks, AK

1 ACCEPTED SOLUTION

Accepted Solutions
jag_SAS
SAS Employee

Hi. The message you are receiving is too generic to help you debug the problem.

 

Assuming you have used sas.servers to verify the services are up:

Lev1/sas.servers status

Then there are several logs you can check:

/Lev1/Web/Logs/SASServer1_1/SASContentServer9.4.log

/Lev1/Web/WebAppServer/SASServer1_1/logs/server.log

 

The exact location of the logs at your site can be determined by reviewing your Instructions.html file under the Lev1/Documents directory.

 

If you cannot tell the issue by reviewing the logs and restarting your middle tier does not help or is not an option, I would suggest opening a ticket with SAS Technical Support and sending in the two logs above. The middle tier support team will be able to help you debug your specific issue. 

View solution in original post

2 REPLIES 2
jag_SAS
SAS Employee

Hi. The message you are receiving is too generic to help you debug the problem.

 

Assuming you have used sas.servers to verify the services are up:

Lev1/sas.servers status

Then there are several logs you can check:

/Lev1/Web/Logs/SASServer1_1/SASContentServer9.4.log

/Lev1/Web/WebAppServer/SASServer1_1/logs/server.log

 

The exact location of the logs at your site can be determined by reviewing your Instructions.html file under the Lev1/Documents directory.

 

If you cannot tell the issue by reviewing the logs and restarting your middle tier does not help or is not an option, I would suggest opening a ticket with SAS Technical Support and sending in the two logs above. The middle tier support team will be able to help you debug your specific issue. 

Kalind_Patel
Lapis Lazuli | Level 10
Hi @aj34321, this error generally comes when your sassrv account or sastrust account have not proper credentials or roles assigned, please read the object spawner log it will give you clear idea about that,
And also make sure that sassrv password have not changed after the installation, and if changed then you have used SDM to update the paaswords.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 2 replies
  • 2562 views
  • 2 likes
  • 3 in conversation