Applies to: Siebel Call Center, MME - Version: 7.8.2.3 [19221] and later [Release: V7 and later ]
Information in this document applies to any platform.
SymptomsBackground
--------------
EAI HTTP Transport error was reported when called from one server. But if user was switched to another server in the same enterprise, the call worked.
Problem
---------
In the object manager log file the following message was seen :-
SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 503'
Environment
---------------
Siebel - 7.8.2.3
DB - Oracle 9
OS - Windows 2003
CauseWith detailed logging (change evtloglvl %=4 for comp sseobjmgr_enu) it could be seen that the HTTP request was refused due to proxy configuration (outside Siebel control) :-
EAITransport EAITransportDebug 4 0 2008-11-11 11:34:32 *** HTTP response Headers from Data Send request:
HTTP/1.0 503 Service Unavailable
Server: squid/2.6.STABLE5
Date: Tue, 11 Nov 2008 10:34:31 GMT
Content-Type: text/html
Content-Length: 1236
Expires: Tue, 11 Nov 2008 10:34:31 GMT
X-Squid-Error: ERR_DNS_FAIL 0
X-Cache: MISS from http-proxy
X-Cache-Lookup: MISS from http-proxy:8080
X-Cache: MISS from http-proxy.abcdef.org
X-Cache-Lookup: MISS from http-proxy.abcdef.org:8080
Via: 1.0 http-proxy:8080 (squid/2.6.STABLE5), 1.0 http-proxy.abcdef.org:8080 (squid/2.6.STABLE5)
Proxy-Connection: close
Update to SR #3-816952432: SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 503'
SolutionThis was resolved with support from local server team. The operating system user for the erroring machine had incorrect proxy configuration, and when it was changed, the EAI HTTP Transport requests were successful.
Applies to: Siebel CRM - Version: 7.5.3 [16157] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.
DescriptionDun & Bradstreet (DNB) have changed their web site which is used by Siebel to access DNB account information. This change by DNB is because of a migration of their Secure Site and Standard SSL Certificates from a single tier certificate hierarchy to a new more secure two-tier hierarchy.
Likelihood of OccurrenceThis change will affect all Siebel users that use the search and purchase of DNB account information in the Siebel application.
Possible SymptomsConnecting to the old web address gives the following error when searching for a DNB account in the Site Map>D&B view:
HTTP Request error during 'Submitting data Send HTTP request': 'Status Code 504' (SBL-EAI-04117)
Workaround or Resolution(1) Change the DNB web site
The change to the DNB web site in Siebel is implemented in the Site Map>Administration Integration>WI Symbolic URL List>Symbolic URL Administration view and search for the name DNBGlobalAccess
The URL is changed from:
https://globalaccess.dnb.com/access/scripts/broker.asp
To the value:
https://toolkit.dnb.com/access/scripts/broker.asp
The same DNB user Id and password can still be used on the new DNB web site.
(2) Siebel 7.5.3 on Unix server
There are problems connecting to the new DNB web site using Siebel version 7.5.3 on a Unix server with Mainsoft (Mainwin 502). The following is the proposed work around as documented in the CR 10539523 and FR 12-1NVVV7U.
On 7.5.3 Unix, route the DNB requests via the Windows Server for connecting to DNB; Alternatively, Customers can upgrade to 7.7 Unix (which uses Mainwin 502 SP1 from Mainsoft) or a later version to uptake the new SSL updates from DNB.
(3) Java Runtime Environment
Customers using the JAVA Toolkit need to check what version of JRE they are using. It is recommended for JRE versions to be upgraded at the customer site in order to successfully negotiate a connection to the new DNB web site. The following document from Sun provides more detail:
http://java.com/en/download/help/cacerts.xml
Customers must be running on one of the following range of versions:
JRE 1.4.2_03 and later
JRE 1.4.1_06 and later
JRE 1.3.1_10 and later
(4) SSL Certificates
DNB is completing a migration of Secure Site and Standard SSL Certificates from a single tier certificate hierarchy to a new more secure two-tier hierarchy. Customers using the JAVA Toolkit need to check which SSL Client they are using. Customers can either use the SSL client provided with the JAVA Toolkit or a client from a third party. For all customers overriding the Sun JSSE library supplied along with Java Toolkit and using their own or any other third party SSL client, upgrade to the higher version of the SSL client and possibly the JRE would be highly recommended.
Java Secure Socket Extension (JSSE) 1.0.2 is a Java package that enables secure Internet communications - https://toolkit.dnb.com/locked/resource/InstJT.html?stat_link=020202&id=71ECE9A8785069230437
(5) How to Contact DNB
If you have any questions, you may contact Toolkit Tech Support on email address toolkit_techsupport@dnb.com or at the US phone number 1-800-234-3867 Ext 7001.
Applies to: Siebel Marketing - Version: 7.8.2.11[19244] and later [Release: V7 and later ]
Information in this document applies to any platform.
***Checked for relevance on 20-Jan-2011***
Symptoms
Customer (re-)configured their environment with Siebel 7.8.2.11 in one webserver and OBI EE 10.1.3.4 in another webserver.
Except Campaign load everything is working good. Even segmention select segment is working.
During campaign load the following error is received:
Error/Warning : Error invoking service 'Mktg Data Load Service', method 'PrepareCache' at step 'Prepare Cahce'.(SBL-BPR-00162)
--
HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 403'(SBL-EAI-04117)
Cause
Customer found an error in IIS log and an incorrect/missings setting for allowing the (load balanced) server
Solution
After granting access in IIS to the failing server the campaign load worked.
Applies to: Siebel Advanced Search - Version: 8.1.1.1 [21211] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsOn : 8.1.1.x version, when attempting to execute a search operation, the following error occurs.
ERROR
-----------------------
HTTP Request error during '<?>': '<?>'(SBL-EAI-04117)
STEPS
-----------------------
The issue can be reproduced with following steps:
1. Install Siebel 8.1.1.x and OSES 10.1.8.4
2. Implement ACR452.
3. Configure the Siebel Search functionality.
4. Execute a search operation entering a keyword.
5. The operation fails with error:
HTTP Request error during '<?>': '<?>'(SBL-EAI-04117)
CauseParameter 'Search Engine Config Filename' was set incorrectly:
Search Engine Config Filename = \\10.217.30.73\fs\SSC\config\Search_Engine_Config.xml]
The parameter shouldn't contain character ].
SolutionIn order to solve the issue, follow the bellow steps:
1. Go to Administration – Search > Search Engine Settings and set parameter as bellow:
Search Engine Config Filename =\\10.217.30.73\fs\SSC\config\Search_Engine_Config.xml
2. Logout Siebel.
3. Login Siebel.
4. Execute again a search operation, entering a keyword.
5. Verify if the behavior continues.
Applies to: Siebel Marketing - Version: 8.1.1 SIA [21111] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
Comments
--------
=== ODM Issue Clarification ===
From Landing Site screen, in Landing Page view , while doing preview getting this error.
Also Same error is encountered in Preview and Deploy in View.
Error from UI
---------------------------
Siebel
---------------------------
HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'(SBL-EAI-04117)
---------------------------
OK
---------------------------
Error in ObjMgr Log
____Object Mgr Log __________
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (httptransport.cpp (1631)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 500'
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (httptransport.cpp (981)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (xmlcnv.cpp (1727)) SBL-EAI-00247: Fatal Error in XML Parser at line 28, column 188: Expected end of tag 'HR'
Cause
Comments
--------
=== ODM Cause Determination ===
Wrong parameter setting in properties file:
WebSurveyHandlerClassName = oracle.apps.sem.wsd.runtime.queueing.MBQQueueHandle
Comments
--------
=== ODM Cause Justification ===
Verified against working instance where it is:
WebSurveyHandlerClassName = oracle.apps.sem.wsd.runtime.queueing.MBQQueueHandler
Solution
Comments
--------
=== ODM Solution / Action Plan ===
In Siebel Marketing Installation and Administration Guide Version 8.1 > Setting Up Web Marketing > Setting Up Siebel Web Marketing > To configure the Web Survey Daemon > step 4 it says 'MBQQueueHandle', but it needs to be 'MBQQueueHandler' (note the 'r' at the end).
Documentation defect (#12-1XF0FNJ 'Typo in documentation regarding MBQQueueHandler') has been logged to address this.
ReferencesBUG:10588695 - TYPO IN DOCUMENTATION REGARDING MBQQUEUEHANDLER
NOTE:785710.1 - 'Submit' button not showing on a deployed Survey on version 8.1.1
Applies to: Siebel System Software - Version: 7.5.3 [16157] to 8.1.1 [21112] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Microsoft Windows (32-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11.0
This document was previously published as Siebel SR 38-3189300651.
SymptomsWhen an outbound web service was called from Siebel, the following error was raised:
HTTP Request Error during 'Submit Data Send HTTP Request': 'Status code - 401' (SBL-EAI-04117).
This same web service was called successfully from other web service clients but failed only when called from Siebel.
CauseThe cause of the issue was the lack of permissions of the user running the Siebel Server on the Share Point server that existed between Siebel and the outbound web service.
SolutionThe HTTP status code 401 means that there are some issues regarding unauthorized access to the web service. After the customer’s research, he found that it was not a proxy server issue, but rather an issue with the SharePoint userid and password.
Although the user id and password are not sent as parameters in the web service, SharePoint uses login credentials which are sent by the web server when sending the xml.
When testing the web service from his local client, the service worked because his user id and password were setup as an admin on the SharePoint server. However, when he attempted to test the same web service using the thin client, the user id and password of the user running the Siebel Server process was passed to SharePoint.
The solution was to run the Siebel Server service as a user that has permissions on the SharePoint server.
Applies to: Siebel Reports - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsFollowing an installation or upgrade of the Siebel BI Publisher Report Server the following error messages may be seen within either the log files for the XMLPReportServer component or within the logs for the requesting Object Manager :
ObjMgrLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (httptransport.cpp (981)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
ObjMgrLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (soapbinding.cpp (564)) SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'getTemplateParameters' exists in SOAP message.
ObjMgrBusServiceLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (outdisp.cpp (209)) SBL-EAI-04308: Operation 'getTemplateParameters' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceService' at port 'PublicReportService_v11' failed with the following explanation: "No such operation 'getTemplateParameters'".
ObjMgrBusServiceLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (xmlpadaptersvc.cpp (2799)) SBL-EAI-04308: Operation '<?>' of Web Service '<?>.<?>' at port '<?>' failed with the following explanation: "<?>".
When these error messages are reported within the log files the intended reporting functionality will fail but may manifest itself differently dependent on the context.
CauseThese error messages are returned when the outbound webservice call is for an operation which does not exist within the target webservice.
In the Siebel BI Publisher Integration this behavior is most likely to occur because the outbound webservice has been misconfigured and is calling the wrong version of the BI Publisher PublicReportService.
SolutionWhen running Siebel 8.1.1 the outbound webservice call will show the following configuration :
Outbound WebService.Name : PublicReportServiceService
Outbound WebService.Namespace : http://xmlns.oracle.com/oxp/service/PublicReportService
ServicePort.Name : PublicReportService
ServicePort.ServiceDisplayName : PublicReportService
ServicePort.Address : http://<BIPublisherMachineName>:9704/xmlpserver/services/PublicReportService
When running Siebel 8.1.1.1 the outbound webservice call will be to the PublicReportService_v11 and show the following configuration :
Outbound WebService.Name : PublicReportServiceService
Outbound WebService.Namespace : http://xmlns.oracle.com/oxp/service/v11/PublicReportService
ServicePort.Name : PublicReportService_v11
ServicePort.ServiceDisplayName : PublicReportService
ServicePort.Address : http://<BIPublisherMachineName>:9704/xmlpserver/services/PublicReportService_v11
A Documentation Bug #12-1WF7BTL has been raised to ensure that the Reports Administration Guide makes correct references to the exposure of the Outbound Web Service.
Applies to: Siebel Reports - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] Auto
Database: Oracle 10g
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-2688604731.
SymptomsWe have a serious problem with the report server in our Production enviroment. This is urgent as the users are not able to take out the reports .
The setup of Siebel & report server environment was done on 26-Oct-05. The report server was working fine till 25-nov-05. On the morning of 25-Nov-05, the report server stopped working. When we click on reports it gives the following error message.
"Could not connect to the Reports Server. Server: 's185b0028', Volume: 's185b0028'. Status : '<?>'. Please contact your administrator."
We have gone through the SRs & checked the actuate parameters settings. We have tried to point our existing (test)siebel server to the report server (development) enviorment but that too is not working and same error appears when tried to run a report thro web client.
I am unable to connect to the report server through the dedicated client also.
The same problem occurred in our training environment also but after some time it worked again fine .
SolutionFor the benefit of other readers,
The user was reported to have the following error when trying to perform User Synchronization or run a report in Web Client,
"Could not connect to the Reports Server. Server: 's185a0028', Volume: 's185a0028'. Status : '<?>'. Please contact your administrator."
However when the same user tries to perform user synchronization or schedule from a Dedicated Web Client, there is no error. Both the eAutobjMgr_enu "Actuate Server Report Server" parameter (in OM) or "ReportServerHost" parameter (in CFG) are given the same reportserver host name and port address.
Through investigation after turning the Report Server log level = 5, it shows that the eAutoOjbmgr_enu log is reported the following error.
2005-11-28 13:25:44 (httptransport.cpp (1407)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 407'Report Server Report Server Method Exit 5 0
This shows that there is an issue in sending a command through the Object Manager to the report server through web services and that the code was failing to invoke the HTTP Transport Service.
We don't think the problem is with the production report server, but rather the production siebel server side since the development siebsrvr can send/run the report against the production report server.
Through a search on My Oracle Support, there are a few postings that are related to this EAI HTTP Transport which is related to the proxy server. Eventually the issue was resolved after the customer changed the the proxy settings on both of the Siebel servers.
Related keyword 'Status code - 407' to find out these posting 38-2094012637 , 38-923230151 or 38-1753008181
Information in this document applies to any platform.
SymptomsBackground
--------------
EAI HTTP Transport error was reported when called from one server. But if user was switched to another server in the same enterprise, the call worked.
Problem
---------
In the object manager log file the following message was seen :-
SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 503'
Environment
---------------
Siebel - 7.8.2.3
DB - Oracle 9
OS - Windows 2003
CauseWith detailed logging (change evtloglvl %=4 for comp sseobjmgr_enu) it could be seen that the HTTP request was refused due to proxy configuration (outside Siebel control) :-
EAITransport EAITransportDebug 4 0 2008-11-11 11:34:32 *** HTTP response Headers from Data Send request:
HTTP/1.0 503 Service Unavailable
Server: squid/2.6.STABLE5
Date: Tue, 11 Nov 2008 10:34:31 GMT
Content-Type: text/html
Content-Length: 1236
Expires: Tue, 11 Nov 2008 10:34:31 GMT
X-Squid-Error: ERR_DNS_FAIL 0
X-Cache: MISS from http-proxy
X-Cache-Lookup: MISS from http-proxy:8080
X-Cache: MISS from http-proxy.abcdef.org
X-Cache-Lookup: MISS from http-proxy.abcdef.org:8080
Via: 1.0 http-proxy:8080 (squid/2.6.STABLE5), 1.0 http-proxy.abcdef.org:8080 (squid/2.6.STABLE5)
Proxy-Connection: close
Update to SR #3-816952432: SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 503'
SolutionThis was resolved with support from local server team. The operating system user for the erroring machine had incorrect proxy configuration, and when it was changed, the EAI HTTP Transport requests were successful.
Applies to: Siebel CRM - Version: 7.5.3 [16157] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.
DescriptionDun & Bradstreet (DNB) have changed their web site which is used by Siebel to access DNB account information. This change by DNB is because of a migration of their Secure Site and Standard SSL Certificates from a single tier certificate hierarchy to a new more secure two-tier hierarchy.
Likelihood of OccurrenceThis change will affect all Siebel users that use the search and purchase of DNB account information in the Siebel application.
Possible SymptomsConnecting to the old web address gives the following error when searching for a DNB account in the Site Map>D&B view:
HTTP Request error during 'Submitting data Send HTTP request': 'Status Code 504' (SBL-EAI-04117)
Workaround or Resolution(1) Change the DNB web site
The change to the DNB web site in Siebel is implemented in the Site Map>Administration Integration>WI Symbolic URL List>Symbolic URL Administration view and search for the name DNBGlobalAccess
The URL is changed from:
https://globalaccess.dnb.com/access/scripts/broker.asp
To the value:
https://toolkit.dnb.com/access/scripts/broker.asp
The same DNB user Id and password can still be used on the new DNB web site.
(2) Siebel 7.5.3 on Unix server
There are problems connecting to the new DNB web site using Siebel version 7.5.3 on a Unix server with Mainsoft (Mainwin 502). The following is the proposed work around as documented in the CR 10539523 and FR 12-1NVVV7U.
On 7.5.3 Unix, route the DNB requests via the Windows Server for connecting to DNB; Alternatively, Customers can upgrade to 7.7 Unix (which uses Mainwin 502 SP1 from Mainsoft) or a later version to uptake the new SSL updates from DNB.
(3) Java Runtime Environment
Customers using the JAVA Toolkit need to check what version of JRE they are using. It is recommended for JRE versions to be upgraded at the customer site in order to successfully negotiate a connection to the new DNB web site. The following document from Sun provides more detail:
http://java.com/en/download/help/cacerts.xml
Customers must be running on one of the following range of versions:
JRE 1.4.2_03 and later
JRE 1.4.1_06 and later
JRE 1.3.1_10 and later
(4) SSL Certificates
DNB is completing a migration of Secure Site and Standard SSL Certificates from a single tier certificate hierarchy to a new more secure two-tier hierarchy. Customers using the JAVA Toolkit need to check which SSL Client they are using. Customers can either use the SSL client provided with the JAVA Toolkit or a client from a third party. For all customers overriding the Sun JSSE library supplied along with Java Toolkit and using their own or any other third party SSL client, upgrade to the higher version of the SSL client and possibly the JRE would be highly recommended.
Java Secure Socket Extension (JSSE) 1.0.2 is a Java package that enables secure Internet communications - https://toolkit.dnb.com/locked/resource/InstJT.html?stat_link=020202&id=71ECE9A8785069230437
(5) How to Contact DNB
If you have any questions, you may contact Toolkit Tech Support on email address toolkit_techsupport@dnb.com or at the US phone number 1-800-234-3867 Ext 7001.
Applies to: Siebel Marketing - Version: 7.8.2.11[19244] and later [Release: V7 and later ]
Information in this document applies to any platform.
***Checked for relevance on 20-Jan-2011***
Symptoms
Customer (re-)configured their environment with Siebel 7.8.2.11 in one webserver and OBI EE 10.1.3.4 in another webserver.
Except Campaign load everything is working good. Even segmention select segment is working.
During campaign load the following error is received:
Error/Warning : Error invoking service 'Mktg Data Load Service', method 'PrepareCache' at step 'Prepare Cahce'.(SBL-BPR-00162)
--
HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 403'(SBL-EAI-04117)
Cause
Customer found an error in IIS log and an incorrect/missings setting for allowing the (load balanced) server
Solution
After granting access in IIS to the failing server the campaign load worked.
Applies to: Siebel Advanced Search - Version: 8.1.1.1 [21211] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsOn : 8.1.1.x version, when attempting to execute a search operation, the following error occurs.
ERROR
-----------------------
HTTP Request error during '<?>': '<?>'(SBL-EAI-04117)
STEPS
-----------------------
The issue can be reproduced with following steps:
1. Install Siebel 8.1.1.x and OSES 10.1.8.4
2. Implement ACR452.
3. Configure the Siebel Search functionality.
4. Execute a search operation entering a keyword.
5. The operation fails with error:
HTTP Request error during '<?>': '<?>'(SBL-EAI-04117)
CauseParameter 'Search Engine Config Filename' was set incorrectly:
Search Engine Config Filename = \\10.217.30.73\fs\SSC\config\Search_Engine_Config.xml]
The parameter shouldn't contain character ].
SolutionIn order to solve the issue, follow the bellow steps:
1. Go to Administration – Search > Search Engine Settings and set parameter as bellow:
Search Engine Config Filename =\\10.217.30.73\fs\SSC\config\Search_Engine_Config.xml
2. Logout Siebel.
3. Login Siebel.
4. Execute again a search operation, entering a keyword.
5. Verify if the behavior continues.
Applies to: Siebel Marketing - Version: 8.1.1 SIA [21111] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
Comments
--------
=== ODM Issue Clarification ===
From Landing Site screen, in Landing Page view , while doing preview getting this error.
Also Same error is encountered in Preview and Deploy in View.
Error from UI
---------------------------
Siebel
---------------------------
HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'(SBL-EAI-04117)
---------------------------
OK
---------------------------
Error in ObjMgr Log
____Object Mgr Log __________
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (httptransport.cpp (1631)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 500'
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (httptransport.cpp (981)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (xmlcnv.cpp (1727)) SBL-EAI-00247: Fatal Error in XML Parser at line 28, column 188: Expected end of tag 'HR'
Cause
Comments
--------
=== ODM Cause Determination ===
Wrong parameter setting in properties file:
WebSurveyHandlerClassName = oracle.apps.sem.wsd.runtime.queueing.MBQQueueHandle
Comments
--------
=== ODM Cause Justification ===
Verified against working instance where it is:
WebSurveyHandlerClassName = oracle.apps.sem.wsd.runtime.queueing.MBQQueueHandler
Solution
Comments
--------
=== ODM Solution / Action Plan ===
In Siebel Marketing Installation and Administration Guide Version 8.1 > Setting Up Web Marketing > Setting Up Siebel Web Marketing > To configure the Web Survey Daemon > step 4 it says 'MBQQueueHandle', but it needs to be 'MBQQueueHandler' (note the 'r' at the end).
Documentation defect (#12-1XF0FNJ 'Typo in documentation regarding MBQQueueHandler') has been logged to address this.
ReferencesBUG:10588695 - TYPO IN DOCUMENTATION REGARDING MBQQUEUEHANDLER
NOTE:785710.1 - 'Submit' button not showing on a deployed Survey on version 8.1.1
Applies to: Siebel System Software - Version: 7.5.3 [16157] to 8.1.1 [21112] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Microsoft Windows (32-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11.0
This document was previously published as Siebel SR 38-3189300651.
SymptomsWhen an outbound web service was called from Siebel, the following error was raised:
HTTP Request Error during 'Submit Data Send HTTP Request': 'Status code - 401' (SBL-EAI-04117).
This same web service was called successfully from other web service clients but failed only when called from Siebel.
CauseThe cause of the issue was the lack of permissions of the user running the Siebel Server on the Share Point server that existed between Siebel and the outbound web service.
SolutionThe HTTP status code 401 means that there are some issues regarding unauthorized access to the web service. After the customer’s research, he found that it was not a proxy server issue, but rather an issue with the SharePoint userid and password.
Although the user id and password are not sent as parameters in the web service, SharePoint uses login credentials which are sent by the web server when sending the xml.
When testing the web service from his local client, the service worked because his user id and password were setup as an admin on the SharePoint server. However, when he attempted to test the same web service using the thin client, the user id and password of the user running the Siebel Server process was passed to SharePoint.
The solution was to run the Siebel Server service as a user that has permissions on the SharePoint server.
Applies to: Siebel Reports - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsFollowing an installation or upgrade of the Siebel BI Publisher Report Server the following error messages may be seen within either the log files for the XMLPReportServer component or within the logs for the requesting Object Manager :
ObjMgrLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (httptransport.cpp (981)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
ObjMgrLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (soapbinding.cpp (564)) SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'getTemplateParameters' exists in SOAP message.
ObjMgrBusServiceLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (outdisp.cpp (209)) SBL-EAI-04308: Operation 'getTemplateParameters' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceService' at port 'PublicReportService_v11' failed with the following explanation: "No such operation 'getTemplateParameters'".
ObjMgrBusServiceLog Error 1 000047a24b1c0048:0 2009-12-21 14:27:57 (xmlpadaptersvc.cpp (2799)) SBL-EAI-04308: Operation '<?>' of Web Service '<?>.<?>' at port '<?>' failed with the following explanation: "<?>".
When these error messages are reported within the log files the intended reporting functionality will fail but may manifest itself differently dependent on the context.
CauseThese error messages are returned when the outbound webservice call is for an operation which does not exist within the target webservice.
In the Siebel BI Publisher Integration this behavior is most likely to occur because the outbound webservice has been misconfigured and is calling the wrong version of the BI Publisher PublicReportService.
SolutionWhen running Siebel 8.1.1 the outbound webservice call will show the following configuration :
Outbound WebService.Name : PublicReportServiceService
Outbound WebService.Namespace : http://xmlns.oracle.com/oxp/service/PublicReportService
ServicePort.Name : PublicReportService
ServicePort.ServiceDisplayName : PublicReportService
ServicePort.Address : http://<BIPublisherMachineName>:9704/xmlpserver/services/PublicReportService
When running Siebel 8.1.1.1 the outbound webservice call will be to the PublicReportService_v11 and show the following configuration :
Outbound WebService.Name : PublicReportServiceService
Outbound WebService.Namespace : http://xmlns.oracle.com/oxp/service/v11/PublicReportService
ServicePort.Name : PublicReportService_v11
ServicePort.ServiceDisplayName : PublicReportService
ServicePort.Address : http://<BIPublisherMachineName>:9704/xmlpserver/services/PublicReportService_v11
A Documentation Bug #12-1WF7BTL has been raised to ensure that the Reports Administration Guide makes correct references to the exposure of the Outbound Web Service.
Applies to: Siebel Reports - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] Auto
Database: Oracle 10g
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-2688604731.
SymptomsWe have a serious problem with the report server in our Production enviroment. This is urgent as the users are not able to take out the reports .
The setup of Siebel & report server environment was done on 26-Oct-05. The report server was working fine till 25-nov-05. On the morning of 25-Nov-05, the report server stopped working. When we click on reports it gives the following error message.
"Could not connect to the Reports Server. Server: 's185b0028', Volume: 's185b0028'. Status : '<?>'. Please contact your administrator."
We have gone through the SRs & checked the actuate parameters settings. We have tried to point our existing (test)siebel server to the report server (development) enviorment but that too is not working and same error appears when tried to run a report thro web client.
I am unable to connect to the report server through the dedicated client also.
The same problem occurred in our training environment also but after some time it worked again fine .
SolutionFor the benefit of other readers,
The user was reported to have the following error when trying to perform User Synchronization or run a report in Web Client,
"Could not connect to the Reports Server. Server: 's185a0028', Volume: 's185a0028'. Status : '<?>'. Please contact your administrator."
However when the same user tries to perform user synchronization or schedule from a Dedicated Web Client, there is no error. Both the eAutobjMgr_enu "Actuate Server Report Server" parameter (in OM) or "ReportServerHost" parameter (in CFG) are given the same reportserver host name and port address.
Through investigation after turning the Report Server log level = 5, it shows that the eAutoOjbmgr_enu log is reported the following error.
2005-11-28 13:25:44 (httptransport.cpp (1407)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 407'Report Server Report Server Method Exit 5 0
This shows that there is an issue in sending a command through the Object Manager to the report server through web services and that the code was failing to invoke the HTTP Transport Service.
We don't think the problem is with the production report server, but rather the production siebel server side since the development siebsrvr can send/run the report against the production report server.
Through a search on My Oracle Support, there are a few postings that are related to this EAI HTTP Transport which is related to the proxy server. Eventually the issue was resolved after the customer changed the the proxy settings on both of the Siebel servers.
Related keyword 'Status code - 407' to find out these posting 38-2094012637 , 38-923230151 or 38-1753008181
No comments:
Post a Comment