SBL-EAI-04318: There is no active Inbound Web Service named '%1'.
Applies to:
Siebel System Software - Version: 7.8.2 SIA [19213] - Release: V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] Hi Tech
Database: Oracle 10.1.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-3209743841.
Symptoms
SBL-EAI-04301
Requirement is to generate WSDL files for our Inbound Web Services, but errors are reported :-
SBL-EAI-04318: There is no active Inbound Web Service named ‘'.
When one of operators is used in Port Type name (Business service name or workflow process Name) the following error is encountered
SBL-EAI-04301: There is no active Web Service with inbound port type named ‘'.
Can you please let me know what the error message and more importantly how to correct it?
thank you,
Cause
The errors were being reported when an operators (“ And “ ,” or”, “Like” etc) is used in web service or port name. From the review of log file, Siebel considers the operator in a field value as operator and create 2 conditions in a query SQL statement. Therefore the records can not be found and above error is encountered.
By example if the web service name is "A and B", following condition will be added into SQL to find the web service record
...
T1.NAME ='A' AND T1.NAME = 'B'
Change Request 12-1HSM9XY has been logged to address the non-intended behavior
Solution
As workaround, by removing the operator which is used in web service name or Port Type name (Business service name or workflow process Name) above behavior can be avoided.
You can find the information about operators in following bookshelf reference :-
Siebel Developer's Reference > Operators, Expressions, and Conditions
Related
Applies to:
Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1208748981.
Symptoms
SBL-EXL-00151, SBL-EAI-04318
Hi
I'm trying to invoke an outbound web service. After importing the WSDL, I tried importing the run-time xml entry and invoke it. I have attached the run-time xml file for your reference.
No matter what I do, I keep getting the following error in the error logs...
There is no active Web Service named 'http://tempuri.org/:OCIFSoldProductService'.(SBL-EAI-04318)(SBL-EXL-00151)
If you notice in the xml file, the web service actually has a namespace of http://xmlns.bmogc.net/ocif/2003, so I'm not sure why that's not being picked up.
I tried to go through the S_WS_WEBSERVICE, S_WS_PORT and S_WS_BNDNG_DTL relationship and everything seems to be intact.
I even tried manually re-creating the entry, but I still can't invoke it.
The full Siebel log does not shows any entries of the integration object being serialized, so obviously we didn't even get to the stage of generating the request message. I've also attached the Siebel log files with Log Level set to All.
This is really urgent. If you can give us any feedback or any pointers that would be great.
You can contact me at 416-890-8709 or 416-549-6681.
Thanks
Regards
Sanford
Solution
Message 1
For the benefit of other users:
The behavior was resolved after customer deleted all the proxy business service and the integrartion objects, and re-imported the WSDL again.
Thank you,
Siebel Technical Support
Related
Siebel System Software - Version: 7.8.2 SIA [19213] - Release: V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] Hi Tech
Database: Oracle 10.1.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-3209743841.
Symptoms
SBL-EAI-04301
Requirement is to generate WSDL files for our Inbound Web Services, but errors are reported :-
SBL-EAI-04318: There is no active Inbound Web Service named ‘
When one of operators is used in Port Type name (Business service name or workflow process Name) the following error is encountered
SBL-EAI-04301: There is no active Web Service with inbound port type named ‘
Can you please let me know what the error message and more importantly how to correct it?
thank you,
Cause
The errors were being reported when an operators (“ And “ ,” or”, “Like” etc) is used in web service or port name. From the review of log file, Siebel considers the operator in a field value as operator and create 2 conditions in a query SQL statement. Therefore the records can not be found and above error is encountered.
By example if the web service name is "A and B", following condition will be added into SQL to find the web service record
...
T1.NAME ='A' AND T1.NAME = 'B'
Change Request 12-1HSM9XY has been logged to address the non-intended behavior
Solution
As workaround, by removing the operator which is used in web service name or Port Type name (Business service name or workflow process Name) above behavior can be avoided.
You can find the information about operators in following bookshelf reference :-
Siebel Developer's Reference > Operators, Expressions, and Conditions
Related
Applies to:
Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1208748981.
Symptoms
SBL-EXL-00151, SBL-EAI-04318
Hi
I'm trying to invoke an outbound web service. After importing the WSDL, I tried importing the run-time xml entry and invoke it. I have attached the run-time xml file for your reference.
No matter what I do, I keep getting the following error in the error logs...
There is no active Web Service named 'http://tempuri.org/:OCIFSoldProductService'.(SBL-EAI-04318)(SBL-EXL-00151)
If you notice in the xml file, the web service actually has a namespace of http://xmlns.bmogc.net/ocif/2003, so I'm not sure why that's not being picked up.
I tried to go through the S_WS_WEBSERVICE, S_WS_PORT and S_WS_BNDNG_DTL relationship and everything seems to be intact.
I even tried manually re-creating the entry, but I still can't invoke it.
The full Siebel log does not shows any entries of the integration object being serialized, so obviously we didn't even get to the stage of generating the request message. I've also attached the Siebel log files with Log Level set to All.
This is really urgent. If you can give us any feedback or any pointers that would be great.
You can contact me at 416-890-8709 or 416-549-6681.
Thanks
Regards
Sanford
Solution
Message 1
For the benefit of other users:
The behavior was resolved after customer deleted all the proxy business service and the integrartion objects, and re-imported the WSDL again.
Thank you,
Siebel Technical Support
Related
תגובות
הוסף רשומת תגובה