Webservices in Dynamics NAV 2009

HugoSilveira

Hi all,

I have one machine with NAV 2009 installed. RTC is working fine and i started the Microsoft Dynamics NAV Business Web Services service and i just can see my URL webservices in this machine. It prompt me a windows login, i give it and everything works fine.

If i try to connect from another machine, it also asks me from login but after 3 times the process is stopped. I can't see my webservices from any other machine. Any help will be much appreciated.

Thanks in advance.

Regards

HS

mohana_cse06

have you installed webservice in server machine only?
is it in domain?

what URL you are using from other machines?

HugoSilveira

Hi,

webservice is installed only in server machine.

The server and the clients are all in the same domain.

The URL is for example: http://172.19.128.1:7047/DynamicsNAV/WS/Services

Any idea?

Thanks

mohana_cse06

did you try with Server name instead of IP in URL?

HugoSilveira

yes i did but the result is the same. it doesn't work. I saw some articles about webservices like the one below, but i try it (i hope that i try it with no mystakes) and it also didn't work. I don't know what can i do more...

http://blogs.msdn.com/b/nav_developer/a ... setup.aspx

ufuk

If you manually type URL on Explorer can you see your services on the calling machine?
If you can see services but the problem occurs when you try to login are you sure there is no problem with the domain and user permissions?
If you can select your services but the problem occurs only on runtime have you checked if NetworkCredentials include domain parameter?

Nils_Peemöller

Hi,

this interesting behaviour I know from a missing setup of delegation. Have you installed SQL server and web service on the same machine? If not, you have to set up delegation and the rights for change listener. See official microsoft documentation. Unfortunately, this setup is quite tricky and time expensive.

Nils

MattKeyes

What Nils said may indeed be the case, and that setup can be very difficult and labor intensive.

You might try turning on NTLM security in the CustomSettings.config file and give it a whirl.

Change the key below to "True":

<add key="WebServicesUseNTLMAuthentication" value="True" />