02-09-2024 6:22 PM - edited 02-09-2024 6:23 PM
We have 2 job servers using BODS 4.3:
When setting up Data Services scheduler to run from SERVER-1 the job will run without issues. However, when trying to set up a job schedule to run form SERVER-2, the scheduler will not run the job.
Data Services is able to create the schedule files and Windows Task Schedules on Server-2. But when the schedule job is supposed to run nothing is shown in Management Console. From the Windows Task Scheduler I get the following message:
Task Scheduler successfully completed task "\At2" , instance "{9abc427c-c3f1-49ad-aac1-abb6fecaa}" , action "C:\Windows\SYSTEM32\cmd.exe" with return code 2147991339.
AL_RWJobLauncherLog will show
(14.3.2.615) 02_09_2024 12:43:01 (4940): CRWJobLauncherApp::InitInstance called.
(14.3.2.615) 02_09_2024 12:43:01 (4940): Connected to CMS Server : SERVER-1:6400 of CMS Cluste : @SERVER-1:6400
(14.3.2.615) 02_09_2024 12:43:02 (4940): Connected to CMS Server : SERVER-1:6400 of CMS Cluste : @SERVER-1:6400
(14.3.2.615) 02_09_2024 12:43:33 (4940): *** RWJL_EXIT called.
(14.3.2.615) 02_09_2024 12:43:33 (4940): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
Already tried some KBA 1824177, 1823762, and 1957152 without luck. Can anyone that had this issue share how to resolve this?
User | Count |
---|---|
78 | |
10 | |
10 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.