Control-M(Scheduling tool) failed to trigger the Batch Jobs

dataservices administration
1

Hello All,
we are using Control M to schedule the batch jobs. Recently we upgraded from DS 3.2 to 4.2. Now in DS 4.2 version, control M is failing to trigger the jobs and throwing an error Access Denied. DS batch files are in D:\Jobs\Prod. The control M ID have full access to D:\Jobs\Prod folder and also to the %Link DIR%\Bin folder. Do i have do give access to any other folder?

When i added Control M ID as a admin to the DS server, jobs are running fine. but I cant do this due to security reasons.

DSKSR (BOB member since 2011-02-04)

2

may the log creation is failing, you need to give access to %DS_COMMON_DIR%\log folder also

manoj_d (BOB member since 2009-01-02)

3

It have full access to the %DS_COMMON_DIR%\log folder.
Also, when control m tries to execute the job, i am seeing the below error logged into Al_RWjoblauncherlog.txt file.

(14.2.1.622) 08_25_2014 21:03:41 (4104): CRWJobLauncherApp::InitInstance called.
(14.2.1.622) 08_25_2014 21:03:41 (4104): Failed to create ExtendedErrorHelper instance
(14.2.1.622) 08_25_2014 21:03:41 (4104): *** RWJL_EXIT called.
(14.2.1.622) 08_25_2014 21:03:41 (4104): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
(14.2.1.622) 08_25_2014 21:03:41 (4104): *** RWJL_EXIT called <180009 : Invalid command line syntax. (BODI-1250107)>
(14.2.1.622) 08_25_2014 21:03:41 (4104): *** ERROR: RWJobLauncher failed to get the repository information. (BODI-1250216)
USAGE
Command line syntax:

AL_RWJobLauncher.exe [“inet addr”] [“server log path”] [-w] [-s] [-t] [-v] [-C] [-S]

“inet addr” : inet address (in quotes). For example: “inet:foo:3010”.

“server log path” : Path to log directory for server (in quotes).

-w : Execute the job and wait for it to complete. The -s option (below) is implicitly included.

-tnnn : nnn = The time in milliseconds that the Job Server waits before checking a job’s status.

-s : Return exit status of the last job executed (unless server error, then return status of request).

     Note: Combine -w, -s, and -t to execute the job, wait for completion and return the status.

-v : Print AL_RWJobLauncher version number

-S “server group” : Lists the server group and Job Servers it contains using the following syntax:

     "server group name;server name:server host:server port[;server name:server host:server port][...]"

-C “file name” : Name of the engine command file (path to a file which contains the command line arguments to be sent to the engine).

JOB LAUNCHER ERRORS:

180002 : Network failure. (BODI-1250100)

180003 : Schedule service has not been started. (BODI-1250101)

180004 : Link_Dir is not defined. (BODI-1250102)

180005 : Trace Message file could not be created. (BODI-1250103)

180006 : Error Message file could not be created. (BODI-1250104)

180007 : GUID not found. Status cannot be returned. (BODI-1250105)

180008 : No command line arguments were found (causing this dialog). (BODI-1250106)

180009 : Invalid command line syntax. (BODI-1250107)

180010 : Can’t open command file (see -C option). (BODI-1250108)

DSKSR (BOB member since 2011-02-04)

4

Is the Control-M agent logged in as the same user that owns the Job Server?

eganjp :us: (BOB member since 2007-09-12)

5

the following error means the BOE SDK is not installed properly
Failed to create ExtendedErrorHelper instance

what other BO Applications are installed on this server ? only DS Designer and job server ?
what is the complete version of IPS/BI 4.1? and what is the complete version of DS 4.2 ?

do you have a support case for this ?

manoj_d (BOB member since 2009-01-02)

6

Control M agent uses different ID, no the one job server uses.

Only Data services 4.2 is installed on this server(all components).

Complete DS version:

Designer - 14.2.1.622
Jobserver - 14.2.1.622
Jobengine - 14.2.1.622
Repository - 14.2.1.0000

SAP BusinessObjects BI Platform 4.1 Support Pack 2
Version: 14.1.2.1121

DSKSR (BOB member since 2011-02-04)

7

I’m not experienced with Linux but I’ve seen issues where a login that is not the job server user doesn’t work right if the login doesn’t make a call to the al_env.sh script in the profile. At least, I think that’s the shell script you need to call.

eganjp :us: (BOB member since 2007-09-12)

8

we are using windows server.
where is this script al_env.sh located. i cant find it in bin folder.

DSKSR (BOB member since 2011-02-04)

9

In Windows it would be al_env.bat.

You should always provide the O/S along with the DS versions.

eganjp :us: (BOB member since 2007-09-12)

10

there is no al_env.bat, there is no need to run any bat file to set DS env on Windows

the issue that you are seeing is because of BOE SDK isn’t install properly
do this
open a command window
cd to the folder where the bat file with job execution command exists
set the following env
set BOE_LOGGER_ENVIRONMENT=-trace
execute the bat file that has job command
check for AL_RWJobLauncher*.glf file in the <INSTALL_ROOT>\SAP BusinessObjects Enterprise XI 4.0\logging folder, attach that log

manoj_d (BOB member since 2009-01-02)

11

Thanks Manoj.

I executed the batch file from cmd prompt after changing the boe_logger_environment = -trace and i have attached the AL_RWJobLauncher*.glf file.

Also i noticed when i executed, i see a windows popup says RWjoblauncher DLL has stopped working.
AL_RWJobLauncher_4920_2014_09_03_19_54_03_638_trace.txt (11.0 KB)

DSKSR (BOB member since 2011-02-04)

12

nothing much in the log, looks like there is some issue on the SDK side, you can try running repair for DS, if that doesn’t work, please open a support message

manoj_d (BOB member since 2009-01-02)

13

Thanks Manoj.
we noticed that CMS user is getting locked every time control m triggers the job and i think that is the reason for the RWjoblauncher DDL error. so we unlocked the CMS user, added the control M ID as a administrator to the job server. Now control m is able to trigger the jobs with out any errors. even i can run the jobs from cmd prompt with out any issues.

Right now control m id have modify and execute access to Batch files, Bin folder and log folder. so i think this ID need more access to execute the job.

DSKSR (BOB member since 2011-02-04)

14

Hi Guys

I know this is an old thread. But this is most relevant with issue I am facing.

I have a similar issue where new jobs in DS are failing. I have
DS 4.1 installed on windows 2008.

The specific job gets triggered on 1/3 production servers, all batch files are same and control -m user id has access to all other folders (SAP BO DS) and there is no network issue noticed while jobs are executed.

This particular repository is added to 3 JS on 3 different servers but no JS grp is created (had lots of issue and was removed before I joined the org). AL_RWlaucher logs says exit called but does not give any error msg

All other older jobs are running fine.Please advice

Regards
Manish Singh

singhman (BOB member since 2015-03-10)