Hi folks, I just thought I'd pop in and ask if there's any known issues (including the option simply isn't supported) with using SQL Server 2012 Standard as the database server for a new SCCM 2012 installation? The reason I ask is that I've worked through the prerequisites to the point where the remaining three don't concern me (this is solely a test environment, by the way, not production), yet when I elect to conduct the installation, I get the following error: Could not connect or execute the SQL query. Click the View Log button for more information. I've run an SQL Server Profiler session and have validated that both my account (for checking the pre-requisites) and the SCCM server's computer account (which the setup routine switches to for the actual installation) both have the capacity to log onto the SQL Server, so I'm not entirely sure what I'm up against here. Before I start dumping information, I'll clarify a couple of points: The SCCM server's computer account is both a local administrator and SQL Server sysadmin role holder;The Windows Firewall is not an issue. Program rules exist for both the database and browser service, and for the purpose of testing, I have created an inbound open access rule where the scope is restricted to the new SCCM host. And now to the information dumps. Firstly, here's the pre-requisite check warnings I have ignored as non-issues prior to launching the installation (again, this is only a test environment - virtualised at that): Secondly, here's the results of the SQL Server 2012 Profiler trace which appear after the setup has been started (i.e. after the pre-req check has finished): EventClass ApplicationName DatabaseName HostName LoginName ServerName StartTime TextData Audit Login SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.8 =-- network protocol: TCP/IP SQL:BatchCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.8 exec sp_server_info 18 SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.8 exec sp_server_info 18 SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set ansi_warnings on; SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set ansi_padding on; SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set ansi_nulls on; SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set concat_null_yields_null on; SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set arithabort on; SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set numeric_roundabort off; SQL:StmtCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set DATEFORMAT mdy; SQL:BatchCompleted SCCM_SYStoSQL_TEST_SERVICE master SCCMSRV01 TEST\SCCMSRV01$ SQLSRV01\ISCO 40:40.9 set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; Finally, here is the contents of the latter portion of ConfigMgrSetup.log (i.e. commencing the actual setup after the pre-req finalisation): ~~===================== << Starting Configuration Manager 2012 Setup >> ===================== $$<Configuration Manager Setup><04-10-2012 10:34:02.468-480><thread=2688 (0xA80)> INFO: ConfigMgr2012 Setup was started by TEST\admin.account. $$<Configuration Manager Setup><04-10-2012 10:34:02.484-480><thread=2688 (0xA80)> INFO: Command line specified was: "SetupWpf.exe" $$<Configuration Manager Setup><04-10-2012 10:34:02.484-480><thread=2688 (0xA80)> ~FQDN for server SCCMSRV01 is sccmsrv01.test.mydomain.edu.au $$<Configuration Manager Setup><04-10-2012 10:34:02.484-480><thread=2688 (0xA80)> INFO: Target computer is a 64 bit operating system. $$<Configuration Manager Setup><04-10-2012 10:34:02.593-480><thread=2688 (0xA80)> INFO: Checking for existing setup information. $$<Configuration Manager Setup><04-10-2012 10:34:02.593-480><thread=2688 (0xA80)> INFO: Checking for existing SQL information. $$<Configuration Manager Setup><04-10-2012 10:34:02.593-480><thread=2688 (0xA80)> INFO: Verifying the registry entry for Asset Intelligence installation $$<Configuration Manager Setup><04-10-2012 10:34:02.593-480><thread=2688 (0xA80)> INFO: Setting the default CSV folder path $$<Configuration Manager Setup><04-10-2012 10:34:02.593-480><thread=2688 (0xA80)> INFO: No language packs detected. $$<Configuration Manager Setup><04-10-2012 10:34:02.593-480><thread=2688 (0xA80)> INFO: Configuration Manager Build Number = 7711 $$<Configuration Manager Setup><04-10-2012 10:34:02.921-480><thread=2688 (0xA80)> INFO: Configuration Manager Version = 5.0 $$<Configuration Manager Setup><04-10-2012 10:34:02.921-480><thread=2688 (0xA80)> INFO: Configuration Manager Minimum Build Number = 800 $$<Configuration Manager Setup><04-10-2012 10:34:02.921-480><thread=2688 (0xA80)> INFO: Verifying Configuration Manager Active Directory Schema Extensions. $$<Configuration Manager Setup><04-10-2012 10:34:02.921-480><thread=2688 (0xA80)> INFO: Found DS Root:CN=Schema,CN=Configuration,DC=test,DC=nd,DC=edu,DC=au~ $$<Configuration Manager Setup><04-10-2012 10:34:02.936-480><thread=2688 (0xA80)> INFO: Verifying Configuration Manager Active Directory Schema Extensions. $$<Configuration Manager Setup><04-10-2012 10:34:02.968-480><thread=2688 (0xA80)> INFO: Found DS Root:CN=Schema,CN=Configuration,DC=test,DC=nd,DC=edu,DC=au~ $$<Configuration Manager Setup><04-10-2012 10:34:02.968-480><thread=2688 (0xA80)> INFO: Validating characters in path from Program Files\Microsoft Configuration Manager $$<Configuration Manager Setup><04-10-2012 10:34:03.202-480><thread=2688 (0xA80)> INFO: Evaluation Product Key was specified. $$<Configuration Manager Setup><04-10-2012 10:34:03.202-480><thread=2688 (0xA80)> INFO: VL or OEM Product Key was specified. $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: Installing Evaluation version. $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: 'sccmsrv01.test.mydomain.edu.au' is a valid FQDN. $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: 'sccmsrv01.test.mydomain.edu.au' is a valid FQDN. $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> ERROR: Failed to connect to registry to determine if Configuration Manager console is installed. $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: 'sqlsrv01.test.mydomain.edu.au' is a valid FQDN. $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: This is a named instance SQL Server. $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: SQL Server instance name (pSetupInf->SqlInstName): ISCO $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: SQL Server master database (pSetupInf->SqlMasterDB): ISCO\master $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: Site SQL Server database name (pSetupInf->SqlDatabaseName): ISCO\CM_FRE $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> INFO: Site SQL Server computer name (pSetupInf->SqlServer): sqlsrv01.test.mydomain.edu.au $$<Configuration Manager Setup><04-10-2012 10:34:07.149-480><thread=2688 (0xA80)> ~~===================== Failed Configuration Manager 2012 Server Setup ===================== $$<Configuration Manager Setup><04-10-2012 10:34:08.116-480><thread=2688 (0xA80)> Cheers, Lain

It's always a good idea to have a look at the product docs first. The supported configurations are listed here: http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig and SQL 2012 is not mentioned at all. So it's not supported. CM12 related questions should be posted to http://innovation.connect.microsoft.com/discussions?ProjectName=configmgrbeta as long as no Technet forums are available.Torsten Meringer | http://www.mssccmfaq.de

Thanks Torsten. I clearly didn't look hard enough when I first started the process as I thought I'd read that page. Nevertheless, I think I'll push on and see if I can't diagnose the issue, as there's still a number of things I haven't tried, not the least of which are the backwards compatibility components. It seems odd that the pre-requisites check and the very first part of the setup work happily before halting one to two seconds into the installation. As it's only the test environment, the worst that can happen is a waste a bit of quiet time in between the busy periods. Cheers, Lain