Windows Small Business Server 2011 Premium includes SQL Server 2008 R2 http://www.microsoft.com/sbs/en/us/editions-overview.aspx. This version is feature by feature the same as SQL 2008 R2 Standard with the difference that it must be installed in an Small Business Server domain or, if purchased separately, an environment with certain characteristics. But, what does that mean?
SQL 2008 R2 Standard for Small Business is supported for installation in a small business domain, which includes installing on one of the following Windows Server® 2008 R2 editions:
If the check fails, you will see the a failed check in the "Operating system supported for edition” topic.
Clicking in the Failed status shows the following message:
--------------------------- Rule Check Result --------------------------- Rule "Operating system supported for edition" failed. This SQL Server edition is not supported on this operating system. See SQL Server Books Online for information about supported operating systems for SQL Small Business Server edition. ---------------------------
SQL Server 2008 R2 setup logs (check SQL Server detail.txt installation file available on C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log)
2011-07-08 15:52:32 Slp: Rule evaluation message: The SQL Server 2005 Express Tools are not installed. 2011-07-08 15:52:32 Slp: Send result to channel : RulesEngineNotificationChannel 2011-07-08 15:52:32 Slp: Initializing rule : Operating system supported for edition 2011-07-08 15:52:32 Slp: Rule applied features : ALL 2011-07-08 15:52:32 Slp: Rule is will be executed : True 2011-07-08 15:52:32 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.EditionRequirementCheck 2011-07-08 15:52:33 Slp: O destino de uma invocação accionou uma excepção. 2011-07-08 15:52:33 Slp: em System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) em System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) em System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) em System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) em Microsoft.SqlServer.Configuration.SetupExtension.EditionRequirementCheck.CheckSBSEnvironment() em Microsoft.SqlServer.Configuration.SetupExtension.EditionRequirementCheck.Microsoft.SqlServer.Configuration.RulesEngineExtension.IRuleInitialize.Init(String ruleId) em Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.Execute(Boolean stopOnFailure) 2011-07-08 15:52:33 Slp: Rule initialization failed - hence the rule result is assigned as Failed 2011-07-08 15:52:33 Slp: Send result to channel : RulesEngineNotificationChannel 2011-07-08 15:52:33 Slp: Initializing rule : Previous releases of Microsoft Visual Studio 2008 2011-07-08 15:52:33 Slp: Rule applied features : IS;BIDS;Tools;SSMS 2011-07-08 15:52:33 Slp: Rule is will be executed : True
In this case setup was running under local non-domain account. In order to avoid this problem: