ESD does not update Siebel Enterprise properly when Pause Or Cancel jobs is use on ESD Administration Page (Doc ID 1577008.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Email Marketing Server - Version 8.1.1 [21112] to 8.1.1.10 [23021] [Release V8]
Information in this document applies to any platform.

Symptoms

When attempting to pause a ESD Job using the ESD Job monitor web page "http:///esd/jobMonitor.jsp", the Job is pause in the Job Monitor web page but no feedback can be observed on the Siebel Marketing application.

Inspecting the esd.log we can see the following error:

2013-03-25 07:10:52,625 [QueueReader-0-callbackQueue] ERROR CallbackProcessor Error in connecting to web service: com.siebel.sem.common.db.DataProcessor$ConnectionFailureException: org.apache.axis2.AxisFault: This operation is not allowed when there are no records displayed.

Please execute a query that returns at least one record or add a new record.(SBL-DAT-00215)
2013-03-25 07:10:52,625 [QueueReader-0-callbackQueue] ERROR QueueReader Connection failure processing file dataq.0000000002
com.siebel.sem.common.db.DataProcessor$ConnectionFailureException: org.apache.axis2.AxisFault: This operation is not allowed when there are no records displayed.

Please execute a query that returns at least one record or add a new record.(SBL-DAT-00215)
at com.siebel.sem.esd.integrated.CallbackProcessor.process(CallbackProcessor.java:119)
at com.siebel.sem.common.db.QueueReader.run(QueueReader.java:134)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.axis2.AxisFault: This operation is not allowed when there are no records displayed.

Please execute a query that returns at least one record or add a new record.(SBL-DAT-00215)
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:446)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.siebel.marketing.webmarketing.WebMarketingStub.emailMarketingUpdateJobStatus(WebMarketingStub.java:767)
at com.siebel.sem.esd.integrated.CallbackProcessor.process(CallbackProcessor.java:78)
... 2 more

Alternatively the following error may be seen:

2013-03-26 12:50:52,781 [QueueReader-0-callbackQueue] ERROR CallbackProcessor Error in connecting to web service: com.siebel.sem.common.db.DataProcessor$ConnectionFailureException: org.apache.axis2.AxisFault: Error Code: 10944642 Error Message: Error: Inbound SOAP Message - Session Token is missing or invalid or has expired
2013-03-26 12:50:52,781 [QueueReader-0-callbackQueue] ERROR QueueReader Connection failure processing file dataq.0000000002
com.siebel.sem.common.db.DataProcessor$ConnectionFailureException:
org.apache.axis2.AxisFault: Error Code: 10944642 Error Message: Error: Inbound SOAP Message - Session Token is missing or invalid or has expired
at com.siebel.sem.esd.integrated.CallbackProcessor.process(CallbackProcessor.java :119)
at com.siebel.sem.common.db.QueueReader.run(QueueReader.java:134)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.axis2.AxisFault: Error Code: 10944642 Error Message:
Error: Inbound SOAP Message - Session Token is missing or invalid or has expired
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:446)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.siebel.marketing.webmarketing.WebMarketingStub.emailMarketingUpdateJobStatus(WebMarketingStub.java:767)
at com.siebel.sem.esd.integrated.CallbackProcessor.process(CallbackProcessor.java:78)
... 2 more

The issue can be reproduced at will with the following steps:
1. Using Siebel Marketing application launch a Campaign Wave
2. Check the ESD Job Monitor Web page "http:///esd/jobMonitor.jsp"
3. It should list a Job running, so ESD is sending emails.
4. Click on Pause on ESD Job Monitor web page for the current Job.
5. Check the Siebel Marketing wave, it still show Running.
6. Check the esd.log and you can see if keep trying to send feedback to Siebel Enterprise about the pause Job, but it returns an error:
"
2013-03-25 07:10:52,625 [QueueReader-0-callbackQueue] ERROR CallbackProcessor Error in connecting to web service: com.siebel.sem.common.db.DataProcessor$ConnectionFailureException: org.apache.axis2.AxisFault: This operation is not allowed when there are no records displayed.

Please execute a query that returns at least one record or add a new record.(SBL-DAT-00215)
2013-03-25 07:10:52,625 [QueueReader-0-callbackQueue] ERROR QueueReader Connection failure processing file dataq.0000000002
com.siebel.sem.common.db.DataProcessor$ConnectionFailureException: org.apache.axis2.AxisFault: This operation is not allowed when there are no records displayed.

"

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms