Skip to main content
Question

Build SOAP request - Unable to parse wsdl

  • September 21, 2023
  • 2 replies
  • 345 views

DeLo
Forum|alt.badge.img+4
  • Navigator | Tier 3
  • 20 replies

http://private.company.com:1234/vertex-remote-services/oseriestm/filetransfer90?wsdl

Using a verified URI (replaced domain info for security reasons), I entered it into the SOAP Web Service v3.17.0.  Then I click Build SOAP request and receive an Unable to parse wsdl error message. I import this URI into SOAPUI and it perfectly parses it. And I can execute it from SOAPUI to get the successful response. I entered all the necessary parameters in the SOAP Web Service to see if it was simply an issue with the Build SOAP request feature, and it still errors. Here’s the error when running the bot.

An unexpected error occurred.
org.ow2.easywsdl.schema.api.SchemaException: SchemaException: the imported document cannot be import at: http://www.w3.org/2005/05/xmlmime: org.ow2.easywsdl.schema.api.SchemaException: SchemaException: Can not get schema: : javax.xml.bind.UnmarshalException

 

2 other URI for the same webservice work just fine in the same bot.  Same server/domain/port info. Only this URI is causing issues.

 

2 replies

rima.sengupta
Automation Anywhere Team
Forum|alt.badge.img+9
  • Automation Anywhere Team
  • 85 replies
  • September 26, 2023

Hello @DeLo  

Thank you for sharing your question.

I would recommend that you submit a formal support ticket so of our support members can assist you with this.
To submit a support ticket, visit the Support Portal. (LINK)

If you are unable to access this page, please reach out to your account representative for troubleshooting assistance.

Rima Sengupta

Pathfinder Community Team


DeLo
Forum|alt.badge.img+4
  • Author
  • Navigator | Tier 3
  • 20 replies
  • September 26, 2023

Support ticket opened. Discovery session completed. Investigation in progress...


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings