none
SQL 2016 on premises

    Question

  • Pushing KB3210089 on OS2016&SQL2016 throws an error:

    Important Update for SQL Server 2016 SP1(KB3210089) - Error 0x80070643

    Any idea how to fix it?


    bostjanc

    Sunday, March 26, 2017 8:13 AM

Answers

  • Checked patch level with sql management studio, and they patch was not yet there...
    Tried with repair SQL and pushing update again - didn't help.

    The only thing that helped was completely uninstalling sql 2016 and installing it again.

    After that the update succeded.

    case closed.

    thanks for the reply


    bostjanc

    Sunday, March 26, 2017 5:26 PM

All replies

  • Please review installation log file for more details about the issue, it's located in folder

    C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\<TimeStamp>


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Sunday, March 26, 2017 8:50 AM
  • Thanks for the reply.

    looking at detail.txt, can not find anything useful.

    Uploaded to googl drive the log file:

    https://drive.google.com/open?id=0B_Cst0SCMGxWWm5iNUVqNFowMkU


    bostjanc

    Sunday, March 26, 2017 9:00 AM
  • This seems to be where things go wrong:

    (01) 2017-03-26 01:06:15 Slp: Sco: Attempting to open service handle for service ReportServer
    (01) 2017-03-26 01:06:15 Slp: Sco: Attempting to close SC Manager
    (01) 2017-03-26 01:06:15 Slp: Attempting to run patch request for instance: MSSQLSERVER
    (01) 2017-03-26 01:07:10 Slp: Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2061893565)
    (01) 2017-03-26 01:07:10 Slp: Sco: Attempting to open SC Manager
    (01) 2017-03-26 01:07:10 Slp: Sco: Attempting to open service handle for service SQLBrowser
    (01) 2017-03-26 01:07:10 Slp: Sco: Attempting to close service handle for service SQLBrowser
    (01) 2017-03-26 01:07:10 Slp: Sco: Attempting to close SC Manager

    But that opens the question what happened between 1:06:15 and 1:07:10. Could there be any more log file from this point in time? Something in the SQL Server error log.

    These logs are certainly not trivial to decipher, not the least because of the deluge of text in them. It may be better to open a case with Microsoft. Although check first that your instance is not already on the version the patch is for. I have had errors from Windows Update with this update, but the patch is nevertheless in place.

    Sunday, March 26, 2017 9:20 AM
  • Checked patch level with sql management studio, and they patch was not yet there...
    Tried with repair SQL and pushing update again - didn't help.

    The only thing that helped was completely uninstalling sql 2016 and installing it again.

    After that the update succeded.

    case closed.

    thanks for the reply


    bostjanc

    Sunday, March 26, 2017 5:26 PM