SAS M7 Content Server validate gives SEVERE: Exception accessing https://... (Connection reset)

[bheinsius]

Hi,

I just configured an 94M7 environment for a customer reverse proxy (F5) following instructions at https://documentation.sas.com/doc/en/bicdc/9.4/bimtag/p0sxhuco18v167n13dsmnrfqv7yy.htm

I have done this many times before - with success - but this time I can't get it to work.

Everything works well except for the SAS Content Server. Validating it from SAS Management Console gives an error:

[6/4/21 11:21 PM] INFO: Starting simple validation for WebDAV server (level 1) - ping
[6/4/21 11:21 PM] INFO: Ping successful!
[6/4/21 11:21 PM] INFO: Starting extended validation for WebDAV server (level 1) - Making a connection
[6/4/21 11:21 PM] INFO: Path: 'https://xxxxxxxxxxx:443/SASContentServer/repository/default/sasfolders/'
[6/4/21 11:21 PM] SEVERE: Exception accessing https://xxxxxxxxxxxxxxxxx (Connection reset)

I have not seen this error before. I can access the content server just fine from a web browser.

No errors in SASContentServer log or SASServer1_1.log either. Also no hits on Google for this specific error.

Any ideas?

-Bart

[gwootton]

Does your proxy permit the methods used by WebDAV described in the link (e.g. PROPFIND, PROPPATCH, MKCOL)? You could test this with curl:

curl -X PROPFIND --user 'sasadm@saspw:password' http://mid.demo.sas.com:7980/SASContentServer/repository/default --upload-file - -H "Depth: 1" <<end
<?xml version="1.0"?>
<a:propfind xmlns:a="DAV:">
<a:prop><a:resourcetype/></a:prop>
</a:propfind>
end

[bheinsius]

Your curl command returns:

curl: (7) couldn't connect to host

where executing this with a connection to the original server returns HTTP/1.1 200 OK

So indeed it seems like the F5 does not permit these methods, I will verify this with the F5 administrator, and let you know, thanks.

[Tom007]

HI @bheinsius 

Thank you for sharing the SAS Enterprise Miner 15.2 version issue, we are also encountering similar error in our SAS 9.4 M7 environment.

Was there any fix for the below issue.!!

Looking forward to your response.

[Tom007]

Below is the error message we encountering, all platform user experiencing same 

Please Select another one. The current selection may have permission issue.
Detail Error: com.sas.services.ServiceException: Previously failed to connect to https://DSN.com:8343/SASContentServer/repository/default/sasdav for user

[gwootton]

Did you use the curl command above to ensure you're able to use the WebDAV access methods successfully?

[Tom007]

Hi @gwootton 

Thank for your response. 

Could you provide the syntax that should include in the curl command. From which node I have to test the curl command from Compute node or Mid-Tier node ?

[gwootton]

You can run the curl command from any host that has a network path to your midtier URL, and the syntax would be that exact command I have above in my initial reply to this topic. You'd just need to replace the sasadm password and URL with values valid for your environment.

[Tom007]

HI @gwootton 

I did execute the curl command on compute node, got pages of output as below.

curl -X PROPFIND --user 'sasadm@saspw:password' https://DSN.com:8343/SASContentServer/repository/default

<?xml version="1.0" encoding="UTF-8"?><D:multistatus xmlns:D="DAV:"><D:response><D:href>https://DSN.com:8343/SASContentServer/repository/default/</D:href><D:propstat><D:prop><D:creationdate>1970-01-01T00:00:00Z</D:creationdate><D:alternate-URI-set/><D:lockdiscovery/><D:displayname>default</D:displayname><D:supportedlock><D:lockentry><D:lockscope><D:exclusive/></D:lockscope><D:locktype><D:write/></D:locktype></D:lockentry></D:supportedlock><D:group-member-set/><D:principal-URL><D:href>/</D:href></D:principal-URL><D:getlastmodified>Fri, 14 Jun 2024 14:14:01 GMT</D:getlastmodified><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:group-membership/></D:prop><D:status>HTTP/1.1 200 OK</D:status></D:propstat></D:response><D:response><D:href>https://DNS.com:8343/SASContentServer/repository/default/sasdav/</D:href><D:propstat><D:prop><D:creationdate>2022-11-28T22:01:52Z</D:creationdate><D:group-member-set/><D:getlastmodified>Fri, 14 Jun 2024 14:14:01 GMT</D:getlastmodified><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:alternate-URI-set/><D:lockdiscovery/><jcr:createdBy xmlns:jcr="http://www.jcp.org/jcr/1.0">sasadm</jcr:createdBy><D:displayname>sasdav</D:displayname><D:supportedlock><D:lockentry><D:lockscope><D:exclusive/></D:lockscope><D:locktype><D:write/></D:locktype></D:lockentry></D:supportedlock><D:principal-URL><D:href>/sasdav</D:href></D:principal-URL><jcr:created xmlns:jcr="http://www.jcp.org/jcr/1.0">2022-11-28T17:01:52.181-05:00</jcr:created><D:group-membership/></D:prop><D:status>HTTP/1.1 200 OK<

[Tom007]

Hi @gwootton 

Also encountering below output intermittently on compute node

curl -X PROPFIND --user 'sasadm@saspw:password' https://DSN.com:8343/SASContentServer/repository/default

<!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1></body></html>[user@hostname 2024-Jun-13.185416]$

[gwootton]

You probably got pages of output because you did not include the full command. The curl command supplied is passing a Depth limiter of 1 and specifying what property we are requesting in the body.

That said, since you got a response back this is probably not the same issue as the original poster, as their request using the PROPFIND method was rejected.

A 500 response from the application would have a corresponding error in the SASServer1_1 server.log.

You may want to engage SAS Technical Support on this issue.