locked
RC0 setup failure - .NET 4.0 and x64 RRS feed

  • Question

  • Hello.

    I am not having much joy attempting to install SQL Server 2012 RC0 x64 on Windows 2008 R2 SP1 Enterprise Edition (build 7601)

    I've used the .exe and .box files from my msdn subscription to install it instead of the .iso

    I'm installing it using a domain admin account,

    It falls over at the Install_CotNetCore_Cpu64_Action step 

    with error: Microsoft .NET Framework 4.0 installation has failed with exit code 1

    I looked through the log files but there doesn't appear to be anymore useful info than the error above. The DotnetCore_Cpu_1.log file is just a HTML doc that contains nothing useful as far as I can see so I dont know what to do next other than log this on connect too because I cant attach my log files on here

    Cheers

    Wednesday, February 8, 2012 2:28 PM

All replies

  • Hi,

    Please look at below link and check if it helps

    http://connect.microsoft.com/SQLServer/feedback/details/712945/sql-2012-rc0-install-fails-with-net-4-0-error

    ======================================

    Please mark as answer if helpful

    Thursday, February 9, 2012 4:33 AM
  • thanks for the reply.

    I added the registry keys as per the connect log and manually installed .net 4.0 and it still doesn't work.

    on the install validation page it even says that .net 4.0 is already installed yet it fails with the same error:-

    Error details:
    § Error installing Microsoft .NET Framework 4.0
    Microsoft .NET Framework 4.0 installation has failed with exit code 1.
    Error code: 1
    Log file: c:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120209_082700\DotNetKB2533523_Cpu64_1.log

    Why try and install something you know that's there already?? I'll log it on connect I think.

    Thursday, February 9, 2012 8:53 AM
  • Hi Rob,

    try to install this update:

    http://www.microsoft.com/download/en/details.aspx?id=27014

    description

    http://support.microsoft.com/kb/2533523

    I'm assuming this by your error log DotNet KB2533523 it might help, let me know.

    Before that check your version of .NET framework in Programs and Feature, I found treath posting about beta .NET causing this problem:

    It turned out that for me, the cause of the problem was that I had a .NET 4 beta component installed, and I forgot to remove it. I saw it when I decided I was going to reinstall .NET 4. So I removed it. Now these updates are no longer trying to re-install themselves, finally.

    Regards


    • Edited by Ursa Pangos Thursday, February 9, 2012 9:10 AM
    Thursday, February 9, 2012 9:07 AM
  • thanks that bit worked. I had no previous versions of .NET installed thought, this was a brand new clean install of windows.

    however - I now have more errors further along the install, a runtime error this time.

    Here's a snippet of my detail log for the failure:-

    (01) 2012-02-09 13:22:03 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
    (01) 2012-02-09 13:22:03 Slp: External component has thrown an exception.
    (01) 2012-02-09 13:22:03 Slp: The configuration failure category of current exception is ConfigurationFailure
    (01) 2012-02-09 13:22:03 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
    (01) 2012-02-09 13:22:03 Slp: System.Runtime.InteropServices.SEHException: External component has thrown an exception.
    (01) 2012-02-09 13:22:03 Slp:    at Microsoft.Win32.SafeNativeMethods.CloseHandle(IntPtr handle)
    (01) 2012-02-09 13:22:03 Slp:    at System.Runtime.InteropServices.SafeHandle.InternalDispose()
    (01) 2012-02-09 13:22:03 Slp:    at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
    (01) 2012-02-09 13:22:03 Slp:    at System.Diagnostics.Process.Close()
    (01) 2012-02-09 13:22:03 Slp:    at System.Diagnostics.Process.Dispose(Boolean disposing)
    (01) 2012-02-09 13:22:03 Slp:    at System.ComponentModel.Component.Dispose()
    (01) 2012-02-09 13:22:03 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
    (01) 2012-02-09 13:22:03 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
    (01) 2012-02-09 13:22:03 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
    (01) 2012-02-09 13:22:03 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
    (01) 2012-02-09 13:22:03 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
    (01) 2012-02-09 13:22:03 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
    (01) 2012-02-09 13:22:03 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2012-02-09 13:22:03 Slp: Inner exceptions are being indented
    (01) 2012-02-09 13:22:03 Slp:
    (01) 2012-02-09 13:22:03 Slp: Exception type: System.Runtime.InteropServices.SEHException
    (01) 2012-02-09 13:22:03 Slp:     Message:
    (01) 2012-02-09 13:22:03 Slp:         External component has thrown an exception.
    (01) 2012-02-09 13:22:03 Slp:     Data:
    (01) 2012-02-09 13:22:03 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
    (01) 2012-02-09 13:22:03 Slp:       WatsonConfigActionData = INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
    (01) 2012-02-09 13:22:03 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
    (01) 2012-02-09 13:22:03 Slp:     Stack:
    (01) 2012-02-09 13:22:03 Slp:         at Microsoft.Win32.SafeNativeMethods.CloseHandle(IntPtr handle)
    (01) 2012-02-09 13:22:03 Slp:         at System.Runtime.InteropServices.SafeHandle.InternalDispose()
    (01) 2012-02-09 13:22:03 Slp:         at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
    (01) 2012-02-09 13:22:03 Slp:         at System.Diagnostics.Process.Close()
    (01) 2012-02-09 13:22:03 Slp:         at System.Diagnostics.Process.Dispose(Boolean disposing)
    (01) 2012-02-09 13:22:03 Slp:         at System.ComponentModel.Component.Dispose()
    (01) 2012-02-09 13:22:03 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
    (01) 2012-02-09 13:22:03 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
    (01) 2012-02-09 13:22:03 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
    (01) 2012-02-09 13:22:03 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
    (01) 2012-02-09 13:22:03 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
    (01) 2012-02-09 13:22:03 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
    (01) 2012-02-09 13:22:04 Slp: Watson Bucket 1
     Original Parameter Values

    I'm sad to say this but its unlikely my company will upgrading to SQL 2012 based on my experiences so far, I cant even install it let alone test it.

    Thursday, February 9, 2012 1:55 PM
  • Hi Rob,

    can you please take a look at system and HW requirements:

    http://msdn.microsoft.com/en-us/library/ms143506%28v=sql.110%29.aspx

    and needed permisiion for services accounts

    http://msdn.microsoft.com/en-us/library/ms143504%28v=sql.110%29.aspx

    and confirm you have all this.

    I also found posts sugessting that if you have some builds of Windows Server, from MSDN library, installation might not suceed. So if you have an option to try intalling on some other Windows Server (other installation media), this would be an option too (if all above requirements are meet).

    This might help too (post for sql express, but some more things to check):

    http://social.msdn.microsoft.com/Forums/zh/sqlsetupandupgrade/thread/5a3727d0-35b6-4dae-9d1a-3423987aa14b

    I have set up and configure SQL 2012 without any problems.

    Regards


    • Edited by Ursa Pangos Friday, February 10, 2012 12:46 PM
    Friday, February 10, 2012 12:39 PM
  • Hey there,
    I´m trying to install Denali RC0 on a Win 7 fully patched in a HV VM with VS CTP installed.

    There´s .Net 4 Client Profile Deu Language Pack and Multi-Targeting Pack
    and naturally 4.5 Dev Peview packs for VS 11 CTP.

    I tried ALL the above.
    4 Full and Full SC wouldn´t install. Neither would the Reliability Update.

    After running the two regs it installed a couple more items, including the SS Man Studio, but NOT the RC0 DB engine, still reporting the .Net 4 1642 error.

    The SQLEXPRESS CTP3 installed with VS CTP only wants to Attach version 7 DBs, but neither AdventureWorks2008R2_Data.mdf nor AdventureWorksDWDenali_Data.mdf which both seem to be 7.05.

    Thx
    G.

    Tuesday, February 14, 2012 3:20 PM
  • Hi,

    this is bug from MS Connect abot .NET

    http://connect.microsoft.com/SQLServer/feedback/details/712945/sql-2012-rc0-install-fails-with-net-4-0-error

    Gue22, what did you install SQL 2012 RC0 (Release candidate) or SQLEXPRESS CTP3?

    "To ensure proper working of the samples you must ensure that all databases and tabular models and samples belong to the same release version. For example, mixing the SQL Server Code-Named “Denali" CTP3 with SQL Server 2012 RC0 may cause issues."

    Regards

    Wednesday, February 15, 2012 9:15 AM
  • Re: bug from MS Connect about .NET

    As I said: I tried ALL the above, including the two reg-edits from Connect, but the install still reports the .Net 4 problem.

    OTOH I realized that I actually don´t need the SQL Server 2012 RC0 Developer version on the same (virtual) machine! I simply got another VM with the Dev RC0, which I need for column-store experiments!

    Though the reported error is a *.Net 4* problem (and not a problem with the 4.5 beta), I realize VS´s Denali CTP3 and 2012 RC0 on the same machine are no good idea. Though the one is SQLEXPRESS and the other a full version, I guess they´re basically the same install and will interfere.

    I uninstalled the SS RC0 parts that DID install and the whole VS 11 today.

    Do you think a SS 2012 RC0 Dev and VS 11 *without* the Denali CTP3 SQLEXPRESS part would work?

    Thx
    G.

    Wednesday, February 15, 2012 9:42 PM
  • I'm not shure, I've installed RC0 2012 and I'm using BIDS which came with it (2010) and everything works perfect.

    I wasn't shure where you are trying to restore AdventureWorksDWDenali_Data.mdf, on RC0 or Express version, that's why I've poste you the above answer.

    If you have time and resources, then try to install RC0 individually on clean machine.

    If you have .NET error and you installed VS 2011, this could be a case, while .NET Framework 4.5 Developer Preview is installed as part of Visual Studio 2011 Developer Preview and SQL 2012 RC0 is using .NET Framework 4.

    Regards


    • Edited by Ursa Pangos Thursday, February 16, 2012 9:48 AM
    Thursday, February 16, 2012 8:58 AM
  • Sorry Gue,

    I havent read your poste carfully enough.

    I think SQL Express TCP3 and RC0 shouldn't produce .NET error while they are using same version.

    The only difference is if you install Express .NET 4 in snot included in installation package, but if you are installing RC0 it is (feature installation package). And for both is requirements that are installed on OS that already has .NET 3.5 with SP1 up and running.

    http://sqlblog.com/blogs/aaron_bertrand/archive/2011/08/10/36736.aspx

    Regards



    • Edited by Ursa Pangos Thursday, February 16, 2012 9:25 AM
    Thursday, February 16, 2012 9:20 AM