Problem with wsdl in progress 11.6.4 - Forum - OpenEdge General - Progress Community

Problem with wsdl in progress 11.6.4

 Forum

Problem with wsdl in progress 11.6.4

This question is not answered

The bprowsdldoc tool is sending the following errors when trying to process this url (https://4145659-sb1.app.netsuite.com/wsdl/v2017_1_0/netsuite.wsdl) (progress 11.6.4), if I put it in the browser it shows the information without indicating any problem,

Others wsdl (with https) works perfectly..

proenv>bprowsdldoc 4145659-sb1.app.netsuite.com/.../netsuite.wsdl
Error message: 9318
Error message: 9407
Error loading WSDL document  4145659-sb1.app.netsuite.com/.../netsuite.wsdl : Fatal Error: connect operation failed (WinSock reported error=0)
  location: 4145659-sb1.app.netsuite.com/.../netsuite.wsdl (11748)

What can i do to fix it ?

Thanks

All Replies
  • Hi Jpena,

    Can you please set/export "SSLSYS_DEBUG_LOGGING=7"  and then execute bprowsdldoc command.

    It generates a cert.client.log and please attach the cert.client.log to this forum question, so that we can analyze and let you know the problem.

    Thanks,

    Sai Tharun Kollampally

  • cert.client.log

    cert.client.log file

    Thanks

    Jesús Pena

  • Hi Jpena,

    Thanks for providing cert.client.log.

    I have tried to reach "4145659-sb1.app.netsuite.com/.../netsuite.wsdl" using sslc client and it is working fine.

    Can you please execute the commands and send me the log

    sslc s_client -connect 4145659-sb1.app.netsuite.com:443 -tls1_2 -cipher ADH-AES256-GCM-SHA384 -CApath $DLC/certs -debug -msg -state > SSL.log

    pkiutil -verbose  -list <Certifcate-Alias-Name> certificate.log

    Also, can you send me the network traces by capturing the details via WIRESHARK or any other possible tool?

    Thanks,

    Sai Tharun Kollampally

  • SSL.logcertificate.log

    These are the files you requested

    Thanks

    Jesús Pena

  • Hi Jpena,

    Sorry for delayed response,currently team is busy in 12.1 release work.

    Can you please log an RFA for this, so that as soon as we complete 12.1 work, we will be able to look into this.

    After logging RFA, please try to add the captured network traces from any tool like wireshark, it will help us to understand the problem better.

    Thanks,

    Sai Tharun Kollampally