Managed SQL server FixSQLRegistryKey stopped working


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.


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

8 Responses to "Managed SQL server FixSQLRegistryKey stopped working"

  1. That worked beautifully! Thanks so much!

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


  2. 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:
    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!

  3. 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:
    ...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?

  4. 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.



Leave a Reply