In order to fix the SPN problem I manually registered the SPN in Active Directory (on the SQL Computeraccount). It turns out that Microsoft Dynamics NAV for example is falling back to Ntlm, intereseting… So let’s fix the SPN, restart SQL Server and look what’s happening? Now Microsoft Dynamics NAV 2017 is also connected to SQL Server but instead of Ntlm it is using Kerberos now. Select session_id,net_transport,client_net_address,auth_scheme from sys.dm_exec_connections With this query you’re able to view what kind of authentication scheme is being used: In order to get an answer you could query SQL Server. In theory I can’t connect to my SQL Server using Kerberos authentication so why I’m still able to connect to my SQL Server? What kind of authentication is being used? Even other services from other machines are still able to connect (like Microsoft Dynamics NAV). – SPN’s must be registered for SQL Server – The client and server computers should be in the same domain or trusted (2 way) domains. In order to use Kerberos authentication with SQL Server there are some conditions to be met: For more information please go to Microsoft Docs. I’m running SQL Server under a ‘Virtual’ account so that should be the cause of the ‘error’.įrom security perspective it is recommend to run SQL Server under the least privileged account: a virtual of MSA.
It cleary indicates thats SQL Server couldn’t register SPN’s. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Quite some interesting information in my opinion, however I also found this message: Recently I checked my SQL Server Error Logs. So blogging about this will also help to document this issue and the quick solution ofcourse! I thought it was worth sharing this ‘tip’ in order to save valuable time for you and myself ofcourse in the main future if you encounter this issue (again). Final: Windows8.1-KB2919355-圆4 Download from (this one is quite an extensive download and takes about 10 minutes to install completely).
In order to fix this just install these updates and SQL 2016 Developer Edition will install without problems. If you have installed KB2919355, please make sure you have restarted your machine. A while ago I was setting up a new Nav envrionment and got this error during the installation of SQL Server 2016 (Developer Edition) installation on Windows 2012 R2: KB2919355 Installation failed (Validation Failed) Rule “KB2919355 Installation” failed.
0 kommentar(er)
