Which logs to check when having a socket close error on batch jobs

[jbond007]

Hi Communities,

Recently we are having an on and off issues with our batch jobs, having [SAS][ODBC SQL Server Wire Protocol driver]Socket closed. We don't have any pattern observed since its happening at  different time and different jobs. Any tips on what to check or maybe debugging level to get the root cause?

SAS TS suggested that the cause of this is because of:

• network failure
• firewall timeout
• the database unexpectedly terminated the connection
• account permissions

But according to our DB and network team, nothing wrong on their side so we're checking what to tweak on SAS side. Will adding sastrace help on this?

https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/acreldb/n0732u1mr57ycrn1urf24gzo38sc.htm

Any tips is appreciated, thank you.

[ChrisNZ]

This message is Generated by the ODBC driver. SAS receives it and displays it as is.

The issue is lost communication between the ODBC driver and SQL Server, nothing to do with SAS. The communication between SAS and the driver is not what that message is about, and doesn't seem to be the problem.

Your platform admin needs to investigate. The driver might have logging options, they could try enabling them.

The driver seems be made by Progress. Contact them.

You could also try other ODBC SQL Server drivers.