Question

5
Replies
1592
Views
 Rahul R (RahulR85)

IN
RahulR85 Member since 2016 1 post
Posted: January 25, 2017
Last activity: January 25, 2017
Posted: 25 Jan 2017 0:23 EST
Last activity: 25 Jan 2017 22:03 EST
Closed

WSDL ERROR

Hi friends , 

Show More

Hi friends , 

New SOAP Integration
Image removed.Image removed. HelpImage removed.
This record has
1
Error
in
1
place
—
Could not initialize XSD component builder: Caught exception parsing XML stream

***Moderator Edit: Vidyaranjan | Updated Categories*** 

Show Less
Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
Posted: 25 Jan 2017 0:49 EST
Sudhish Othoyoth Puthiyapurayil (othos)
PEGA
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Rahul,


Can you please explain your use case in detail?. Because the posted exception can be triggered in various scenarios.
Posted: 4 years ago
Posted: 25 Jan 2017 6:19 EST
Santanu Bhattacherjee (Santanu)
PEGA
Senior Manager - Sales Automation
Pegasystems Inc.
IN

Along with what othos suggested, I would also like to understand whether you are seeing any interesting entry in the log file or not. So please review the log and let us know .


Also, find this discussion thread which talks about similar kind of issue. 
Posted: 4 years ago
Posted: 25 Jan 2017 22:03 EST
Praneeth Purighalla (PraneethPurighalla)
PEGA
Lead System Architect
Pegasystems Inc.
IN

Most likely the WSDL whose URL you provided or the one you uploaded is invalid. This could also occur if there are leading spaces at the beginning of the WSDL content.