Issues on 2014 to 2016 upgrade.

  • Hi,

    I have a cluster with differents SQL version (2012-2014) and i need to update an instance to SQL 2016. But, during the "install_sqlncli_Cpu64_Action" i have the error message in my log files "

    Product: Microsoft SQL Server 2012 Native Client -- Installation failed.

    MSI (s) (BC:34) [13:37:00:372]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2012 Native Client. Product Version: 11.3.6518.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603." and i have a rollback and failed upgrade.

    Do you have any idea on this issue ?

    Rgds,
    FL.

  • fabien.lopes - Monday, April 3, 2017 8:26 AM

    Hi,

    I have a cluster with differents SQL version (2012-2014) and i need to update an instance to SQL 2016. But, during the "install_sqlncli_Cpu64_Action" i have the error message in my log files "

    Product: Microsoft SQL Server 2012 Native Client -- Installation failed.

    MSI (s) (BC:34) [13:37:00:372]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2012 Native Client. Product Version: 11.3.6518.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603." and i have a rollback and failed upgrade.

    Do you have any idea on this issue ?

    Rgds,
    FL.

    Have you checked the rest of the logs for other error messages, given that this one is not very detailed?

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • Hi,

    Thank for your response. I have checked the log in MSSQL\130\setup Bootstrap for the install logs and in the instance logs and I don't have more informations. Maybe I have forget to check a log ?

    For information in my precedent post i have sent the informations log from the sqlncli_Cpu64_1.log and in summary log i have this informations :

    Detailed results:
    Feature:        Client Tools Connectivity
    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 Native Client Access Component
    Component error code:    1603
    Component log file:    C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description:     Fatal error during installation.
    Error help link:     http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature:        Database Engine 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 Native Client Access Component
    Component error code:    1603
    Component log file:    C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description:     Fatal error during installation.
    Error help link:     http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature:        Integration 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 Native Client Access Component
    Component error code:    1603
    Component log file:    C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description:     Fatal error during installation.
    Error help link:     http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature:        SQL Client Connectivity
    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 Native Client Access Component
    Component error code:    1603
    Component log file:    C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description:     Fatal error during installation.
    Error help link:     http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature:        SQL Client Connectivity SDK
    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 Native Client Access Component
    Component error code:    1603
    Component log file:    C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description:     Fatal error during installation.
    Error help link:     http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Rgds,
    FL.

  • Phil Parkin - Monday, April 3, 2017 9:02 AM

    fabien.lopes - Monday, April 3, 2017 8:26 AM

    Hi,

    I have a cluster with differents SQL version (2012-2014) and i need to update an instance to SQL 2016. But, during the "install_sqlncli_Cpu64_Action" i have the error message in my log files "

    Product: Microsoft SQL Server 2012 Native Client -- Installation failed.

    MSI (s) (BC:34) [13:37:00:372]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2012 Native Client. Product Version: 11.3.6518.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603." and i have a rollback and failed upgrade.

    Do you have any idea on this issue ?

    Rgds,
    FL.

    Have you checked the rest of the logs for other error messages, given that this one is not very detailed?

    Hi,

    Thank for your response. I have checked the log in MSSQL\130\setup Bootstrap for the install logs and in the instance logs and I don't have more informations. Maybe I have forget to check a log ?

    For information in my precedent post i have sent the informations log from the sqlncli_Cpu64_1.log and in summary log i have this informations :

    Detailed results:
    Feature: Client Tools Connectivity
    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 Native Client Access Component
    Component error code: 1603
    Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description: Fatal error during installation.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature: Database Engine 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 Native Client Access Component
    Component error code: 1603
    Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description: Fatal error during installation.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature: Integration 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 Native Client Access Component
    Component error code: 1603
    Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description: Fatal error during installation.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature: SQL Client Connectivity
    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 Native Client Access Component
    Component error code: 1603
    Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description: Fatal error during installation.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Feature: SQL Client Connectivity SDK
    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 Native Client Access Component
    Component error code: 1603
    Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_145102\sqlncli_Cpu64_1.log
    Error description: Fatal error during installation.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%400x162A16FE%400x1603

    Rgds,
    FL. 

  • Could this be relevant?

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • Phil Parkin - Monday, April 3, 2017 10:02 AM

    Could this be relevant?

    I have thought about it, but I have about 20 SQL instances in 2012 on this cluster, and I wonder what impact I have to remove the 2012 native client tool on the access instance ?

  • fabien.lopes - Monday, April 3, 2017 10:07 AM

    Phil Parkin - Monday, April 3, 2017 10:02 AM

    Could this be relevant?

    I have thought about it, but I have about 20 SQL instances in 2012 on this cluster, and I wonder what impact I have to remove the 2012 native client tool on the access instance ?

    I do not know the answer to that, sorry. You are right to be careful.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • This was removed by the editor as SPAM

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

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