This content has been marked as final. Show 1 reply
In order for a web service request to be answered, a process must be running that binds to the web service. The problem you have is that there is no process running, and so nothing in OEDQ consuming or 'listening' to the web service request.
Depending on your installation, you should have a job to run (that will in turn run a process, specifying the correct data interface bindings to bind the process to the web service).
Are you also using EDQ Address Verification?