SAP Knowledge Base Article - Preview

2032665 - RWJobLauncher failed to connect to CMS

Symptom

JobLauncher fails when invoked:

(14.2.3.481) 06_19_2014 15:44:04 (4488):               CRWJobLauncherApp::InitInstance called.
(14.2.3.481) 06_19_2014 15:44:04 (4488):               Failed to create ExtendedErrorHelper instance
(14.2.3.481) 06_19_2014 15:44:04 (4488):               *** RWJL_EXIT called.
(14.2.3.481) 06_19_2014 15:44:04 (4488):               *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)


Read more...

Environment

  • IPS or BI 4.1 SP5 with SAP Data Services 4.2 SP3 (all support packs and patches)
  • IPS or BI 4.1 SP4 with SAP Data Services 4.2 SP1 and SP2 (all support packs and patches)
  • IPS or BI 4.1 SP3 Patch 2 or above with SAP Data Services 4.2 (all support packs and patches).
  • IPS or BI 4.0 SP9 Patch 2 or above with SAP Data Services 4.1 SP3 (all patches).

Keywords

joblauncher error boe component upgrade, DS, BODS, schedule job, couldn't execute, JobLauncher, BODI-1250220 , KBA , EIM-DS-DEP , Data Services Deployment, Installation, Upgrade , EIM-DS , Data Services (Use Subcomponent) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.