none
failed installation of SQL Server 2014 RRS feed

  • Question

  • After several failed attempts to install SQL Server 2014 Developer Edition as a named instance on a PC, it is time to seek help.  Said PC has Windows 7, SP1, 64-bit and already has a default instance of SQL Server (2008 R2 Developer) and a named instance of SQL Server (SQL Express).  After each failed install of SQL Server 2014 an uninstall was performed to clean up the parts of 2014 that were installed.  The Summary file, provided at the end of the latest failed install, shows the following detailed results -

    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Master Data Services
      Status:                        Passed

      Feature:                       Distributed Replay Client
      Status:                        Passed

      Feature:                       Distributed Replay Controller
      Status:                        Passed

      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Data Quality Client
      Status:                        Passed

      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

      Feature:                       Reporting Services - SharePoint
      Status:                        Passed

      Feature:                       Reporting Services Add-in for SharePoint Products
      Status:                        Passed

      Feature:                       Documentation Components
      Status:                        Passed

      Feature:                       SQL Client Connectivity SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.

    Rules with failures:

    Global rules:

    Scenario specific rules:

    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141128_141920\SystemConfigurationCheck_Report.htm

    The only thing that's not green in the SystemConfigurationCheck_Report.htm file is this:

    Now this PC runs McAfee, which apparently controls Windows Firewall.  When the firewall is turned off in McAfee the Windows Firewall screen still says the Windows Firewall is on.  I don't see how to turn Windows Firewall off manually on a machine that runs McAfee.

    On the latest install attempt, I left the firewall turned on in McAfee and checked the box to allow port 1433 - see screen shot below (in previous install attempts this box was unchecked).  This install attempt failed and generated the messages described above.

    I am at a loss as to what to try next to get SQL Server 2014 to install.  Why isn't it working?

    Saturday, November 29, 2014 5:14 PM

Answers

  • RESOLUTION:

    In the log files from a failed install the Summary.txt file had a recurring message in the "Reason for failure" lines and that was "An error occurred for a dependency of the feature causing the setup process for the feature to fail."  A search in the Detail.txt file from the same installation attempt found several lines that contained "Feature dependency condition for action: Install_sql_engine_core_shared_Cpu64_Action".  A search on the internet for Install_sql_engine_core_shared_Cpu64_Action located this useful link:

    http://msdn.developer-works.com/article/12696830/Add+replication+feature+failed

    which recommends to copy the installation files from the DVD to C:\temp.  After doing this, SQL Server 2014 Developer Edition installed without issues.  However, a new problem came up: no SQL Server instances would run and SQL Server Configuration Manager > SQL Server Services looked like this:

    An internet search for SQL  server configuration manager the remote procedure call failed after 2014 install located this useful link:

    http://www.morgantechspace.com/2013/10/the-remote-procedure-call-failed-in-sql.html

    which recommends to apply Service Pack 2 to SQL Server 2008 R2 instances.  After doing that update, SQL Server Configuration Manager returned to normal and the SQL Server instances ran fine.



    • Marked as answer by Knot Sunday, December 14, 2014 11:04 PM
    • Edited by Knot Sunday, December 14, 2014 11:05 PM
    Sunday, December 14, 2014 10:55 PM

All replies

  • Hi,

    Can you post output of summary.txt file here. Its would be located at below location.it

    C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log . If you cannot find it use This link to locate it. The one you posted is this complete log is this the summary,txt log. If so then no information why SQL Server failed is mentioned here in that case you must upload content of Details.txt file on some shared location and post link here so that we can access and see the logs


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My Technet Wiki Article

    MVP

    Saturday, November 29, 2014 5:35 PM
    Moderator
  • Hello,

    Please see the following thread:

    http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/6c9c1163-7fed-4a24-a5ee-25c7a5ff58c4  

    This may be related to a corrupted media.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Saturday, November 29, 2014 5:39 PM
    Moderator
  • The text in the original post is part of the Summary.txt file - I should've said so but didn't think of it at the time.  I did find Detail.txt and uploaded it to my Dropbox account.  Try this link to view the file:

    https://www.dropbox.com/s/d55tz92byuzj3od/Detail.txt?dl=0

    Sunday, November 30, 2014 12:27 AM
  • As a test, I tried the install on a virtual machine that does not have McAfee security.  After turning off Windows Firewall on the virtual machine, the install was successful.  Therefore, I think the media is OK.  The results of this test suggest that the problem has to do with the firewall.  Does anyone know how to turn off the Windows Firewall manually on a machine that has McAfee security?  Or is there some other approach to solve this problem?
    Sunday, November 30, 2014 1:16 PM
  • Hi,

    Please see below to turn on and off windows firewall

    windows.microsoft.com/en-gb/windows/turn-windows-firewall-on-off#turn-windows-firewall-on-off=windows-7


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My Technet Wiki Article

    MVP

    Sunday, November 30, 2014 1:30 PM
    Moderator
  • Link is broken.

    I went to Control Panel > System and Security > Windows Firewall and got the following screen:

    The "Turn Windows Firewall on or off" option is disabled (which must be because of the McAfee software - it was not disabled on the virtual machine that does not have McAfee software).


    • Edited by Knot Sunday, November 30, 2014 2:36 PM
    Sunday, November 30, 2014 2:34 PM
  • Hi Knot,

    As your description, you come across an error when you install SQL Server 2014 developer edition. Please turn off the software McAfee, so that it can’t  scan the files related with SQL Server and ensure the smooth installation. According to your error log from Detail.txt, I get two error messages which indicate files are not found and one warning.

    1. .NET Framework standalone installation package is not found. .NET Framework 3.5 SP1 is a requirement for SQL Server 2014.

    Firstly, please check if .NET Framework 3.5(.NET 3.5) is enabled as per the path(Control Panel >> Programs and Features >> Turn Windows features on or off). If it is not enabled, please enable it.

    Secondly, you could check if .NET 3.5 is corrupted using .NET Framework Setup Verification Tool. If it is corrupted, please repair it using .NET Framework Repair Tool, then install SQL Server again and check if the error still occurs.

    2. sql_engine_core_inst.msi file is not found. So please check if the file exists in D:\x64\setup\sql_engine_core_inst_msi\x64, if it doesn’t exist, you could solve this issue by one of the methods, then install SQL Server again and check if the error still occurs.

    a. Use a script.

    b. Manually restore the files. For more information about the process, please refer to the article: http://support.microsoft.com/kb/969052

    3. One warning is that no matched disk size is detected. Before you run setup to install or upgrade SQL Server, verify that you have at least 6.0 GB of available disk space on the system drive. For more information about the process, please refer to the article: http://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx

    Regards,

    Michelle Li

    Monday, December 1, 2014 11:02 AM
    Moderator
  • I have run the .NET repair tool on this machine.  It seems as though the missing sql_engine_core_inst.msi file is located in a different place than where the computer is looking.  Rather than being in D:\x64\setup\sql_engine_core_inst_msi\x64 it is in D:\x64\setup\sql_engine_core_inst_msi instead.  How do I get the machine to find this file during the install process?



    • Edited by Knot Thursday, December 11, 2014 2:09 PM
    Thursday, December 11, 2014 2:08 PM
  • Update -

    1. installed another instance on virtual machine with Windows Firewall on and it was successful - this suggests that the firewall being on or off does not cause a problem when installing SQL Server 2014
    2. searched the Details.txt file of successfully installed instance for "File 'D:\x86\setup\sql_engine_core_inst_msi\x86\sql_engine_core_inst.msi' does not exist" message and it is present in that file - this suggests that missing file is not the reason for a failed install of SQL Server 2014
    3. ran the .NET repair tool on the PC where SQL Server 2014 won't install properly - it made no difference when an attempt to reinstall was made...it still failed

    I am bewildered by why it won't install on the PC and out of ideas for what to try next.  Any suggestions?

    Saturday, December 13, 2014 11:58 AM
  • RESOLUTION:

    In the log files from a failed install the Summary.txt file had a recurring message in the "Reason for failure" lines and that was "An error occurred for a dependency of the feature causing the setup process for the feature to fail."  A search in the Detail.txt file from the same installation attempt found several lines that contained "Feature dependency condition for action: Install_sql_engine_core_shared_Cpu64_Action".  A search on the internet for Install_sql_engine_core_shared_Cpu64_Action located this useful link:

    http://msdn.developer-works.com/article/12696830/Add+replication+feature+failed

    which recommends to copy the installation files from the DVD to C:\temp.  After doing this, SQL Server 2014 Developer Edition installed without issues.  However, a new problem came up: no SQL Server instances would run and SQL Server Configuration Manager > SQL Server Services looked like this:

    An internet search for SQL  server configuration manager the remote procedure call failed after 2014 install located this useful link:

    http://www.morgantechspace.com/2013/10/the-remote-procedure-call-failed-in-sql.html

    which recommends to apply Service Pack 2 to SQL Server 2008 R2 instances.  After doing that update, SQL Server Configuration Manager returned to normal and the SQL Server instances ran fine.



    • Marked as answer by Knot Sunday, December 14, 2014 11:04 PM
    • Edited by Knot Sunday, December 14, 2014 11:05 PM
    Sunday, December 14, 2014 10:55 PM