Question5Replies1517Views RahulR85 Member since 2016 1 post Posted: 3 years agoLast activity: 3 years 7 months ago Closed WSDL ERRORHi friends , New SOAP Integration HelpThis record has1Errorin1place—Could not initialize XSD component builder: Caught exception parsing XML stream***Moderator Edit: Vidyaranjan | Updated Categories*** Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! 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: 3 years agoothos PEGA replied to RahulR85Hi Rahul, Can you please explain your use case in detail?. Because the posted exception can be triggered in various scenarios. Posted: 3 years agoSantanu PEGA replied to RahulR85Along 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: 3 years agoARVINDMALAV PEGA replied to RahulR85Can you please review the XSD to see if its valid? Posted: 3 years agoArun_Mahanty PEGA replied to RahulR85Hi Rahul, You can have a look at the following article https://pdn.pega.com/support-articles/metadata-accelerator-does-not-par… . Thanks, Arun Posted: 3 years agoPraneethPurighalla PEGA replied to RahulR85Most 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.