NAV5.00 Web Services 3-tier setup

TFCrowtherTFCrowther Member Posts: 35
edited 2012-11-29 in NAV Three Tier
Hi

Using a NAV5.00 database I’ve upgraded the executable to use NAV 2009 R2.

I copied the system tables 2000000000+ from a NAV 2009 R2 database into the NAV5.00 database.
Along with FORM810 Web Services.

Set File>Database>Alter>Options> Enable for Microsoft Dynamics NAV Server = YES.

I then installed the NAV Services on the NAV Server and pointed the CustomSettings.config file to the NAV5.00 database on the SQL Server.
Configured the SPN’s and Delegation etc.

Published a simple Web Service and consumed the Web Service on NAV Server.
All successful so far.

But trying to consume the Web Service on a 3-tier client works once but fails on subsequent attempts?

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="urn:microsoft-dynamics-schemas/error">a:Microsoft.Dynamics.Nav.Types.NavDatabasePasswordException</faultcode><faultstring xml:lang="en-NZ">The login failed when connecting to SQL Server AKL-SVR-SQL3\SQL.</faultstring><detail><string xmlns="http://schemas.microsoft.com/2003/10/Serialization/"&gt;The login failed when connecting to SQL Server AKL-SVR-SQL3\SQL.</string></detail></s:Fault></s:Body></s:Envelope>

To re-enable I run a GET on the Web Service on the NAV Server and it somehow clears the issue so I can again consume the Web Service on a 3-tier client???

Basically is 3-tier web services incompatible with NAV5.00 and I should stick with 2-tier or is it likely to be some weird caching issue failing the login on subsequent attempts?

Thanks

Comments

  • MarkHamblinMarkHamblin Member Posts: 118
    Have you tried replicating the issue with a clean 2009 install that doesn't rely on the NAV 5 DB?

    Could be a network authentication issue, or could be due to the NAV 5 DB (maybe some state info isn't getting cleared properly due to missing/incompatible DB objects). You probably won't know until you try the same thing in with a 2009 DB.
  • kinekine Member Posts: 12,562
    It could be different things. It could be wrongly configured SPN (it means Kerberos not working correctly), or some incompatible code (I saw many modifications in CU1 preventing e.g. logging of one user to more sessions etc.), but in general, there is no problem to use WebServices even with older database than NAV 5.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
Sign In or Register to comment.