BI Schedule Service SAOP Call Not Working After 22B Upgrade
(Doc ID 2884130.1)
Last updated on SEPTEMBER 24, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.4.0 version, MICC Transfer to TSC
BI Schedule Service SAOP call not working after 22B Upgrade
We are using Schedule Service SOAP WebService to call one our custom report in our SOA based integration, this functionality is working fine earlier(before 22b upgrade)'
But after 22b upgrade to our SAAS dev3 instance, this SAOP call in not working in any of our SOA integration.
ERROR
-----------------------
Getting the below error:
=======================
Error reading XMLStreamReader: Trying to bind URI 'http://www.w3.org/2000/xmlns/ to prefix "{0}" (can not be explicitly bound)
at [row,col {unknown-source}]: [1,2605]
oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : Error reading XMLStreamReader: Trying to bind URI 'http://www.w3.org/2000/xmlns/ to prefix "{0}" (can not be explicitly bound)
at [row,col {unknown-source}]: [1,2605]
=======================
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |