When you try to access Navision Web services you may encounter the following error
“This Site can’t be reached, xxxx refused to connect”
The most common reason for this error is the NAV Service is not enabled for SOAP/OData.
To enable these services, open the Microsoft Dynamics NAV Server Administration tool and select the SOAP Services Tab/ OData Services Tab and make sure the property is set to true
Enable SOAP Services and Enable OData Services to true, if you are using SOAP you just need to enable SOAP and vice versa.
You can also use the Powershell Cmdlet
Set-NAVServerConfiugration to enable the services for example to enable OData you use the following cmdlet
Set-NAVServerConfiguration -ServerInstance <ServerInstance> -keyname ODataServicesEnabled -keyvalue true
Replace <ServerInstance> with the name of the Microsoft Dynamics NAV Server instance on which to set up OData services.
Check the following link for more examples
https://msdn.microsoft.com/en-us/library/dn135246(v=nav.70).aspx
One other reason for this error is because the port is blocked and you need to create an inbound rule to allow it.
Please check this below the article you need to do the same for the web services port
If you have any other tips or suggestions, please do share them in the comments below.
3 comments:
I did not use SOAP or OData data and I had been created a role to allow port 8080, but it still refuse to connect to localhost and did not appear any error in my console.
Do u have any idea for this?
Thank you so much for providing such a unique and descriptive analysis of SOAP services.
Powerbi Read Soap
Post a Comment