Elisabeth, there are at least 3 things to consider/do. (If you may be thinking there's some bug you're hitting about web svcs in general on cf2018, I don't think so.)
Instead, as a preface, there may well be a single configuration change needed on the new server, but more likely the problem is that some OTHER unexpected error is happening (in the attempt to run the web service on the new server, perhaps related to something NOT specific to web services at all), and you just are not seeing that error: instead what you ARE seeing may be the calling cf2016 server tripping over that unexpected error. That is a common problem in such integration processing.
So first I'd recommend you check on the cf2018 server (serving the web service), to see if there is any error tracked there when the web service is called. Look in its cf logs. But note that if any error handler may have implemented, then the logs may not show the error. You'd need to then find where such error handling may be tracking such errors.
Since that could be challenging, the next step would be to try to call the web service directly, rather than through cfml. You could look at the cfml calling the web service, determine the url and any arguments passed in, and then call the cf2018 server's web service directly. You can try it from a browser, or you may find you need a client tool like soapui or postman. That may show the error that cf2018 is returning, rather than how currently you're seeing the error from your cf2016 code when it's not handling that error well.
Finally, it's POSSIBLE that you may simply need to configure the cf admin in 2018 to be the same as 2016, regarding the setting on the web services page, about the default web service "level" (1 or 2). That's simple to check and try, but it's too involved to elaborate further here (the difference, the ability to control that also at the app or code level, etc). So for now, just compare your cf2016 and cf2018 servers regarding that value. Are they the same? If not, and you change it, does that help?
Someone may wonder why I didn't offer that first. My reasoning is that the error shown doesn't look like one common to that setting being the cause. And either way, the first two suggestions above will serve Elisabeth (and anyone with such a migration) regarding still other web svc errors that could happen and which could have very different causes.
Let us know how that goes. I could offer much more on the points above, but some prefer brevity. I'll add also that I could easily help you solve this directly (via remote consulting), likely in as little as 15 mins, if interested. No worries if you aren't/can't/won't, in which case I hope the above gets you going.
/Charlie (troubleshooter, carehart.org)
1 Correct answer
10
Replies
AdChoices