locked
SQLServer 2016 update pushing by mistake (KB3164398) RRS feed

  • Question

  • Hi.

    We have a WSUS server on our local domain and SQLServer updates are approved by default rule.

    I have a client with Windows 10 Enterprise. After a SQLServer 2016 Express (With sp1) installed on this computer, WSUS push KB3164398 to this computer but it never installed succeeded.

    I tried to download this patch and install manually, saying there is nothing to update...

    Any idea other than discard this update from WSUS?

    Thanks.

    _____

    Correction: this update is also pushed by Microsoft Update directly.

    • Edited by EternalSnow Friday, January 6, 2017 3:08 AM
    Thursday, January 5, 2017 1:18 AM

Answers

  • I was getting error:"Critical Update for SQL Server 2016 MSVCRT Prerequisites KB3164398"

    then installed the fix located here:http://download.microsoft.com/download/C/C/2/CC2DF5F8-4454-44B4-802D-5EA68D086676/vcredist_x64.exe


    Jaime E. Maccou

    • Marked as answer by EternalSnow Tuesday, January 10, 2017 8:26 AM
    Tuesday, January 10, 2017 7:20 AM

All replies

  • Hi EternalSnow,

    1. WSUS won't "push" updates for clients, if clients download update from WSUS server, then, it means the clients need the update.

    2. What error message do you get when fails to install the update?

    3. And what message do you get when you manually install the update?

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, January 5, 2017 8:05 AM
  • are you able to check, using the following guidance, if you do have the relevant/equivalent critical update?

    (KB3164398 or KB3138367)

    https://blogs.msdn.microsoft.com/sqlcat/2016/07/28/installing-sql-server-2016-rtm-you-must-do-this/

    https://msdn.microsoft.com/en-us/library/dn876712.aspx

    https://support.microsoft.com/en-us/kb/3164398


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Thursday, January 5, 2017 8:13 AM
  • Hi EternalSnow,

    1. WSUS won't "push" updates for clients, if clients download update from WSUS server, then, it means the clients need the update.

    2. What error message do you get when fails to install the update?

    3. And what message do you get when you manually install the update?

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Hi Anne,

    thanks for your reply.

    1 I know, lol. I said that because when I check update from Microsoft directly instead of WSUS, this update will NOT included. But it will appear again while checking with WSUS.

    2 Installing from WSUS/Windows Update:

    Critical Update for SQL Server 2016 MSVCRT Prerequisites KB3164398 - Error 0x80070643

    From System Event:

    Installation Started: Windows has started installing the following update: Critical Update for SQL Server 2016 MSVCRT Prerequisites KB3164398

    Installation Failure: Windows failed to install the following update with error 0x80070643: Critical Update for SQL Server 2016 MSVCRT Prerequisites KB3164398.

    From Application Event:

    wuaueng.dll (5920) SUS20ClientDataStore: The database format feature version 8980 (0x2314) could not be used due to the current database format 1568.20.0, controlled by the parameter 1073741825 (0x40000001).

    Fault bucket , type 0
    Event Name: WindowsUpdateFailure3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 10.0.14986.1000
    P2: 80070643
    P3: AF443B5C-7EA4-4C14-895C-4839F0352CDB
    P4: Install
    P5: 201
    P6: 0
    P7: 86430003
    P8: UpdateOrchestrator
    P9: {7971F918-A847-4430-9279-4A52D1EFE18D}
    P10: 0

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: ebd38bea-c352-4894-9438-20f340a4d306
    Report Status: 268435456
    Hashed bucket: f25b32014dfc454f223d5c37f8095687

    3 Install manually:

    There are no SQL Server instances or shared features that can be updated on this computer.

    Thursday, January 5, 2017 9:08 AM
  • are you able to check, using the following guidance, if you do have the relevant/equivalent critical update?

    (KB3164398 or KB3138367)

    https://blogs.msdn.microsoft.com/sqlcat/2016/07/28/installing-sql-server-2016-rtm-you-must-do-this/

    https://msdn.microsoft.com/en-us/library/dn876712.aspx

    https://support.microsoft.com/en-us/kb/3164398


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Hello, thanks for your idea.

    the result of select @@VERSION is:

    Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)   Oct 28 2016 18:17:30   Copyright (c) Microsoft Corporation  Express Edition (64-bit) on Windows 10 Enterprise Insider Preview 6.3 <X64> (Build 14986: ) 

    Thursday, January 5, 2017 9:09 AM
  • the result of select @@VERSION is:

    Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)   Oct 28 2016 18:17:30   Copyright (c) Microsoft Corporation  Express Edition (64-bit) on Windows 10 Enterprise Insider Preview 6.3 <X64> (Build 14986: ) 

    ok, so you've got SQL2016SP1, but what about the VC12runtime (VC which is the actual issue of the KB article, not a SQL patch at all really)

    https://support.microsoft.com/en-au/kb/3164398

    More information
    We recommend that you check the build version of the Microsoft VC Runtime DLLs that are installed on servers that have, or will have, SQL Server 2016 installed.
    You should install KB3138367 if the build version of %SystemRoot%\system32\msvcr120.dll is not 12.0.40649.5 or later.
    To check the file version, open Windows Explorer, locate and then right-click the %SystemRoot%\system32\msvcr120.dll file, click Properties, and then click the Details tab.

    If your VC12runtime file version is 12.0.40649.5 or later, your installation is not at risk of the described issue.

    Note that if you decline the update in WSUS, that will mean none of the WSUS clients on your WSUS will ever detect for that update.

    It does seem like a detection/applicability logic defect in the catalog metadata...

    maybe check/ask in the SQL forums (since it's the SQL team not the WSUS team, who will determine the correction if needed)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Thursday, January 5, 2017 9:51 PM
  • the result of select @@VERSION is:

    Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)   Oct 28 2016 18:17:30   Copyright (c) Microsoft Corporation  Express Edition (64-bit) on Windows 10 Enterprise Insider Preview 6.3 <X64> (Build 14986: ) 

    ok, so you've got SQL2016SP1, but what about the VC12runtime (VC which is the actual issue of the KB article, not a SQL patch at all really)

    https://support.microsoft.com/en-au/kb/3164398

    More information
    We recommend that you check the build version of the Microsoft VC Runtime DLLs that are installed on servers that have, or will have, SQL Server 2016 installed.
    You should install KB3138367 if the build version of %SystemRoot%\system32\msvcr120.dll is not 12.0.40649.5 or later.
    To check the file version, open Windows Explorer, locate and then right-click the %SystemRoot%\system32\msvcr120.dll file, click Properties, and then click the Details tab.

    If your VC12runtime file version is 12.0.40649.5 or later, your installation is not at risk of the described issue.

    Note that if you decline the update in WSUS, that will mean none of the WSUS clients on your WSUS will ever detect for that update.

    It does seem like a detection/applicability logic defect in the catalog metadata...

    maybe check/ask in the SQL forums (since it's the SQL team not the WSUS team, who will determine the correction if needed)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    1 Currently, the version of msvcp120.dll is 12.0.21005.1. And, there is a file named msvcp120_clr0400.dll, which version is 12.0.52512.0.

    2 That's why I post here. I guess there might be something wrong in the patch detection logic related to WSUS, or the client while working with WSUS. But I will post the link to that forum also. Thanks for your advice.

    Friday, January 6, 2017 1:27 AM
  • 1 Currently, the version of msvcp120.dll is 12.0.21005.1. And, there is a file named msvcp120_clr0400.dll, which version is 12.0.52512.0.

    2 That's why I post here. I guess there might be something wrong in the patch detection logic related to WSUS, or the client while working with WSUS. But I will post the link to that forum also. Thanks for your advice.

    No, not msvcp120.dll, you must check msvcr120.dll  ;)

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, January 6, 2017 3:10 AM
  • lol, my fault.

    msvcr120.dll: 12.0.21005.1

    msvcr120d.dll: 12.0.21005.1

    msvcr120_clr0400.dll: 12.0.52512.0

    Friday, January 6, 2017 3:16 AM
  • Hi EternalSnow,

    Just to confirm if you have solved the issue? If yes, you may mark useful reply as answer, if you need additional assistence, welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 9, 2017 9:46 AM
  • it's still there but I choose to let it be.

    Monday, January 9, 2017 10:14 AM
  • lol, my fault.

    msvcr120.dll: 12.0.21005.1

    msvcr120d.dll: 12.0.21005.1

    msvcr120_clr0400.dll: 12.0.52512.0


    ok, so I'm no software developer, but your v12.0.21005.1 seems to be a lower/older version than the required v12.0.40649.5 or later....

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Monday, January 9, 2017 8:33 PM
  • Yup.

    I have the old files but cannot upgrade them.

    Tuesday, January 10, 2017 12:25 AM
  • I was getting error:"Critical Update for SQL Server 2016 MSVCRT Prerequisites KB3164398"

    then installed the fix located here:http://download.microsoft.com/download/C/C/2/CC2DF5F8-4454-44B4-802D-5EA68D086676/vcredist_x64.exe


    Jaime E. Maccou

    • Marked as answer by EternalSnow Tuesday, January 10, 2017 8:26 AM
    Tuesday, January 10, 2017 7:20 AM
  • Thanks Jaime,

    after install the patch you pointed, the original one successfully installed.

    Tuesday, January 10, 2017 8:27 AM