none
SQL Server 2008 Installation - Rule "Operating system supported for edition" failed.

    Question

  • Hi there,

    I've just performed a fresh install of both Windows Server 2008 Standard and SQL Server 2008 Standard Edition for Small Business.  At the end of the SQL Server installation I'm getting the above installation rule failure.

    I've seen the installation requirements detailed here: http://www.microsoft.com/sqlserver/2008/en/us/small-business.aspx , and as far as I can tell we are not violating any of them.

    We have a single server set up to perform ActiveDirectory on a single domain for about 50 employees.

    Is there a way to find out precisely what is causing the problem?

    Thanks, Shareef.
    Friday, November 27, 2009 5:51 PM

Answers

  • So due to time restraints I ended up calling and paying for the microsoft support.

     

    The result was that my issue had nothing to do with SQL.  The way I was setting it up was indeed a valid way to set it up, which was SBS 2008 hosting the AD and 2008 standard hosting the SQL.

     

    My issue, as it turns out, was that I did a migration of my DC.  However for one reason or another my migration was done improperly.  While all the functions that I had previously used worked, in the background there was issues with my DNS and who was in fact the DC.  I had remnants of the source server in my DNS/AD sites and services/AD users and computers.  I had to go in and manually wipe out all the entries.

    Tuesday, April 06, 2010 12:49 AM

All replies

  • Thanks but that is the same info in the post I linked to above.  What I need to know is how I find out which of the rules failed?

    Shareef.
    Saturday, November 28, 2009 11:43 AM
  • Hi Shareef,

    Please open the setup summary.txt which indicates a Rule Report File, check that file you will know which rules failed. The summary.txt is at %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Log by default.
    ChunSong Feng
    Microsoft Online Community Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Tuesday, December 01, 2009 2:33 AM
    Moderator
  • Hi


        Try to login through domain login and install. It will not install successfull through local admin login

    Regd
    Rajesh
    Friday, February 12, 2010 7:56 AM
  • Hi, I was referred here from this thread.

     

    http://social.technet.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/c9821312-6825-422b-9dda-bcfbc0b9bf6b

     

    Here's the setup.txt, I don't quite understand it.

     

     

    Overall summary:

      Final result:                  User cancelled

      Exit code (Decimal):           -2068380094

      Exit facility code:            1207

      Exit error code:               1602

      Exit message:                  User has cancelled.

      Start time:                    2010-04-05 09:47:28

      End time:                      2010-04-05 09:56:56

      Requested action:              Install

     

    Machine Properties:

      Machine name:                  US2

      Machine processor count:       2

      OS version:                    Windows Server 2008

      OS service pack:               Service Pack 2

      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

      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}

      ProductName:                   SQL2008

      Type:                          RTM

      Version:                       10

      SPLevel:                       0

      Installation location:         E:\x64\setup\

      Installation edition:          STANDARD

     

    User Input Settings:

      ACTION:                        Install

      ADDCURRENTUSERASSQLADMIN:      False

      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM

      AGTSVCPASSWORD:                *****

      AGTSVCSTARTUPTYPE:             Manual

      ASBACKUPDIR:                   D:\SQLSERVER\MSAS10.MSSQLSERVER\OLAP\Backup

      ASCOLLATION:                   Latin1_General_CI_AS

      ASCONFIGDIR:                   D:\SQLSERVER\MSAS10.MSSQLSERVER\OLAP\Config

      ASDATADIR:                     D:\SQLSERVER\MSAS10.MSSQLSERVER\OLAP\Data

      ASDOMAINGROUP:                 <empty>

      ASLOGDIR:                      D:\SQLSERVER\MSAS10.MSSQLSERVER\OLAP\Log

      ASPROVIDERMSOLAP:              1

      ASSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE

      ASSVCPASSWORD:                 *****

      ASSVCSTARTUPTYPE:              Automatic

      ASSYSADMINACCOUNTS:            ICT\ktseng

      ASTEMPDIR:                     D:\SQLSERVER\MSAS10.MSSQLSERVER\OLAP\Temp

      BROWSERSVCSTARTUPTYPE:         Disabled

      CONFIGURATIONFILE:             

      ENABLERANU:                    False

      ERRORREPORTING:                False

      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS

      FILESTREAMLEVEL:               0

      FILESTREAMSHARENAME:           <empty>

      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE

      FTSVCPASSWORD:                 *****

      HELP:                          False

      INDICATEPROGRESS:              False

      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\

      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\

      INSTALLSQLDATADIR:             <empty>

      INSTANCEDIR:                   D:\SQLSERVER

      INSTANCEID:                    MSSQLSERVER

      INSTANCENAME:                  MSSQLSERVER

      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService

      ISSVCPASSWORD:                 *****

      ISSVCSTARTUPTYPE:              Automatic

      MEDIASOURCE:                   E:\

      NPENABLED:                     0

      PID:                           *****

      QUIET:                         False

      QUIETSIMPLE:                   False

      RSINSTALLMODE:                 FilesOnlyMode

      RSSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE

      RSSVCPASSWORD:                 *****

      RSSVCSTARTUPTYPE:              Automatic

      SAPWD:                         *****

      SECURITYMODE:                  SQL

      SQLBACKUPDIR:                  <empty>

      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS

      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM

      SQLSVCPASSWORD:                *****

      SQLSVCSTARTUPTYPE:             Automatic

      SQLSYSADMINACCOUNTS:           ICT\ktseng

      SQLTEMPDBDIR:                  <empty>

      SQLTEMPDBLOGDIR:               <empty>

      SQLUSERDBDIR:                  <empty>

      SQLUSERDBLOGDIR:               <empty>

      SQMREPORTING:                  False

      TCPENABLED:                    1

      X86:                           False

     

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

     

    Detailed results:

      Feature:                       Database Engine Services

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       SQL Client Connectivity SDK

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       SQL Server Replication

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Full-Text Search

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Analysis Services

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Reporting Services

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Integration Services

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Client Tools Connectivity

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Management Tools - Complete

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Management Tools - Basic

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Client Tools SDK

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Client Tools Backwards Compatibility

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Business Intelligence Development Studio

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       SQL Server Books Online

      Status:                        Failed: see logs for details

      MSI status:                    Passed

      Configuration status:          Passed

     

      Feature:                       Microsoft Sync Framework

      Status:                        Failed: see logs for details

      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\20100405_094638\SystemConfigurationCheck_Report.htm

     

    Exception summary:

    The following is an exception stack listing the exceptions in outermost to innermost order

    Inner exceptions are being indented

     

    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException

        Message: 

            User has cancelled.

        Stack: 

            at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()

            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)

            at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)

            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)

            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)

            at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)


     

    Monday, April 05, 2010 4:58 PM
  • So due to time restraints I ended up calling and paying for the microsoft support.

     

    The result was that my issue had nothing to do with SQL.  The way I was setting it up was indeed a valid way to set it up, which was SBS 2008 hosting the AD and 2008 standard hosting the SQL.

     

    My issue, as it turns out, was that I did a migration of my DC.  However for one reason or another my migration was done improperly.  While all the functions that I had previously used worked, in the background there was issues with my DNS and who was in fact the DC.  I had remnants of the source server in my DNS/AD sites and services/AD users and computers.  I had to go in and manually wipe out all the entries.

    Tuesday, April 06, 2010 12:49 AM
  • Hi,

    Thanks for your update here :)


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Tuesday, April 06, 2010 10:50 AM
    Moderator
  • I came across this issue with a new installation. I had a brand new sbs premium server (the dc/ active directory controller) and another windows server 2008 standard which was for the sql server.

    To install sql server 2008 in this way, your login credentials must be both a local admin on the ws2008 box as well as a domain admin on the sbs controller.

    the HOSTS file in c:\windows\system32\drivers\etc had an entry there for the DC, but it was in fact the wrong ip address (the servers were installed by the manufacturer).  So it could not authenticate correctly.  It would also take a long time to login, search the domain etc etc, because of this.

     

    So to make it short, check your network and DNS settings!

     

    Dallas

    Sunday, May 16, 2010 11:41 PM
  • I tried this and did find remnants of the old server under AD sites and services. I removed it and still does not allow me to install. Anyone have any input or feed back on how to take care of this issue?
    Thursday, February 17, 2011 5:27 PM