When connecting to a Web Service, the connection is not established and the error "403 forbidden" is shown.
A Web Service goes offline after having worked previously and the error "403 forbidden" is shown.
The generic consume Web Service client in SmartStruxure doesn't have a user agent header defined. Some Web Service providers will not or no longer allow that, and denies the request when it comes from SmartStruxure.
If the same URL is entered in a browser, the page is shown.
The cause of this issue can also be that the Web Service is being polled too often.
Until it is made possible to define a customer user-agent header, you need to use another application to relay the Web Service request. This can for instance be "SBO - Web Service through a Proxy and JSON conversion" from the Exchange Community.