Symptom
- The DS scheduler stopped working after windows security patching up.
- In job launcher log:
(14.2.11.2066) 10_20_2022 20:50:01 (13300): CRWJobLauncherApp::InitInstance called.
(14.2.11.2066) 10_20_2022 20:50:01 (13300): Connected to CMS Server : <Node Name>:6400 of CMS Cluste : @<Cluster Name>
(14.2.11.2066) 10_20_2022 20:50:02 (13300): Connected to CMS Server : <Node Name> :6400 of CMS Cluste : @<Cluster Name>
(14.2.11.2066) 10_20_2022 20:50:50 (9204): *** RWJL_EXIT called.
(14.2.11.2066) 10_20_2022 20:50:50 (9204): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
(14.2.11.2066) 10_20_2022 20:51:32 (13300): *** RWJL_EXIT called.
(14.2.11.2066) 10_20_2022 20:51:32 (13300): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220) - No log printed in the server event log during same timestamp.
Read more...
Environment
SAP Data Services 4.x
IPS cluster
Windows OS
Keywords
BI, DSMC, not, anymore, stop, trigger, response, nothing, happen , KBA , EIM-DS-SVR , Administration/Server , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.