Answered Installing SQL server 2008 R2

  • Saturday, January 19, 2013 5:14 PM
     
     

    I have windows 7 and I have been trying for day to install SQL server 2008 r2 Developer but for some reason it is not installing right. Below I will post pictures on what errors I been getting. I have looked up things to try and I think I tried about everything. Can someone please help me out.

All Replies

  • Saturday, January 19, 2013 5:57 PM
    Moderator
     
     

    From the second image, it appears that you were able to get it installed, correct?  Or is this an image from SSMS on a remote machine?  It also appears that you are trying to connect to the instance named "Home".  Is this the instance name you created during install?  If you used the default instance name, you can connect by supplying only the machine name.  Ex:  Home-PC (from your image).  Also, are you trying to connect locally or remotely?   Try to connect locally first to see if that works, then try remotely to determine if remote connections are enabled, firewall is appropriately opened, etc.

    Thanks,
    Sam Lester (MSFT)


    My Blog

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

  • Saturday, January 19, 2013 6:45 PM
     
     
    Well when i tried to connect to the database part that is the error I would get it doesn't matter if I connect that way or manual it will not connect at all. I turned firewall off.When I install it the instance was set at default.
  • Saturday, January 19, 2013 6:48 PM
    Moderator
     
     

    Just to confirm, are you connecting locally from the same machine where SQL Server engine is installed?  If so, is the SQL Server service running?  When you launch SSMS and supply the machine name only, are you able to connect?

    Thanks,
    Sam Lester (MSFT)


    My Blog

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

  • Saturday, January 19, 2013 6:51 PM
    Moderator
     
     

    Here is a blog from the SQL Server connectivity team on troubleshooting error message 26 from your second screenshot:

    http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx

    Before digging too deep into this article, I would suggest making sure the service is running and you can connect locally from SSMS.

    Thanks,
    Sam Lester (MSFT)


    My Blog

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

  • Saturday, January 19, 2013 7:04 PM
     
     
    Just check SQL Server configuration tool wizzard, check tcp ip and named pipe are enabled or not, enable them and try to connect by providing proper instance name and credential

    Mark this post as answer if this resolves your issue.


    Everything about SQL Server | Experience inside SQL Server -Mohammad Nizamuddin

  • Saturday, January 19, 2013 7:12 PM
     
     
    Yes I am connecting on the same machine that I have the SQL server in. An no I can not even connect given the machine name either.
  • Saturday, January 19, 2013 7:31 PM
     
     
    I need the database engine but it keeps failing and I have no clue why.
  • Saturday, January 19, 2013 8:00 PM
     
     

    Show me your Ready to Install page you might have captured during installation.  It looks like it is not a fresh install. Install again. Have you chosen the architecture correctly (x32 or x64)?

    Did you pass all the Setup support rules?

    are you using a evaluation copy?

    Verify that you have chosen the Database Engine Services in the feature selection page of installation.

    Do you have enough disk space?

    Have you configured the Server correctly?

    In SQL Server 2008 R2 shortcut in All Programs can you open the SQL Server Configuration Manager?

    You have to provide more information before something can be suggested.


    mysorian

  • Saturday, January 19, 2013 8:38 PM
     
     

    Here are some more pictures:

  • Sunday, January 20, 2013 12:57 AM
    Moderator
     
     

    Hello,

    Please try the resolution on the following post:

    http://blogs.msdn.com/b/vsnetsetup/archive/2009/10/29/sql-server-2008-setup-fails-with-a-microsoft-net-framework-exception.aspx  

    Take note that the AppData folder is a hidden folder.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

  • Sunday, January 20, 2013 1:04 AM
     
     
    This is what I got now.
  • Sunday, January 20, 2013 6:00 AM
    Moderator
     
     

    Hello,

    Please share with us the summary.txt and detail.txt log files. The following article may help you locate the files on disk:

    http://technet.microsoft.com/en-us/library/ms143702(v=sql.105).aspx

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

  • Sunday, January 20, 2013 1:46 PM
     
     

    Here is the summary:

    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2061893608
      Exit facility code:            1306
      Exit error code:               24
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2013-01-19 15:23:46
      End time:                      2013-01-19 20:04:50
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xD15B4EB2%400x4BDAF9BA%401306%4024

    Machine Properties:
      Machine name:                  HOME-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered

    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         C:\Users\Home\Downloads\SQL Server 2008 R2 Developer (x86, x64, ia64) - DVD (English)\x64\setup\
      Installation edition:          DEVELOPER

    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            Home-PC\Home
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
      FILESTREAMLEVEL:               2
      FILESTREAMSHARENAME:           MSSQLSERVER
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           Home-PC\Home
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False

      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\ConfigurationFile.ini

    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x4BDAF9BA@1306@24
      Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\Detail.txt

      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x4BDAF9BA@1306@24
      Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\Detail.txt

      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x4BDAF9BA@1306@24
      Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\Detail.txt

      Feature:                       Analysis Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x4BDAF9BA@1306@24
      Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\Detail.txt

      Feature:                       Integration Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Client Tools Connectivity
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Management Tools - Complete
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Management Tools - Basic
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Client Tools SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Business Intelligence Development Studio
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       SQL Server Books Online
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Microsoft Sync Framework
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

    Rules with failures:

    Global rules:

    Scenario specific rules:

    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130119_151924\SystemConfigurationCheck_Report.htm

  • Sunday, January 20, 2013 2:08 PM
     
     
    They are saying the detail.txt is too long to put on here so how should I put it in here?
  • Sunday, January 20, 2013 5:59 PM
     
     

    "Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes"

    Above error means that SQL Server setup is trying to start the SQL Service, but for some reason, the SQL service fails to start. Check the SQL errorlog for more information about the failure as well. You should be able to find the errorlog file in the setup log folder where you have your detail.txt file

  • Sunday, January 20, 2013 7:00 PM
     
     

    Here is the summary:

    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.

    You should take this step.


    mysorian

  • Sunday, January 20, 2013 7:30 PM
    Moderator
     
     Answered
  • Sunday, January 20, 2013 7:51 PM
     
     
    I am going to try to install it again and see if I get any errors I did reformat my hard drive so this is will be first install on it to see if that will help.
  • Sunday, January 20, 2013 11:09 PM
     
     
    I finally figure it out I had to reformat my computer then installed it and everything works now. Thanks everyone on their help.
  • Sunday, January 20, 2013 11:14 PM
     
     
    That was a bit drastic but anyway.

    mysorian