Developer forum

Hi Søren,
could you check if you have installed and configured correctly the NAV code unit?
Have you used the sample code unit from here?
Regards, Dmitrij

Hi

The codeunit works correctely, so does the Navision Webserivice.

We have followed the steps you linked, and we have used the sample code you link as well....

Hi Søren,
Have you tried to use the "Nav Service Test" tab in the Test App?
Is it working with the sample request
"<GetEcomData><tables><Users type="all"/></tables></GetEcomData>" or
"<GetEcomData><tables><Products type="all"/></tables></GetEcomData>"?
Before using it check the settings in the "TestServiceApp.exe.config" file, in the "NavConnector" section if it has the same settings that you use in the Dynamicweb Service configuration(file: "DynamicwebConnectorService.exe.config", "NavConnector" section).
Regards, Dmitrij

Hi

I am using the test app as well - and i get the same result, also when using the "Nav Service Test".

The settings in the two config files are the same - but with no result

Regards, Søren

Hi

Looking in the log on the DW solution there is thrown an error:

ConnectionError: Url: 'http://xx.xxx.xxx.xx:yyyy/DynamicwebService'. Error checking Web Service connection: 'Parameter request in method Process in service DWWebService3 is null! '. Request: '<GetEcomData></GetEcomData>'.

I can't see where that error originates. Looking at the decompiled code in the DynamicwebConnectorService, do not give me any clue, and seeing that the request only consites of the GetEcomData node, hints that the error comes from NAV.

The question is why is the body of the request being striped out, and where is the "strippping" happening

Regards, Kenneth

Hi,

Have you checked that all downloaded files for the connector and test app have been unblocked? (rightclick-> properties, click the "unblock" button see: https://blogs.msdn.microsoft.com/delay/p/unblockingdownloadedfile/ )

If that's not the problem, can you please show us your config file (without sensitive information, of course ).

Thanks, Jonas

Did you solve this issue or find the source of it?

BR.

Lars

In case anyone else experiences this, please check the webservice name in NAV. I may have been changed for some reason, but the connector (and test app) expects it to be DWWebService (case sensitive), as this also defines the namespace (the connector expects that to be urn:microsoft-dynamics-schemas/codeunit/DWWebService). In the above examples I would guess that the webservices were named Dynamicweb2 and Dynamicweb.