I am following the Walkthrough: Installing the Three Tiers on Three Computers topic from the nav_install.chm that is on the DVD.
I have the DB, Nav Server and Nav Client machines setup running Win2k8, Win2k8 and Vista.
I have configured a Domain Account for the Nav Server service to run under and ran the command to Create a Service Principal Name. I have edited the ClientUserSettings.config and added the key as directed (<add key="DelegationInfo" value="DomainUser"></add>).
I then come to the section of the help file headed "Delegating Access to the SQL Server Service", at step 10 it says "In the list of services, click MSSQLSvc, the SQL Server service." - the problem I have is that MSSQLSvc is not listed.
It doesn't help that the online version of the walkthrough (
http://msdn.microsoft.com/en-us/library/dd301254.aspx) is slightly different.
Can anyone offer any advice as to where I may have gone wrong please?
Comments
Also if not work - check your spn's.
Open up the user you created to run the service in Users and Computers
Select the Delegation tab
Set it to “Trust this user for delegation to specified services only"
And set it to “use Kerberos only”
Then press “Add”
Find the user you created to run the service (and created the SPN for)
You should see the MSSQLSvc for the user there to add.
If you don't then you may not have created the right SPN for the user. You can use ADSIEdit.msc to see what service principle names are for the user.
Here are examples of the SPN I created:
MSSQLSvc/domain.servername
MSSQLSvc/domain.servername:1433
Good luck!
One thing I should have added to the original post is that I am trying to use SQL Server 2008.
Will update when I have had chance to test this further.
I am just stuck at the same point.
I have set up a Domain User called NavServer and used the following command to create the SPN (test domain is called marvel)
I can see the SPN in ADSI Edit.
Yet when I get to step 10 in the "To delegate access to the SQL Server Service" of the walkthrough (when I have right-clicked DYNNAV-SERVER and on the Delegation tab have clicked "Trust this computer for delgation to specified services only" and "Use Kerberos only" and clicked [Add] and added DYNNAV-SQL-SERVER) I see the list of "Available services:" shown here.
MSSQLSvc is not there! ](*,)
Earlier you said you were following the walkthrough, so I will assume this is the case. When you specify 'Trust this user for delegation to the specified services only' in AD, in the dialog when you press Add, you need to specify the SQL Server service account.
Let's assume your NAV service is running as a domain user called marvel\NAVServer and SQL Server services run as a domain user called marvel\SqlServer.
You should create SPNs for SqlServer as follows:
setspn -a MSSQLSvc/SQL-SERVER.marvel.company.com marvel\SqlServer
setspn -a MSSQLSvc/SQL-SERVER.marvel.company.com:1433 marvel\SqlServer
where SQL-SERVER is the name of the computer where SQL Server is running.
The SPN you gave for NAV looks good, assuming you are using NAV 2009 RTM (not hotfixed, not SP1 CTP), NAVServer is a domain user account, and DYNNAV-SERVER is the name of the computer running the NAV service.
Now, you should be able to go into the AD snap in and find the user NavServer. Go to properties, then delegation. Press Add, then Users or Computers... and enter SqlServer. You should then see a list of services with SPNs that run under the account SqlServer - this should include MSSQLSvc.
Alex
The SQL Database Engine User is called SQLDBE. I have set the SPNs up as per the suggestion.
I have checked on the DYNNAV-CLIENT for the ClientUserSettings.config files.
There are two;
\\dynnav-client\c$\ProgramData\Microsoft\Microsoft Dynamics NAV
\\dynnav-client\c$\Users\administrator\AppData\Local\Microsoft\Microsoft Dynamics NAV
Both contain this;
\\dynnav-server\c$\Program Files (x86)\Microsoft Dynamics NAV\60\Service
The Log On tab shows "o This account NAVServer@marvel.company.com" and not the usual format of "MARVEL\NAVServer"
The file \\dynnav-server\c$\Program Files (x86)\Microsoft Dynamics NAV\60\Service\CustomSettings.config contains this:
I think NAV will connect to SQL Server using TCP/IP if you set NetType = Default in the service config. Therefore, check whether TCP/IP is enabled on SQL Server using the SQL config management tool - I often forget this. Also, you will need to open the port (1433 by default) on the firewall.
Since you created the SPN for NAV using a fully qualified name, I think you need to also specify a fully qualified name in the clientUserSettings.config file, e.g. <add key="Server" value="DYNNAV-SERVER.marvel.company.com"></add>.
Also, after you make changes to SPNs you should restart the affected services.
Alex
I changed the clientUserSettings.config file (both of them on the Client tier machine) to contain <add key="Server" value="DYNNAV-SERVER.marvel.company.com"></add>.
The 3 machines can all resolve each other's name and ping each other.
Now when I run the RTC on the Client tier PC, I get this after a minute or so pause:
If I click [Yes] to try again, the same message is displayed after a minute or so.
If I click [No], I am shown this:
If I click [Connect], after a minute or so pause, I am shown this:
So, slightly different, but back to where I was last week ](*,)
It wasn't on my server, so I enabled it and still get the same problem ](*,)
I have set up a 4th VM called Nav2009AllTier and installed SQL and Nav Server and both of the clients on to it using Install Demo option from the installation DVD.
So I now have 4 machines
What I can do with the Classic Client
On DYNNAV-Client I can open CRONUS on DYNNAV-SQL and on Nav2009AllTier using server name DYNNAV-SQL and Nav2009AllTier respectively.
On NAV2009AllTier I can open CRONUS on DYNNAV-SQL using Server name DYNNAV-SQL and I can open CRONUS on Nav2009AllTier using Server name Nav2009AllTier or localhost.
What I can do with the RTC
On Nav2009AllTier I can open CRONUS on Nav2009AllTier using Server name Nav2009AllTier/DynamicsNAV
On DYNNAV-Client I can open CRONUS on Nav2009AllTier using Server name Nav2009AllTier/DynamicsNAV
What I cannot do with the RTC
I cannot, on DYNNAV-Client or Nav2009AllTier, open Cronus using Server name DYNNAV-Server/DynamicsNAV
](*,)
I cannot see anything that looks related in the Event Logs on DYNNAV-SQL or DYNNAV-Server and there is nothing NAV related in the SQL Server's log apart from an entry stating that spidxx is using xp_ndo_x64.dll to execute one of the ESPs (I am guessing this is when I connected with the Classic client).
The client should be able to connect with either netbios or fully qualified names, even if authentication later fails once the connection has been established.
Further down in the stack trace we can see a SecurityNegotiationException, then an AuthenticationException, then eventually a Win32Exception with the message 'The target principal name is incorrect'. This suggests to me that although it looks like you simply can't connect to the server, actually you are having a problem negotiating an authentication scheme.
Before you try anything else, please confirm that you are using NAV 2009 without any hotfixes applied, and that you are not using the SP1 CTP2 release.
Since your other settings look good I wonder if you have accidentally created duplicate SPNs. I would recommend skimming through this guide to troubleshooting Kerberos errors: http://technet.microsoft.com/en-us/library/cc728430(WS.10).aspx.
In particular, try:
Alex
I am having EXACTLY the same issue as you. On VMware....
Let me know if you come across anything, and if I make a tweak and get it to work I'll do the same.
-Edit.....
Forgot to say, I changed my Client config file to point to the IP Address instead of FQDN and get the error
Microsoft Dynamics NAV
The login failed when connecting to SQL Server SRVVANSQL1.
OK
t
http://blogs.msdn.com/nav_developer/arc ... -2009.aspx
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I have not had chance to progress my test for a while. Real work getting in the way!
I will update as soon as I can.