Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-09004: XML schema document located at '%1' could not be parsed.
ScopeThis document is informational and intended for any user.
SBL-EAI-09004: XML schema document located at '%1' could not be parsed.ExplanationThere was an error getting and/or parsing an XML schema document from a URL.
Corrective ActionVerify the URL refers to a valid XML document
Applies to: Siebel System Software - Version: 7.8.2.5 SIA [19227] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Solaris Operating System (SPARC 64-bit)
Product Release: V7 (Professional)
Version: 7.7.2.2 [18356]
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: HP 9000 Series HP-UX
This document was previously published as Siebel SR 38-2217436991.
""""Checked for relevance on 29-OCT-2010""""
SymptomsSBL-EAI-09004, SBL-UNU-00247
Hi,
I am importing a wsdl file using the web service wizard for connectivity to an external soap web service.
I am getting the following error messages:
The http://schemas.xmlsoap.org/wsdl/:operation 'updateDocument' was ignored. Error importing XML schema via method 'GetIntObjByType' for 'type' 'ContentBean' in 'urn:IQuadContentService'(SBL-EAI-08009)
XML Schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-UNU-00247)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:The host/address 'www.w3.org' could not be resolved(SBL-UNU-00247)
This looks like there is a connectivity issue to the internet, but the internet connectivity seems fine on the PC I am using. Also I have been able to import a different wsdl which points to a public soap service which imports fine and also uses the same xml schema file available on the internet at w3.org. I have attached the log file and wsdl file which is causing us the problem.
Causefeature unavailable. Tools needs file access to xsd files referenced in the WSDL.
Solution
The same wsdl could be imported by Siebel Technical Support without error. The reason for the error at the customer site was due to the use of a proxy server (check Explorer > Tools > Internet Options > Connections, and click LAN Setting). One suggestion was to configure the settings to bypass the proxy server for the www.w3.org urls. The customer instead used a dial up connection to avoid the proxy server, and was able to import the wsdl ok.
BUG: 10483854 has previously been logged to request that Tools support use of a proxy server when accessing the url (still open at the time of writing).
ReferencesBUG:10483854 - TOOLS MUST SUPPORT A PROXY SERVER WHEN IMPORTING WSDL
NOTE:1076251.1 - Master Note for Siebel Web Services
Applies to: Siebel CRM - Version: 8.0.0.5 SIA [20420] and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 04-Jan-2011***
SymptomsWhen I try to import a WSDL File, I'm getting following errors.
Project: CM Interface
WSDL file to import: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.wsdl
Run-time configuration data file: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.xml
Log File: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.log
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'BPEL_CAMB_DOMICILIOS' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'BPEL_CAMB_DOMICILIOSPort' can not be imported. PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.cablemas.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
.(SBL-EAI-04331)
CauseIncreasing the Tools Client log the additional information was collected.
a) Instructions to increase Tools Client log.
You have to set the following System Environment Variables:
SIEBEL_LOG_EVENTS=5
To set up environment variables perform the following steps:
Start > Settings > Control Panel > System.
Click on the Advanced tab and then click on the Environment Variables button.
Under the System variables view, click the New button and add the variable names and values mentioned above. Click the Ok button when finished. After that, you have to restart the Tools Client.
The detailed siebdev.log file should be generated.
b) In the siebdev.log file
WebSvcDesign XSDImpWarning 2 000000024a520670:0 2009-07-06 17:53:49 [0] Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=file:///C:\Shared\WSDL2\INT-210-BPEL-CAMB_DOMICILIOS.xsd(SBL-EAI-00247) (IDS_XMLCNV_ERR_FTLPARSE)
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (xsdcontext.cpp (693)) SBL-EAI-09004: XML Schema document located at 'INT-210-BPEL-CAMB_DOMICILIOS.xsd' could not be parsed.
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (wsimpwiz.cpp (2163)) SBL-EAI-04331: PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
c) As the error log indicated the WSDL file points to an xsd file that could not be imported because it does not exist in the same directory where the WSDL file is located.
The following import instruction in the WSDL file triggers this event.
<import namespace="http://www.server.com/SBLCambioDomicilios" schemaLocation="INT-210-BPEL-CAMB_DOMICILIOS.xsd"/>
SolutionPlease move the XSD file to the same directory where the WSDL file is located.
Best Regards
Oracle Support
ReferencesNOTE:1076251.1 - Master Note for Siebel Web Services
Applies to: Siebel CRM - Version: 7.8.2.4 [19224] - Release: V7
Information in this document applies to any platform.
SymptomsError is reported when importing customer wsdl for outbound web service :-
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'HubPartnerSSO' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'HubPartnerSSOSOAP' can not be imported. PortType 'HubPartnerSSOPort' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'getTargetUrlSSO' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'getUrlPartnerSSOIn' in 'http://schemas.bnnpa.com/pub/commons/HubPartnerSSO/v1'(SBL-EAI-08009)
XML Schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:The host/address 'www.w3.org' could not be resolved(SBL-UNU-00247).(SBL-EAI-04331)
.
CauseThe wsdl contains a weakly typed schema definition (xs:anyType) :-
<xs:element name="ContextData" type="xs:anyType" minOccurs="0" maxOccurs="1">
SolutionWith the 'xs:anyType' replaced by 'xs:string', the wsdl can be imported ok.
Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM Keywords | |
WEB SERVICES; WSDL; XML SCHEMA; OUTBOUND | |
Errors | |
SBL-EAI-04340; SBL-UNU-00247; SBL-EAI-08009; SBL-EAI-04331; SBL-EAI-09004; SBL-EAI-04333 | |
אין תגובות:
הוסף רשומת תגובה