NAV 2009 R2 Webservice - strange error 500.

mihail_kolevmihail_kolev Member Posts: 379
edited 2013-07-29 in NAV Three Tier
Hello,

I have realy strange issue. I have a webservice, all delegations are set up and it works like charm

BUT

for some reason it just start to say The login failed when connecting to SQL Server when use the webservice methods from .NET (using generated network credentials) and it says Error 500 when I try to open it in Internet Explorer. This happens only when I use the full url - http://server.company.local:7047/Dynami ... S/Services

Now, the funny part - when I go to the server and type this url http://localhost:7047/DynamicsNAV/WS/Services

in Internet Explorer it works, and magically this url http://server.company.local:7047/DynamicsNAV/WS/Services also start working without anything else done.

Can anybody tell me why this is happening, maybe how to prevent it and how opening the localhost url fixes the problem.
-Mihail- [MCTS]

Answers

  • mihail_kolevmihail_kolev Member Posts: 379
    Update: there is big time of inactivity of the service (no requests) and also no logins to NAV client... Can this be related to the problem?
    -Mihail- [MCTS]
  • nttisnttis Member Posts: 8
    have you solved it?

    i've the same problem trying to access webservices from "internet".
    -error 500: <faultcode xmlns:a="urn:microsoft-dynamics-schemas/error">a:Microsoft.Dynamics.Nav.Types.NavDatabasePasswordException</faultcode>
    <faultstring xml:lang="en-US">The login failed when connecting to SQL Server noscls01\nav01.</faultstring>

    when i try from the localserver everything starts and then i'm able to access from the internet, too.

    :-k
  • skullaskulla Member Posts: 140
    Please check if the login which is using to run Web Services service has permission to the database.
  • mihail_kolevmihail_kolev Member Posts: 379
    In my case it was the problem with the SPN to the MSSQLSvc. It was not added to the trusted delegation list for the user dsa.msc -> properties for the service user->Delegation->"Services to which this account can present delegated credentials:". After adding the correct SPN to that list, the problem is gone.
    -Mihail- [MCTS]
Sign In or Register to comment.