Share via

Error During In-Place Upgrade from SQL Server 2016 to SQL Server 2019

DBAMonkee 96 Reputation points
2021-04-26T19:55:28.257+00:00

I am attempting an In-Place upgrade from SQL Server 2016 (13.0.5201.2) to SQL Server 2019 RTM. I have uninstalled Microsoft SQL Server 2012 Native Client & Microsoft SQL Server 2014 Native Client. I also uninstalled SSMS 17.9 and no other SSMS is installed. I turned on the Windows Installer service, copied the SQL Server 2019 installation files to C root drive and restarted the server. When I run the installer the first error encountered is "Exception has been thrown by the target of an invocation.". If I click the OK button it resumes and encounters a 2nd error "The document specified by its root path '/Extension/Agent/AgentPreviousRegPath' does not exist in data store.". If I click OK button I encounter a 3rd error listed below.

Install_sql_engine_core_inst_Cpu64_Action : Sqlmsirc_NotifyFeatureStates_64

There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.

Next the Complete with failures window is displayed (See Below).
Database Engine Services -- FAILED
SQL Browser -- Succeeded
SQL Writer -- Succeeded
Integration Services -- Succeeded
SQL Client Connectivity SDK -- Succeeded
SQL Client Connectivity -- Succeeded
Setup Support Files -- Succeeded

My summary file -- Exit code (Decimal): -2146232828

Feature: Database Engine Services
Status: Failed
Component name: SQL Server Database Engine Services Instance Features
Component error code: 25012
Error description: There was an error attempting to remove the configuration of the product which prevents any other action
from occuring. The current configuration of the product is being cancelled as a result.

Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80131604
Error description: Exception has been thrown by the target of an invocation

Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B20001
Error description: The document specified by its root path '/Extension/Agent/AgentPreviousRegPath' does not exist in data
store.

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments No comments

Answer accepted by question author

DBAMonkee 96 Reputation points
2021-04-27T19:35:58.673+00:00

I found the issue. I am currently performing the in-place upgrade on a cloned VM but it's not attached to our domain. I had to change the SQL Server service account since we use a domain account to use a local service account. I had stopped the SQL Agent service and pretty much forgot about it. However, it to used a domain account and I had to change it also to use a local service account and also started the SQL Agent service and this resolved the issues. Thanks for taking the time to help me previously!!

Was this answer helpful?


3 additional answers

Sort by: Most helpful
  1. DBAMonkee 96 Reputation points
    2021-04-28T11:11:13.77+00:00

    Thanks for taking the time to help with this issue!!

    Was this answer helpful?

    0 comments No comments

  2. DBAMonkee 96 Reputation points
    2021-04-27T13:00:44.293+00:00

    I checked HKEY_LOCAL_MaCHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL13.MSSQLSERVER\ConfigurationState and found the following to be true before the IN-Place upgrade.

    MPT_AGENT_CORE_CNI = 1
    SQL_Engine_Core_Inst = 1

    After the IN-Place upgrade fails the following values are reflected.

    MPT_AGENT_CORE_CNI = 1
    SQL_Engine_Core_Inst = 3

    I did turn the Windows Installer service on before the In-Place upgrade but did notice that the service was not running after the In-Place upgrade fails.

    Was this answer helpful?

    0 comments No comments

  3. CarrinWu-MSFT 6,891 Reputation points
    2021-04-27T02:49:17.667+00:00

    Hi @DBAMonkee ,

    Welcome to Microsoft Q&A!

    Please follow below steps to check your environment:

    1. Please make sure Windows Installer service is running.
    2. Open the registry and verify the value at HKEY_LOCAL_MaCHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL13.MSSQLSERVER\ConfigurationState, the values for all the keys under this should be 1. If it is not 1, then there is some issue in configuring the corresponding feature.

    If below steps not work, is it possible to uninstall SQL server and then reinstall it for your situation? Please feel free to let me know it work or not.

    Best regards,
    Carrin


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.