Hi All, I raised this question a week ago and am still stuck on the same problem. A quick refresh, I am unable to consume a web service from a 4Dv15.5 application (converted from 4Dv11). The v15 application is running on a Windows 2012 server, say Server1.
The 4D v11 application running on the same server (Server1) is able to call the web service to transmit an XML document with no issues. I have also verified with a separate v15 application running at another installation (Server2) that is able to transmit successfully. So it seems not to be an issue with any v15 coding issue. In all applications (v11 and v15), the same web service call is made : WEB SERVICE CALL($txtSOAP_URL;$txtSOAP_Action;txtSOAP_Method;$txtSOAP_Namespace;Web Service manual) The only difference between the soap URL on Server1 and Server2 is that on Server 1, the URL begins with “https://“ - a secured connection, while on Server2, it starts with “http://“. On Server1, however v11 does not have any problem with the “https://“ connection. Could it be s security certification issue for the v15 app, that’s why the soap server is deemed not reachable every time the web service call is made? Seems like there is very little left to be done on the 4D-end. Does anyone have any other ideas how to troubleshoot and solve this? Regards, Ronnie Tarawerkz > On 11 Apr 2018, at 1:57 pm, Ronnie Teo <ron...@tarawerkz.com> wrote: > > Hi All, > > I would like to seek some help/advise on an XML issue in 4Dv15 on Windows. > > I have an app that is currently running in v11. XML transmission via the > consumption of a hosted web service is working well. > User decides to upgrade their server from Windows Server 2008r2 to 2012 and > from v11 to v15. > > XML transmission from the v11 database when ported over to the new staging > server continues to work well. For the converted v15 application, running on > the same staging server, everything works except the XML transmission. Same > server, same port, soap URL, same web service yet it works on v11 works but > not v15. > > On v15, the Web Service Call command returns with the OK variable not equal > to 1 and a soap server not reachable response. > > Have tried comparing all the settings between the two 4D versions to make > them similar but to no avail. Does anyone have any encounters with this > issue or what could possibly have gone awry with the Web Service Call command > in v15? > > > Thanks, > Ronnie > Tarawerkz ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
