NAV 2009 Webservices

FSmeets

Dear all,

I'm not sure if I'm posting this in the right category, but I have an issue with the NAV 2009 Webservices.
The situation is as following:
- We are running NAV 2009 Classic on database server "A".
- I have installed the Webservices on a virtual machine "B".
- The logon for the services is a domain account.

From my local laptop I connect to http://B:7049/NAV/WS/Services and I get the login screen.
When I login with my own user account I get the following message:
<faultcode xmlns:a="urn:microsoft-dynamics-schemas/error">
a:Microsoft.Dynamics.Nav.Types.NavDatabasePasswordException
</faultcode>
<faultstring xml:lang="en-US">The user ID and password are invalid. Try again.</faultstring>
<detail>
<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">The user ID and password are invalid. Try again.</string>

But now the weird part:
- Now I connect via a RDP session to server "B"
- I connect to http://B:7049/NAV/WS/Services
- I logon with the same credentials as on my local laptop.
- Now I get the correct response from the webservices
<contractRef ref="http://ota-vm-149:7051/NAVIE/WS/SystemService&quot; xmlns="http://schemas.xmlsoap.org/disco/scl/&quot; />
<contractRef ref="http://ota-vm-149:7051/NAVIE/WS/Codeunit/Customer&quot; xmlns="http://schemas.xmlsoap.org/disco/scl/&quot; />
<contractRef ref="http://ota-vm-149:7051/NAVIE/WS/Codeunit/SalesDocument&quot; xmlns="http://schemas.xmlsoap.org/disco/scl/&quot; />
etc.
- When I return to my local laptop and connect to http://B:7049/NAV/WS/Services again, everything is working fine.

Does anyone know what the issue is and how I can solve this?
If you need more information, please let me know.

kine

This looks like problem of Kerberos and SPNs. You need to setup them correctly and correctly set up the delegation. Look for the blogs about that (e.g. on my blog... ;-)).

FSmeets

kine wrote: »

This looks like problem of Kerberos and SPNs. You need to setup them correctly and correctly set up the delegation. Look for the blogs about that (e.g. on my blog... ;-)).

Thanks for your reply, in the meanwhile we checked the SPNs but unfortunately without any success.

kine

and have you checked the AD settings of the account under which the service is running, if there is correct delegation settings? After set it correctly, you need to wait a while, stop service, clean Kerberos tickets, start again, or wait until tickets expires...