Close Menu
    Facebook X (Twitter) Instagram
    Sunday, October 12
    X (Twitter) LinkedIn Reddit RSS
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»SCCM 2012»Managed SQL server FixSQLRegistryKey stopped working

    Managed SQL server FixSQLRegistryKey stopped working

    Eswar KonetiBy Eswar KonetiApril 03, 6:27 pm1 Min Read SCCM 2012 6,889 Views
    Share
    Facebook Twitter LinkedIn Reddit

     

    Trying to install the required Prerequisites files for Configuration Manager 2012 all are done except SQL sever SP1 with CU4.

    SQL server 2008 R2 has got installed but later SP1(QLServer2008R2SP1-KB2528583-x64-ENU) failed with Error “Managed SQL server FixSQLRegistryKey stopped working”

    Trying to fix this by looking at registry/setup log file but I couldn’t.

    image

    The Fix is to Uninstall Microsoft .NET Framework 4 Extended and Microsoft .NET Framework 4 Client Profile

    Managed SQL server FixSQLRegistryKey stopped working Remove .net Framework 4 SQL SQL server 2008 R2 SP1 doesnt work
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    SCCM SQL Report – Compare Installed Apps on TWO Different Computers

    July 13, 10:35 am

    Monitoring Endpoint Security Applications with SCCM ConfigMgr SQL

    October 11, 8:48 pm

    Addressing SCCM Software Update Deployment Challenges with PowerShell – Remote install

    October 23, 10:23 am

    8 Comments

    1. mpleaf on July 11, 2012 3:59 AM

      That worked beautifully! Thanks so much!

      I actually used "QUIETSIMPLE" instead of "QUIET", cause I like to see stuff! Still worked great.

      mpleaf

      Reply
    2. mpleaf on July 6, 2012 1:43 AM

      I get this same error, with a little different circumstance. I am doing my SQL install from the command line in an unattend file, so that as soon as my server/image powers up, I end up with SQL installed. Works great! Ta-dah, instant SQL server 2008 R2 server. Now, I added a line to my unattend file, to install the SP1 as follows:
      "C:\ServerBuild\SQLInstallation\SQLSP\setup.exe" /QUIETSIMPLE /ALLINSTANCES /INDICATEPROGRESS /IACCEPTSQLSERVERLICENSETERMS
      Launches great, but I get the same error here. I don't really have the ability to uninstall .net4 at this point and reinstall later. I downloaded the SP1 .exe file and extracted it all to the local C:\...\SQLSP directory, so the files are all local. Why would I continue to get this error with all install files local?
      Any suggestion on making this work from a truly automated functionality would be greatly appreciated!
      mpleaf

      Reply
      • Eswar Koneti on July 6, 2012 8:27 AM

        Hi Thomas,
        Can you the command line for unattended installation for SP1 path "Filename.exe /Action=Patch /IAcceptSQLServerLicenseTerms /AllInstances /Quiet"

        via http://www.ronnipedersen.com/2012/01/installing-sql-server-2008-r2-for-configmgr-2012/ for more information.

        Reply
    3. mpleaf on July 6, 2012 12:09 AM

      Folks,
      I have the same error coming up, but my situation is a "little" different. I have sysprep set up, so that once my server is powered on for the first time, it does the SQL Server 2008 R2 install from command line. Works like a charm! I then have it install SP1 from command line with the following command:
      "C:\ServerBuild\SQLInstallation\SQLSP\setup.exe" /QUIETSIMPLE /ALLINSTANCES /INDICATEPROGRESS /IACCEPTSQLSERVERLICENSETERMS
      ...which halts at the above error. Keep in mind, I am intending all of this to be "silent", from the unattend file. I can't really "remove" .net4 and then "readd". The files are already completely local (I downloaded the .exe, and extracted all into the C:\...\SQLSP directory. All files all there, so this should not be an issue?

      Anyone have direction further on this as to how I can do this from a fully automated perspective?
      mpleaf

      Reply
    4. fred38ostin on June 29, 2012 7:46 AM

      Recover sql server databases thanks to programmed method I would recommend you next utility sql fix

      Reply
    5. Steve Beaumont on May 10, 2012 12:47 AM

      Hi Eswar!
      Like Allan said with the link to my blog post, it's mainly due to .net 4 introducing tighter security policies around remote installation sources.

      You can either:
      1) Remove .net 4 (which ConfigMgr requires so will need re-installing)
      2) Copy the SQL source files locally or mount from an ISO
      3) Change the CasPol settings (doesn't always work)
      4) Edit some config files to force legacy CasPol and .net 2 preference.

      Regards,
      Steve

      Reply
      • Eswar Koneti on May 10, 2012 1:31 PM

        Good one.

        Reply
    6. Allan on May 3, 2012 12:39 AM

      Actually, there are workarounds.

      I had the exact same problem. I copied the files locally and it worked, but I read that you can also use a DVD/ISO or give FullTrust permissions with CasPol.

      Reference: http://systemscentre.blogspot.com.br/2012/02/installing-sql-2008-r2-from-remote.html (the error is slightly different, but the solution is the same)

      Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2025 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.