Skip Navigation
Expand
Service Not Found response with Connect Web Services for SOAP from add-in
Answer ID 7982   |   Last Review Date 12/19/2018

Why is my custom add-in returning 'Service Not Found, Endpoint reference address is [x] and wsa actions is [x]'?

Environment:

Desktop Add-Ins (.NET API) and Connect Web Services for SOAP

Resolution:

Add-ins coded with the Desktop Add-Ins (.NET API) commonly communicate through the SOAP API endpoint for a site interface. When configuring the soap endpoint within the add-in it is important to identify the appropriate endpoint address. The address to identify within the app.config file for the add-in should follow this guideline:

https://<site>/cgi-bin/<interface>.cfg/services/services_soap

Common mistakes that are made are to use http (https is required) and to include "?wsdl" on the end of this URL.

Available Languages for this Answer:

Notify Me
The page will refresh upon submission. Any pending input will be lost.