webservice server respond with error 410

danlindstrom

We have installed NAV 2009 R2 in a three-tier environment with delegation and the RTC are running fine
sut the WebService responds with an error HTTP410

RTC connects to "dynamicsnav://<appservername>:7046/DynamicsNAV/<company>AB" without any errors!

The call from a browser to "http://<appservername>:7047/DynamicsNAV/WS/Services&quot;
and/or "http://<appservername.domain>:7047/DynamicsNAV/WS/Services&quot;
returns with a login-form and then error-page HTTP410

the setuppath from http://msdn.microsoft.com/en-us/library/ee414212.aspx has been checked and confirmed.

How do I debug the installation?
no errors in either IIS-logg or eventlog
:?

almarka

Try to add the following SPNs to the domain user account running the Microsoft Dynamics NAV Business Services service:

HTTP/FullyQualifiedDomainNameOfNavWebServiceServer
HTTP/NameOfNavWebServiceServer

It should help.

danlindstrom

almarka wrote:

Try to add the following SPNs to the domain user account running the Microsoft Dynamics NAV Business Services service:

HTTP/FullyQualifiedDomainNameOfNavWebServiceServer
HTTP/NameOfNavWebServiceServer

It should help.

Has done it with

setspn -A HTTP/FullyQualifiedDomainNameOfNavWebServiceServer:7047 domain\domainuser
setspn -A HTTP/NameOfNavWebServiceServer:7047 domain\domainuser

domain\domainuser = userID running the service

as stated in the linked document 'How to: Configure Web Services with Delegation'
with no success

I have also done:

httpcfg delete urlacl –u http://+:7047/DynamicsNAV/
httpcfg set urlacl -u http://+:7047/DynamicsNAV/ -a D:^(A;^;GX^;^;^;<SID of domain\domainuser>)

both with exitcode = 0

but still no success

(all this has been done before creating this thread)

ara3n

Open Adsiedit on domain controller and make sure you don't have duplicate SPN.

Open IE on the service tier and try open the WSDL address.

Also try and change the computer name with localhost.

danlindstrom

ara3n wrote:

Open Adsiedit on domain controller and make sure you don't have duplicate SPN.

Open IE on the service tier and try open the WSDL address.

Also try and change the computer name with localhost.

adsiedit gave no duplicates on either NameOfNavWebServiceServer or domain\domainuser

I have enabled the firewall, added Microsoft.Dynamics.Nav.Server and then disabled the firewall

Now the WebServiceServer respons on ipnumber but not on name :?
http://127.0.0.1:7047/DynamicsNAV/WS/Services works, but not http://localhost:7047/DynamicsNAV/WS/Services
same for the exposed localnetworkipnumber
http://172.18.2.18:7047/DynamicsNAV/WS/Services works, but not http://NameOfNavWebServiceServer:7047/D ... S/Services or
http://FullyQualifiedDomainNameOfNavWeb ... S/Services

The local DNS has a pointer/record with the mapping of 172.18.2.18 = NameOfNavWebServiceServer

ara3n

well for right now use the IP address and get the best practices application and install it on the service tier and run it. It will tell you what is not setup correctly.

Can you put a screenshot of the SPN from Adsiedit here?

It's hard to solve the delegation on forums, it's already frustrating as it is when you are doing it for the first time.

danlindstrom

see attached image
CN=NAV CRM Service == domain\domainuser
CN=UPDAFFSYS == NameOfNavWebServiceServer

ara3n

You have port 7048 on http instead of 7047

jonashedberg

We are running 2 separate service tiers on the same server.

ara3n

yes and you are using the same port for RTC. NAV can be run with port sharing but I don't remember what you had to differently.

I suggest to remove and create separate ports.

jonashedberg

It's separated:

1st RTC service on port 7046
1st WS service on port 7047
2nd RTC service on port 7048
2ns WS service in not setup yet, but will be running on port 7049

It's the 1st server that we are dealing with at the moment.

I see we have made an error regarding port number on 2nd server. But that will be corrected.

ara3n

Install the best practices and see what the issue is. Also run/install krebtray and flush the kerboese tickets on the service tier.

jonashedberg

Best practices shows no warning or error.
Already purged the keberos tickets on all involved machines.

As you can see, we have almopst tried everything "in the book".

ara3n

Time to call ms tech support