SBL-EAI-04311: Operation '%1' is expecting a response but no response was received.

Applies to:
Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 7.8

Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04311: Operation '%1' is expecting a response but no response was received.


Scope
This document is informational and intended for any user.


SBL-EAI-04311: Operation '%1' is expecting a response but no response was received.
Explanation
The particular webservice operation is expecting a SOAP response but none was returned by the webservice that was invoked.

Corrective Action
Ensure that the webservice to be invoked is going to return a SOAP response. If the webservice is not meant to return a SOAP response, go to Siebel Tools and check that the business service method (which has the same name as the operation) does not have any business service method arguments of type 'Output' defined.









Applies to:
Siebel System Software - Version: 7.8.2.2 [19219] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.2 [19219]
Database: Oracle 9.2
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: IBM AIX 4.1.4 RS/6000

This document was previously published as Siebel SR 38-3034955799.
***Checked for relevance on 29-NOV-2010***
Symptoms
An Outbound Web Service was implemented using the Java Messaging Service (JMS) transport.
As indicated in the documentation, the address was set as below.

jms://YourQueueName@YourConnectionFactory

When doing this, call of the Web Service lead to the error below.

Operation '%1' is expecting a response but no response was received.(SBL-EAI-04311)


Cause
The error was due to the fact that the external application consuming the message sends the response in a different queue.
In the current version of the product, it is not possible to set different queue for the request and response. Both should go in same queue. So, in the above case, the web service call timed out and not response was got.
Solution

To be able to set different queue for JMS transport, enhancement request 12-1EAJ0Y3 has been created to have the product enhanced in the future version.
Enhancement request 12-1EAJ0Z9 has also been created to have the above point clearly stated in the bookshelf about JMS transport.

The above scenario is also true for MQ transport.

To be able to set different queue for MQ transport, enhancement request 12-1EBUJBZ has been created to have the product enhanced in the future version.

Enhancement request 12-1ECBTP7 has also been created to have the above point clearly stated in the bookshelf about MQ transport.

One possible workaround is to change the transport from JMS/MQ to "Local Business Service". Review the bookshelf Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > About Local Business Service for reference but the general idea is that the SOAP message is passed to a custom BS that will handle the transfer.

NOTE: 477891.1 Using a Local Business Service To Customize the SOAP Header for an Outbound Web Service in Siebel 7 may also be used as reference.

For JMS, a custom BS should call the the standard BS "EAI JMS Transport" to post the request.

Using the SendReceive method the SendQueue and ReceiveQueue can be explicitly set (refer to the Transports and Interfaces: Siebel Enterprise Application Integration > Java Message Service Transport for help about "EAI JMS Transport"). With MQ, refer to BS " EAI MQSeries Server Transport" or " EAI MQSeries AMI Transport".

Using this approach, Error "SBL-EAI-04298: SOAP Envelope received is not valid" may be return then.




References
BUG:10508923 - WITH JMS TRANSPORT, ADD FUNCTIONALITY TO SET DIFFERENT QUEUES FOR REQUEST AND RESPONSE IN WEBSERVICE
BUG:10508924 - DOCUMENT THAT REQUEST AND RESPONSE SHOULD GO IN SAME QUEUE WITH TRANSPORT JMS IN WEB SERVICES
BUG:10509077 - WITH MQ TRANSPORT, ADD FUNCTIONALITY TO SET DIFFERENT QUEUES FOR REQUEST AND RESPONSE IN WEBSERVICE
BUG:10509078 - DOCUMENT THAT REQUEST AND RESPONSE SHOULD GO IN SAME QUEUE WITH TRANSPORT MQ IN WEB SERVICES
NOTE:477891.1 - Using a Local Business Service To Customize the SOAP Header for an Outbound Web Service in Siebel 7.x and 8.x











Applies to:
Siebel Analytics - Version: 7.5.3.160 [AN 211] to 10.1.3.4.1 [1900] - Release: V7 to 10g
Business Intelligence Suite Enterprise Edition - Version: 7.5.2 [AN175] to 10.1.3.4.1 [1900] [Release: V7 to 10g]
Microsoft Windows (32-bit)
Product Release: V7 (Analytics)
Version: 7.5.3.160 [AN 211] Analytics
Database: Microsoft SQL Server 2000 SP4
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3388569990.
Symptoms
Follow-up SR from 38-3385930013

On the custom workflow called 'AGG_JTI_Login1' we are calling service 'SAWSessionServiceSoap', method 'impersonate' and the following error was received:

Error running sub-process 'AGG_JTI_Login1' at step 'Login'.(SBL-BPR-00183)
--
Operation 'impersonate' is expecting a response but no response was received.(SBL-EAI-04311)
--
Error invoking service 'SAWSessionServiceSoap', method 'impersonate' at step 'S2'.(SBL-BPR-00162)

This was checked by WF.

Cause
This customer reported receiving the following error messages when calling the ‘Impersonate’ Method of the Siebel Analytics SOAP ‘SAWSessionServiceSoap’ Service from a Siebel Workflow: -

ObjMgrLog Error 1 0 2007-07-04 11:02:01 (stepexec.cpp (741)) SBL-BPR-00183: Error running sub-process 'AGG_JTI_Login1' at step 'Login'. PrcExec PropSet 4 0 2007-07-04 11:02:01 Setting runtime value of property 'Namespace: 'USER' Name: 'Error Code' Datatype: 'String'' to: PrcExec PropSet 4 0 2007-07-04 11:02:01 SBL-BPR-00183
IDS_EAI_WS_OD_RESPONSE_EXPECTED
SBL-BPR-00162 PrcExec PropSet 4 0 2007-07-04 11:02:01 Setting runtime value of property 'Namespace: 'USER' Name: 'Error Message' Datatype: 'String'' to: PrcExec PropSet 4 0 2007-07-04 11:02:01 Error running sub-process 'AGG_JTI_Login1' at step 'Login'.(SBL-BPR-00183)
Operation 'impersonate' is expecting a response but no response was received.(SBL-EAI-04311)
Error invoking service 'SAWSessionServiceSoap', method 'impersonate' at step 'S2'.(SBL-BPR-00162) StpExec End 4 0 2007-07-04 11:02:01 Stopping step instance of 'Login' with an 'Error' status. StpExec End 4 0 2007-07-04 11:02:01 Stopping step instance of 'Login' with a 'Terminated' status.
PrcExec End 4 0 2007-07-04 11:02:01 Stopping process instance of 'AGG_JTI_Login1' with an 'Error' status. ObjMgrLog Error 1 0 2007-07-04 11:02:01 (app.cpp (2010)) SBL-EXL-00151: Error: SiebelError: Error running sub-process 'AGG_JTI_Login1' at step 'Login'.(SBL-BPR-00183) Operation 'impersonate' is expecting a response but no response was received.(SBL-EAI-04311) Error invoking service 'SAWSessionServiceSoap', method 'impersonate' at step 'S2'.(SBL-BPR-00162) Error near no filename:97 [InvokeMethod()]. from no filename:97 [ImportAccounts()] from no filename:169 [WebApplet_PreInvokeMethod()]

Further investigation and debugging by increasing the Object Manager and Workflow Logs and using the MS SOAP Toolkit showed that the HTTP calls where not getting to the Siebel Analytics Web Server (SAW).

Solution
Once the customer ‘unchecked’ the ‘Use Proxy Server’ Checkbox on their IIS configuration for their User the login to the Siebel Analytics Server occurred as expected.




Related



--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------

Middleware > Business Intelligence > Oracle Business Intelligence Suite, Enterprise Edition > Siebel Analytics
Middleware > Business Intelligence > Oracle Business Intelligence Suite, Enterprise Edition > Business Intelligence Suite Enterprise Edition











Applies to:
Product Release: V7 (Enterprise)
Version: 7.5.2.100 [15252]
Database: Microsoft SQL Server 2000
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: Microsoft Windows 2000 Advanced Server SP 2

This document was previously published as Siebel SR 38-1102388469.

Symptoms
SBL-EAI-04311, SBL-BPR-00162
We are actually working on version 7.5.3 [16157] ENU using the Field Service Application. This is a completely vanilla instance of Siebel with no customizations.

I have a sales order for one product for which inventory is available in a location.

When on the Orders Screen, Header Detail view, with the Sales Order selected, I press the 'Submit' button. I get the following message:

[1] Operation 'Insert' is expecting a response but not response was recieved. (SBL-EAI-04311)
[2] Error invoking service 'External Order', method 'Insert' at step 'External Order Proxy'. (SBL-BPR-00162)

I believe this button triggers the vanilla workflow process 'Submit Order ASI' which has a status of Active and has NOT been customized.

Please advise.


Solution
Message 1
For the benefit of other users, the customer was trying to submit an Sales Order on the Order header applet of Siebel Field Service application, version 7.5.3.

An error message always pops up:

[1] Operation 'Insert' is expecting a response but not response was received. (SBL-EAI-04311)
[2] Error invoking service 'External Order', method

This error could occur if an Order is submitted by clicking the Submit button on the “Order Entry - Order Form Applet Dashboard”, that means, if user
* Create Orders in View > Site Map > Orders > My Service Orders (or All Service Orders),
* Add Line Items for the Order,
* Click the Submit button in the Order Header applet (Order Entry - Order Form Applet Dashboard)

Then, the error message will appear.

The Submit Order on the Service Order order header invokes a workflow called Submit Order ASI which is supposed to be hooked into the companies Integration Server i.e. Tibco, Vitria, etc..

ABO is only supported on Sales Orders.

A documentation enhancement request have been logged to address this behavior.

CR 12-J2ALPG, Need detail steps how to set, and where to set in order to have the Submit button work.

In order to submit Orders, users should
* Create Orders in View > Site Map > Orders > My Sales Orders (or All Sales Orders),
* Add Line Items for the Order,
* Click the Submit button in the Order Header applet (Order Entry - Order Form Applet Dashboard (Sales))










Applies to:
Business Intelligence Server Enterprise Edition - Version: 10.1.3.4.1 [1900] and later [Release: and later ]
Information in this document applies to any platform.

Symptoms
Using Siebel Marketing 8.0.0.7 with OBI 10.1.3.4.1 the following errors are received from the OBI EE: -

In load phase:
--------------
Error/Warning : Error invoking service 'Mktg Data Load Service', method 'PurgeCache' at step 'Purge Segments/Segment Trees Cache'.(SBL-BPR-00162)
Operation 'impersonate' is expecting a response but no response was received.(SBL-EAI-04311)

In Launch Phase:
----------------
Error/Warning : Error invoking service 'Wave Execution', method 'SendOffers' at step 'Send Offers / Vendor Lists'.(SBL-BPR-00162)
--Operation 'impersonate' is expecting a response but no response was received.(SBL-EAI-04311)

Cause
Due to resource limitations on the OBI EE environment, the BI Server is not able to process the Marketing Requests in a timely fashion and the communication requests are timing out.
Solution
This customer resolved their issue by increasing the Memory available on the OBI EE Server machine.

Customer's can also look to increase the 'HTTPSLEEPTIME' parameter in their environment to allow the communication to have longer to make the connection request.
References
NOTE:477522.1 - How To Troubleshoot Memory Leaks on UNIX











Applies to:
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-1834126761.

Symptoms
SBL-EAI-04311
Hello

We have a campaign "Campaign A".
We load a segment => we have 10 contacts in the Campaign list contact.

In the execution option, the option "Load behavior" is "Add to existing wave".

If we schedule the campaign to reload the campaign each day, all the contacts are deleted and then recreated with the result of the segment !

We want that the old contacts stay always (because outcomes are registred) and we want to add each the new contact. (The segment is based on several criteria => each day the contacts are different).

this SR is urgent because we are in production and we can not use the scheduling safely.

Thanks for your help
Regards

Benoit


Solution
Message 1
For the benefit of others,

The customer was doing a campaign load however when this was doen there was an error in the workflow process manager log file containing the following

"Operation 'impersonate' is expecting a response but no response was received.(SBL-EAI-04311)
--
Error invoking service 'Mktg Data Load Service', method 'PrepareCache' at step 'Prepare Cahce'.(SBL-BPR-00162)"

Change Request #12-QDAHPK has been created to deal with the 'impersonate' error that is occurring. If this error occurs please provide the detailed workflow process manager log file to Siebel Technical Support.

Thank you,

Regards
Siebel Technical Support












Applies to:
Siebel Reports - Version: 8.1.1 [21112] to 8.1.1 [21112] - Release: V8 to V8
Information in this document applies to any platform.

Goal
The integration to Oracle BI Publisher uses an Outbound Web Service call, invoking the PublicReportService web service on the Oracle BI Publisher server.

Siebel Outbound Web Services use the "EAI HTTP Transport" business service for sending the HTTP request.

The "EAI HTTP Transport" business service has a parameter called HTTPSleepTime ,which controls how long the business service waits for a response for the webserver. HTTPSleepTime defaults to 120000 milliseconds (2 minutes).

If the generation of the Oracle BI Publisher report, takes over 2 minutes, then an error will occur as a result of the timeout. This may occur in the case of very large and complex reports.

In the XMLPReportServer*.log file the following error message will be displayed:
SBL-EAI-04311: Operation 'runReport' is expecting a response but no response was received.

Solution
It is not currently possible to set the HTTPSleepTime via the XMLP Report Server component and Bug # 10571200 (CR #12-1U2FN7D) has been raised.

Amend the "EAI HTTP Transport" business service using Siebel Tools.
Add code to the Service_PreInvokeMethod method to set the HTTPSleepTime parameter, for example:
function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{

// Double up the sleep time. 4 minutes

Inputs.SetProperty("HTTPSleepTime", "240000");

// continue operation to all method calls.
return (ContinueOperation);
}
Then compile the "EAI HTTP transport" into the .srf and copy to any servers than run the XMLPReportServer component.

Related



--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------

Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Reports
Keywords
--------------------------------------------------------------------------------
HTTPSLEEPTIME; INTEGRATION; EAI HTTP TRANSPORT; HTTP TRANSPORT; OUTBOUND WEB SERVICE
Errors
--------------------------------------------------------------------------------
SBL-EAI-04311