This post is part of the Enabling Secure Connection for Web Services series.
Over the last few posts, I’ve stepped through the changes to the Web Service configuration files. With all of these changes made, there are a small number of steps to now complte, or confirm as complete.
Firstly, as the configuration files have been changed, the Microsoft Dynamics GP Service Host needs to be restarted. This can be done via the Services control panel applet.
Secondly, ensure the firewall port for the secure port is configured to allow access.
Thirdly, I’d recommend verifying the Web Services are working correctly; when you test the services, use the updated paths for https access:
Read original post Enabling Secure Connection for Web Services: Final Service Configuration at azurecurve|Ramblings of a Dynamics GP Consultant