none
SQL 2016 Collation Change - Failure RRS feed

  • Question

  • Fellow SQLers,

    I am a SQL DBA

    We are flipping a collation. We have done this before and understand the use of the Setup /QUIET /ACTION=REBUILDDATABASE  command. Have used it before just fine.

    For some reason on a test clustered instance we are getting errors. I and my fellow dbas have treid as well. Tried from the install disc folder and also tried from Bootstrap setup. we are all admins. All attemps are failing with below errors.

    The active node has sql instance offline and we also tried enabling Named Pipes - no success.

    After the failure, the sa password is blank (which we supplied in the command). When we fix the security, the db DID get the new collation but of course we do not trust the instance.

    What are we missing?

    Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

    Thanks MG

    Wednesday, June 5, 2019 1:54 PM

Answers

  • Fellow SQLers,

    We found the problem. The cause was uncovered when one of our dbas tried to do a repair on the instance. If failed with a message about needing permissions. He uncovered that we needed "DEBUG PROGRAM" permission which was not enabled for us.   That was never shown on any of the output or logs from running the collation change when it failed. He altered security, reran our REBUILDDatabase script and it ran flawlessly in a very short time. All solved.

    MG


    • Marked as answer by mg101 Wednesday, June 5, 2019 6:06 PM
    • Edited by mg101 Thursday, June 6, 2019 2:13 PM wording
    Wednesday, June 5, 2019 6:06 PM

All replies

  • <<A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was <<<not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to <<<allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

    1. Make sure SQL Server Service is running
    2. If a named instance, make sure SQL Server browser service is running
    3. Make sure SQL Server is configured to allow remote connections
    4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
    5. Test server connectivity with PING from the client machine
    6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine.  For example
    a. TELNET <server-name> 1433
    b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
    7. Check firewall settings if step 5 or 6 connectivity test fails


    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Wednesday, June 5, 2019 2:53 PM
  • Uri,

    Thanks but this is a clustered instance. So you have to take the current node offline to run this rebuild.

    SQL Was all working fine before this with ALL of the above things configured correctly.

    MG

    Wednesday, June 5, 2019 3:30 PM
  • Fellow SQLers,

    We found the problem. The cause was uncovered when one of our dbas tried to do a repair on the instance. If failed with a message about needing permissions. He uncovered that we needed "DEBUG PROGRAM" permission which was not enabled for us.   That was never shown on any of the output or logs from running the collation change when it failed. He altered security, reran our REBUILDDatabase script and it ran flawlessly in a very short time. All solved.

    MG


    • Marked as answer by mg101 Wednesday, June 5, 2019 6:06 PM
    • Edited by mg101 Thursday, June 6, 2019 2:13 PM wording
    Wednesday, June 5, 2019 6:06 PM