Whilst administering a SAP ASE based SAP system, I came across an issue in the ASE Job server error log “JSTASK.log”:
00:140737306879744:140737340581728:2016/02/24 16:50:00.87 worker ct_connect() failed.
00:140737306879744:140737340581728:2016/02/24 16:50:00.87 worker jsj__RunSQLJob: jsd_MakeConnection() failed for user sapsa to server SID
00:140737306879744:140737340581728:2016/02/24 16:50:00.87 worker jsj__RunSQLJob() failed for xid 66430
00:140737317369600:140737340581728:2016/02/24 16:55:00.87 worker Client message: ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.
The issue was caused by a change of the sapsa user password whereby the SAP recommended method of using the hostctrl process, wasn’t followed.
The recommended method updates the sapsa user, the secure storage file plus also the external login for the Job Server.
This is mentioned at the very end of SAP note 1706410 (although it is suggested that the process in this note is no longer followed to change the passwords).
To fix the issue, follow finals steps in the SAP note 1706410:
isql -X -Usapsa -S<SID> -w999
use master
go
sp_helpexternlogin
go
Server Login Externlogin
———————- ——————– ————
SYB_JSTASK sapsa sapsa
Drop the SYB_JSTASK entry:
exec sp_dropexternlogin SYB_JSTASK, sapsa
go
Re-create it with the new password:
exec sp_addexternlogin SYB_JSTASK, sapsa, sapsa, ‘<new sapsa password>’
go
This should fix the issue.
