Connection to database causes SSPI context error












1















I have migrated a SQL server from another server box that was decommissioned. They have the same name and also same IP address. However, when I connect to the server from an application using trusted connection, I get the "SSPI context not generated" error.



What I have done:




  • I have used the setspn -X to confirm there is no duplicate SPN.



  • I have changed the order of protocol to follow the order:



    Shared Memory,

    Named Pipes,

    TCP/IP.



  • I have verified that when I restart SQL server, the service registers and deregisters. This was found in the SQL server log.


  • I have checked that on the SQL configuration the TCP/IP network protocol has the right IP and is active and enabled on both 32bit and 64bit.



I am running out of ideas and I am still getting the same error. I can't find any log that point to Kerberos.










share|improve this question
















bumped to the homepage by Community 3 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Is the sysserver name changed .. sp_addservername ?

    – Kin
    Mar 21 '16 at 23:21











  • Was the name correct before you installed SQL or did you change it after?

    – Mister Magoo
    Mar 21 '16 at 23:32











  • Yes the server was changed after and the sysserver was changed as well.

    – damola
    Mar 22 '16 at 17:01
















1















I have migrated a SQL server from another server box that was decommissioned. They have the same name and also same IP address. However, when I connect to the server from an application using trusted connection, I get the "SSPI context not generated" error.



What I have done:




  • I have used the setspn -X to confirm there is no duplicate SPN.



  • I have changed the order of protocol to follow the order:



    Shared Memory,

    Named Pipes,

    TCP/IP.



  • I have verified that when I restart SQL server, the service registers and deregisters. This was found in the SQL server log.


  • I have checked that on the SQL configuration the TCP/IP network protocol has the right IP and is active and enabled on both 32bit and 64bit.



I am running out of ideas and I am still getting the same error. I can't find any log that point to Kerberos.










share|improve this question
















bumped to the homepage by Community 3 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Is the sysserver name changed .. sp_addservername ?

    – Kin
    Mar 21 '16 at 23:21











  • Was the name correct before you installed SQL or did you change it after?

    – Mister Magoo
    Mar 21 '16 at 23:32











  • Yes the server was changed after and the sysserver was changed as well.

    – damola
    Mar 22 '16 at 17:01














1












1








1








I have migrated a SQL server from another server box that was decommissioned. They have the same name and also same IP address. However, when I connect to the server from an application using trusted connection, I get the "SSPI context not generated" error.



What I have done:




  • I have used the setspn -X to confirm there is no duplicate SPN.



  • I have changed the order of protocol to follow the order:



    Shared Memory,

    Named Pipes,

    TCP/IP.



  • I have verified that when I restart SQL server, the service registers and deregisters. This was found in the SQL server log.


  • I have checked that on the SQL configuration the TCP/IP network protocol has the right IP and is active and enabled on both 32bit and 64bit.



I am running out of ideas and I am still getting the same error. I can't find any log that point to Kerberos.










share|improve this question
















I have migrated a SQL server from another server box that was decommissioned. They have the same name and also same IP address. However, when I connect to the server from an application using trusted connection, I get the "SSPI context not generated" error.



What I have done:




  • I have used the setspn -X to confirm there is no duplicate SPN.



  • I have changed the order of protocol to follow the order:



    Shared Memory,

    Named Pipes,

    TCP/IP.



  • I have verified that when I restart SQL server, the service registers and deregisters. This was found in the SQL server log.


  • I have checked that on the SQL configuration the TCP/IP network protocol has the right IP and is active and enabled on both 32bit and 64bit.



I am running out of ideas and I am still getting the same error. I can't find any log that point to Kerberos.







sql-server sql-server-2008-r2 spn






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 22 '16 at 7:08









Andriy M

16k63372




16k63372










asked Mar 21 '16 at 23:12









damoladamola

62




62





bumped to the homepage by Community 3 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 3 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Is the sysserver name changed .. sp_addservername ?

    – Kin
    Mar 21 '16 at 23:21











  • Was the name correct before you installed SQL or did you change it after?

    – Mister Magoo
    Mar 21 '16 at 23:32











  • Yes the server was changed after and the sysserver was changed as well.

    – damola
    Mar 22 '16 at 17:01



















  • Is the sysserver name changed .. sp_addservername ?

    – Kin
    Mar 21 '16 at 23:21











  • Was the name correct before you installed SQL or did you change it after?

    – Mister Magoo
    Mar 21 '16 at 23:32











  • Yes the server was changed after and the sysserver was changed as well.

    – damola
    Mar 22 '16 at 17:01

















Is the sysserver name changed .. sp_addservername ?

– Kin
Mar 21 '16 at 23:21





Is the sysserver name changed .. sp_addservername ?

– Kin
Mar 21 '16 at 23:21













Was the name correct before you installed SQL or did you change it after?

– Mister Magoo
Mar 21 '16 at 23:32





Was the name correct before you installed SQL or did you change it after?

– Mister Magoo
Mar 21 '16 at 23:32













Yes the server was changed after and the sysserver was changed as well.

– damola
Mar 22 '16 at 17:01





Yes the server was changed after and the sysserver was changed as well.

– damola
Mar 22 '16 at 17:01










1 Answer
1






active

oldest

votes


















0














Try using Microsoft Kerberos Configuration Manager for SQL Server to automatically detect and fix such SPN Issues:



https://blogs.msdn.microsoft.com/farukcelik/2013/05/21/new-tool-microsoft-kerberos-configuration-manager-for-sql-server-is-ready-to-resolve-your-kerberosconnectivity-issues/






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f132926%2fconnection-to-database-causes-sspi-context-error%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Try using Microsoft Kerberos Configuration Manager for SQL Server to automatically detect and fix such SPN Issues:



    https://blogs.msdn.microsoft.com/farukcelik/2013/05/21/new-tool-microsoft-kerberos-configuration-manager-for-sql-server-is-ready-to-resolve-your-kerberosconnectivity-issues/






    share|improve this answer




























      0














      Try using Microsoft Kerberos Configuration Manager for SQL Server to automatically detect and fix such SPN Issues:



      https://blogs.msdn.microsoft.com/farukcelik/2013/05/21/new-tool-microsoft-kerberos-configuration-manager-for-sql-server-is-ready-to-resolve-your-kerberosconnectivity-issues/






      share|improve this answer


























        0












        0








        0







        Try using Microsoft Kerberos Configuration Manager for SQL Server to automatically detect and fix such SPN Issues:



        https://blogs.msdn.microsoft.com/farukcelik/2013/05/21/new-tool-microsoft-kerberos-configuration-manager-for-sql-server-is-ready-to-resolve-your-kerberosconnectivity-issues/






        share|improve this answer













        Try using Microsoft Kerberos Configuration Manager for SQL Server to automatically detect and fix such SPN Issues:



        https://blogs.msdn.microsoft.com/farukcelik/2013/05/21/new-tool-microsoft-kerberos-configuration-manager-for-sql-server-is-ready-to-resolve-your-kerberosconnectivity-issues/







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 6 '17 at 7:38









        Masood HashimMasood Hashim

        1807




        1807






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f132926%2fconnection-to-database-causes-sspi-context-error%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            SQL Server 17 - Attemping to backup to remote NAS but Access is denied

            Always On Availability groups resolving state after failover - Remote harden of transaction...

            Restoring from pg_dump with foreign key constraints