Post reply

Having trouble re-installing SQL 2005 on a cluster

  • August 24, 2010 at 10:43 am

    #144780

    I'm testing upgrading a SQL 2005 cluster to SQL 2008. After one successful upgrade, I've removed SQL and have reinstalled SQL 2005 to test everything out again.

    I'm running into two issues. Not sure yet if they are related, and one is being addressed.

    1. We change our TCP/IP ports from the default 1433 to a different value. I've set these in SQL Server Configuration Manager (CM), and they appear to be saved - I can close CM, re-open it, and the ports that I've assigned (both under "SQL Server 2005 Network Configuration | Protocols for MSSQLSERVER | TCP/IP and under "SQL Native Client configuration | Client Protocols | TCP/IP) are changed to this non-default port. However, after attempting to start SQL Server and it fails, I find that these are all set back to 1433. Any ideas?

    2. In checking out why SQL Server won't start up, I see in the ErrorLog these two messages:

    The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

    The SQL then shuts down, and this message is entered:

    The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098. Administrator should deregister this SPN manually to avoid client authentication errors.

    In researching this, I have found this link: This includes this note:

    Note If an SPN already exists, you must delete the SPN before you can reregister it. You may have to do this if the account mapping has changed. To deleted an existing SPN, you can use the SetSPN.exe tool together with the -D switch.

    Since I had a previous installation of SQL on this server, I'm suspecting that the SPN needs to be deleted. One of the SAs is looking into this, and we'll find out soon enough if this fixes this issue.

    Does this sound like it would prevent SQL from starting up?

    3. Would the failure of the SQL to start cause it to change the TCP/IP ports in CM back to 1433?

    Thanks!

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • August 25, 2010 at 5:17 am

    #1211538

    SQL Server service account is unable to add/remove SPN from the AD. Most likely it does not have the privileges.

    However, I don't expect this to prevent SQL Server from starting up.

    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @pradeepadiga

  • August 25, 2010 at 9:25 am

    #1211723

    Well, I've got a little bit of followup on this. The instance still won't start.

    In looking through the application Event Log, and in cluster.log, I see these messages:

    Recovery is complete. This is an informational message only. No user action is required.

    [sqsrvres] ODBC sqldriverconnect failed

    [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

    (repeat above two messages 11 times)

    [sqsrvres] ODBC sqldriverconnect failed

    (repeat above 3 messages as a group 10 times)

    [sqsrvres] OnlineThread: did not connect after 10 attempts resource failed

    Service Broker manager has shut down.

    I haven't been able to find out anything on this yet.

    In the SQL Errorlog:

    Recovery is complete. This is an informational message only. No user action is required.

    Service Broker manager has shut down.

    . This happens after the above ODBC message has been attempted a few times, and about 25 seconds after the Recovery message.

    What I can't figure out is why it can't use the ODBC connection.

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • August 25, 2010 at 1:13 pm

    #1211862

    Did the server name change after cluster installation?

    Please check this these links help

    http://support.microsoft.com/kb/307336

    http://support.microsoft.com/default.aspx?kbid=328306

    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @pradeepadiga

  • August 25, 2010 at 1:57 pm

    #1211897

    Adiga (8/25/2010)

    Did the server name change after cluster installation?

    Please check this these links help

    http://support.microsoft.com/kb/307336

    http://support.microsoft.com/default.aspx?kbid=328306%5B/quote%5D

    Have not attempted to change the server name.

    2nd link: does not appear to apply (can't even start the sql server. This is about connectivity to a running sql server.)

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • August 26, 2010 at 3:13 am

    #1212151

    When you have upgraded from 2005 to 2008, have u register the SPN's manually?

  • August 26, 2010 at 5:18 am

    #1212216

    chetanr.jain (8/26/2010)

    When you have upgraded from 2005 to 2008, have u register the SPN's manually?

    No, didn't have to do anything to make 2008 work properly when upgraded.

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • August 26, 2010 at 8:41 am

    #1212355

    Resolution: see this link

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply