Post reply

hotfix KB3144114 won't install on default instance

  • May 31, 2018 at 4:27 am

    #353505

    I am installing KB3144114 on all our SQL 2008 R2 instances to enable TLS 1.2 support. This has been fine everywhere except on one server that has a default and a named instance. It will install on the named instance but I cannot persuade it to install on the default instance. When I run the exe file from Windows explorer, on the Select Feature panel the named instance and Shared Features are ticked but I cannot tick MSSQLSERVER. If I run the exe file from the command prompt specifying /InstanceName=mssqlserver it appears to completes but the instance is not updated. Both the default and named instance are build 10.50.6000.

  • June 1, 2018 at 5:05 pm

    #1992729

    I had this problem once, can't remember what was the issue. Do you see any errors in bootstrap logs?

  • June 5, 2018 at 7:09 am

    #1992951

    curious_sqldba - Friday, June 1, 2018 5:05 PM

    I had this problem once, can't remember what was the issue. Do you see any errors in bootstrap logs?

    Thanks curious_sqldba. No errors in the logs. They only report what was done, not what wasn't done or why. The only other factor I can think of that might be relevant is that the name of the named instance is 'MSSQLSERVER2' and I'm wondering whether there's a bug in the unusual case where the instance name is 'MSSQLSERVER' + <extension> such that the MSSQLSERVER (ie default) instance isn't updated. However that seems unlikely and would be a lot of trouble to test. I think I'll have to uninstall the MSSQLSERVER2 instance, which we don't actually need, and see what happens.

  • June 7, 2018 at 5:23 am

    #1993189

    curious_sqldba - Friday, June 1, 2018 5:05 PM

    I had this problem once, can't remember what was the issue. Do you see any errors in bootstrap logs?

    FYI I have resolved this issue. The MSSQLSERVER2 instance was a red herring.

    I noticed (from the bootstrap logs actually) that Reporting Services was still at 10.50.1600 build, ie RTM. Presumably this made the instance ineligible for the hotfix. After rerunning the SP3 exe and bringing Reporting Services to 10.50.6000, the hotfix applied fine.

Viewing 4 posts - 1 through 3 (of 3 total)

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