Related content:

Question while importing the WSDL file using wizard, getting "Couldn't get list of service names from WSDL parser" error message. Question Unable to import a WSDL due to "faultCode=PARSER_ERROR" Question File Parser (CSV) Replacing characters when parsing Question Pega marketing failed due to error "Could not access HTTP invoker remote service VBD" Question Could not Parse AKDT timezone Question GetWorkingInstance() could not get instance from TypeProxy. InstanceName: microsoftOutlookAttachmentProxy1 Question Get exception Could not find instance from KeyProviderName: CRMChild Question GetWorkingInstance() could not get instance from TypeProxy. InstanceName: _ApplicationProxy1 Question Outlook unable to get could not get instance of Type Proxy: Instance Name :"microsoftOutlookMailProxy" Question SOAP service WSDL when hit from external doesnt create WO.
Contact a Moderator

Question

6
Replies
659
Views
MadhusudanS9253 Member since 2015 30 posts
Incessant
Posted: 4 years ago
Last activity: 3 years 2 months ago
Closed
Solved

getting "Could not create an instance of the WSDL parser: Failed to parse WSDL document" when importing wsdl

Hi,

On importing WSDL I am getting "Could not create an instance of the WSDL parser: Failed to parse WSDL document" failure. I see that WSDL has reference to external XSDs but those are also at the same path where WSDL resides. Not sure what could be the issue.

Can anyone pls help me out on this.

Thanks,

Madhusudan

***Updated by moderator: Lochan to add Categories***

Data Integration
Close popover
Moderation Team has archived post
Posted: 4 years ago

Hello Madhusudan,

Can you try importing in SOAP UI and does that works? If it works there can you share the WSDL?

Posted: 4 years ago

http://if I browse the wsdl file and import in SOAP UI it looks working But when I give the URL it doesn't work.It shows below error:

        Error loading [https://wwwqa.gesbcontracts.ford.com/GlobalESBIntegProvider/ExtendedServicePlanServiceV1/ExtendedServicePlanServiceV1?wsdl]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: does not close tag.

And since it has external XSD reference we have to use URL in Connector wizard( correct me if its not the case )

I am attaching WSDL and XSDs and below is the wsdl URL:

https://wwwqa.gesbcontracts.ford.com/GlobalESBIntegProvider/ExtendedServicePlanServiceV1/ExtendedServicePlanServiceV1?wsdl


Pls let me know if you need other details.

Accepted Solution
Posted: 4 years ago

Hello,

Madhusudan has communicated with me over a private message that this issue has been resolved!

Instead of importing the WSDL from "New Soap Integration" wizard he used connector and metadata wizard. It worked fine.

Regards,

Lochan  |  Online Community Moderator  |  Pegasystems Inc.

Posted: 3 years ago

I have a same situation, where I get the same error message if I use Connector and Meta Data wizard. I had to import some xsd's.


All Request/Response params generated properly from SOAP UI with same wsdl but not with Metadata accelerator

Posted: 3 years ago

Just found out that this error also is generated when the wsdl file is located on a network drive not mapped to a drive letter. I.e. if the cannonical name of the wsdl file is like \\server\share\file.wsdl paga will fail to greate the wsdl parser object.


Resultion is to copy the file to your local drive or map your server to a windows driver name (like x:)

Posted: 3 years ago

The easiest approach would be to upload the xsds in stead of wsdl first.PegaRules Application  uploads it to the Server but will say that it cannot parse the xsd(which is obvious since we are using a wizard where it looks for wsdls(with/without xsd imports).Once all the xsds you have imported in your wsdl are uploaded,Try uploading the wsdl now and it should work fine.(This is a work around, which is easy too )
Share this page LinkedIn
Copied!