Error while using "Run_Batch_Job" web service call (Job Server null)

[Former Member]

Hello,

I've been trying to use the "Run_Batch_Job" function and I'm getting the following error message:

"Web Services sent the request to start batch job 'JOB_Sleep' on server 'null'. The Job Server refused the request with error: null"

I read somewhere that maybe the AL_MACHINE_INFO table has incorrect info, but in this case it seems (?) correct. I can copy/paste the specifics if need be, but the only field that differs from other entries is the "RESERVED1" field, which is null in this case. As a parallel, "RepoManager" has "5" in that field.

Regardless, I've recently tried adding the job server to a server group, which didn't fix anything.

I've attached the logs (it's a .zip that I renamed to .txt, please take out the .txt to get the contents). Although there are some weird things being logged (like empty messages), I'm not even going to pretend to understand what's in there. I've synced and re-synced my job server and started and re-started my service, to no avail. In the integrator's guide documentation it says that I can input "jobServer" and "serverGroup," though if I choose not to, SAP BODS will choose an appropriate job server or server group for me. Nonetheless, I went to look for these parameters, and I assure you that they are, in fact, NOT in the WSDL. To reiterate, there are no "jobServer" or "serverGroup" parameters in the Run_Batch_Job function. The only thing that I see is off is when I open up the Designer, it tells me that my Profiler is not working, but that shouldn't really have any effect on the job server, correct?

Any ideas?

logs.zip.txt.zip

[Former Member · Accepted solution]

don't update or delete anything from AL_MACHINE_INFO, you may end up corrupting you DS configuration.

the problem that you see may be happening only for jobs invoked using webservices, try to execute the job from Management console or Designer on the same job server if that works fine then there is no problem with the DS JobServer (AL_MACHINE_INFO)

what is the complete version of DS ? there was a issue in DS 4.0 SP1 with run_batch_job or any DS webservice which has a nested input, and it was fixed in later patch/sp I have don't remember the patch number, in any case, the latest SP/Patch for DS is SP2 Patch 3, I would recommend applying the latest patch

[Former Member · Accepted solution]

The job runs fine when I run it through the designer. My version is 14.0.1.142. I assume SP2 would be 14.0.2.XYZ, so I'll try downloading SP2. Thanks.

[Former Member · Accepted solution]

Do you know where the patches are located perchance? I can't find where to download them from.

[Former Member · Accepted solution]

you will find it under Support Packages and Patches, take the latest SP02 Patch 3, you can install this directly on top of SP1, there is no need of installing the SP02 first, this is a complete package

Support Packages and Patches - D" SBOP DATA SERVICES" SBOP DATA SERVICES 4.0

DATASERV02P_3-20007459.EXE SBOP Data Services 4.0 SP02 Patch3  3 Info  1267058 19.03.2012

[Former Member · Accepted solution]

Gotcha - found it. I'll let you know how it turns out. Thanks x10000

[Former Member · Accepted solution]

FYI, I applied the patch and that old "null" error is gone. It's been replaced by "Operation not configured for Web Services: function=Logon" (on the logon)

... Which is progress, thanks!

.. I'm trying to look into this error currently, but do you have any ideas off the top of your head?

[Former Member · Accepted solution]

Ugh, I spoke too soon...

I had come across error "Web Services sent the request to start batch job 'JOB_Sleep' on server 'null'. The Job Server refused the request with error: No JobServer in the Server Group: sg_SAP_BO4_Repo"

... so I deleted my server group.

and now i'm back to this error again:

"Web Services sent the request to start batch job 'JOB_Sleep' on server 'null'. The Job Server refused the request with error: null"

[Former Member · Accepted solution]

if you have done any deletes or updates to AL_MACHINE_INFO then I would suggest you do a resync from the server manager for each repo that is registered to the job server

try with a simple input, you only need 3 things, name of the job, name of the repo as registered in CMC and name of the jobServer (name that you have entered in server manager) and then try, also post your input request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.businessobjects.com/DataServices/ServerX.xsd">

   <soapenv:Body>

      <ser:RunBatchJobRequest>

         <jobName>MY_TEST_JOB</jobName>

         <repoName>DSRepo</repoName>

         <jobServer>JobServer_1</jobServer>

      </ser:RunBatchJobRequest>

   </soapenv:Body>

</soapenv:Envelope>

[Former Member · Accepted solution]

Firstly, I haven't made any changes to AL_MACHINE_INFO.

Sending the request you have set up produces that error. It's what I've been doing.

I actually noticed that if I set "Item" and "ItemElementName" I can pass a jobServer or serverGroup, so I feel like we're getting a little closer. The naming is weird, but at least now I see where this jobServer/serverGroup param is. I guess it's because I used SVCUTIL to auto-generate some C# code instead of constructing the requests myself... Nonetheless, I get the same error...

This is what fiddler says:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

<s:Header>

<h:session xmlns:h="http://www.businessobjects.com/DataServices/ServerX.xsd" xmlns="http://www.businessobjects.com/DataServices/ServerX.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<SessionID xmlns="">895BA18A-8624-D553-E4F0-DE79B3353FA2</SessionID>

</h:session>

</s:Header>

<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<RunBatchJobRequest xmlns="http://www.businessobjects.com/DataServices/ServerX.xsd">

<jobName xmlns="">JOB_Sleep</jobName>

<repoName xmlns="">SAP_BO4_Repo</repoName>

<jobServer xmlns="">SAP_BO4_JobServer</jobServer>

</RunBatchJobRequest>

</s:Body>

</s:Envelope>

[Former Member · Accepted solution]

I am able to use the same input from SoapUI and it's working fine, only thing that I changed is the values (jobName, repoName and jobServer). All these 3 values are case-sensitive, check if you have entered the values the way they appear in management console

run the test agin, and post the last log entries from the following log files

%LINK_DIR%\log\webservices.log.0, web_admin.log.0

also, if possible, use SoapUI or similar tool

this time don't pass the jobServer name at all, webserver will search for any available jobserver and submit the job on it

[Former Member · Accepted solution]

That throws the same error. Here is the SOAP request:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

<s:Header>

<h:session xmlns:h="http://www.businessobjects.com/DataServices/ServerX.xsd" xmlns="http://www.businessobjects.com/DataServices/ServerX.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<SessionID xmlns="">BA6F3EE1-FABD-7CFE-1644-7E143200D178</SessionID>

</h:session>

</s:Header>

<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<RunBatchJobRequest xmlns="http://www.businessobjects.com/DataServices/ServerX.xsd">

<jobName xmlns="">JOB_Sleep</jobName>

<repoName xmlns="">SAP_BO4_Repo</repoName>

</RunBatchJobRequest>

</s:Body>

</s:Envelope>

The response follows:

<?xml version='1.0' encoding='utf-8'?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Body>    

<localtypes:BatchJobResponse xmlns:localtypes="http://www.businessobjects.com/DataServices/ServerX.xsd">

       <pid>-1</pid>

       <cid>-1</cid>

       <rid>-1</rid>

       <repoName>SAP_BO4_Repo</repoName>

       <errorMessage>Web Services sent the request to start batch job 'JOB_Sleep' on server 'null'. The Job Server refused the request with error: null</errorMessage>      

</localtypes:BatchJobResponse

></soapenv:Body>

</soapenv:Envelope>

Strangely enough, those logs were not written to... The "Date modified" is still 4/12/2012 (I ran some successful calls yesterday so I assume it's from then).

P.S. As I mentioned, I don't use SOAP requests to call the services. They are generated for me from the auto-generated C# code. I've never had a problem in the past with misnamed types or parameters (or anything like that), but having checked the parameters anyway I found that they are spelled the same way that they are spelled in the WSDL (taken from the Data Services admin console).

[Former Member · Accepted solution]

is it possible for you to open a case with support for this ? it will be easy for me to work through support to find what is causing the issue, if you have filed a case give me the incident number

for some reason the JobServer name is getting set to null, this was an issue in earlier release and you should not see this with SP2 Pacth 3, did you apply the Patch on the Webserver also ? is everything installed on same server ? go to Management Console and click on about link on the top right side to see the version that is displayed

[Former Member · Accepted solution]

Yes, I did file a case.

Give me a minute and i'll edit this post with the relevant info.

EDIT: I see "Message Number" 337543 / 2012

It seems someone has replied to it recently, didn't respond yet.

[Former Member · Accepted solution]

Guy found a solution to my case...

basically, the repositories were set up to use the wrong account. Strange that it didn't error out somewhere else. Like, I was able to run jobs and whatnot. The only issue I found was this web service call. And, actually, it was only a select few web service calls that were failing.

so make sure to set up your repositories in CMC correctly, guys!

Oh, and thanks so much for the help, friend.