Symptom
- Batch jobs can be executed directly from the DS Management Console, however they do not schedule.
- Executing any job directly from command line produces the following errors in the AL_RWJobLauncher.txt log:
(14.0.3.273) 02_10_2013 08:11:01 (16408): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
--------------------------
(14.0.3.273) 02_11_2013 07:00:00 (4520): CRWJobLauncherApp::InitInstance called.
(14.0.3.273) 02_11_2013 07:00:05 (4520): Launching Job (no wait, no status). INET ADDR <inet:Host:XXXX>, GUID <XXXX>. (BODI-1250134)
(14.0.3.273) 02_11_2013 07:00:05 (4520): Job has started. INET ADDR <inet:Host:XXXX>, GUID <XXXX>. (BODI-1250135)
--------------------------
(14.0.3.273) 02_11_2013 08:37:00 (10108): CRWJobLauncherApp::InitInstance called.
No Repo Registration
(14.0.3.273) 02_11_2013 08:37:01 (10108): *** RWJL_EXIT called.
(14.0.3.273) 02_11_2013 08:37:01 (10108): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
Read more...
Environment
SAP Data Services "DS" 4.0 SP3
Product
Keywords
DSMC, BODS, RQJobLauncher, BODI 1250220, CRQJobLauncherApp , 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.