Problems installing SCCM 2012

I have been trying on and off the past couple of days to get SCCM 2012 to install in my small environment (50 systems). I have resolved all of the prerequisites except for those in regards to SQL. I'm getting the following (my attempts to resolve the issues are bold):

The logon account for the SQL Server service cannot be a local user account or LOCAL SERVICE.  You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
The instance of SQL has been set to run as domain\sccm (service account), but error still shows up.


Configuration Manager requires that you configure your SQL Server instance and Configuration Manager site database (if already present) to use the SQL_Latin1_General_CP1_CI_AS collation, unless you are using a Chinese operating system and require GB18030 support.  For information about changing your SQL Server instance and database collations, see http://go.microsoft.com/fwlink/p/?LinkID=234541.  For information about enabling GB18030 support, see http://go.microsoft.com/fwlink/p/?LinkId=234542.
I've confirmed through multiple installs of SQL 2008 R2 that the proper collation is used

Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.
During the install of SQL 2008 R2 I specified the computer account (domain\SCCM$) and domain\sccm (service account) have sysadmin rights

I thought that it might have to do with the version of SQL I'm using, say lacking a CU. I'm running SQL 2008 R2 10.50.4000 which I believe equates to 20008 R2 w/SP2 and no CU. This is a supported version according to here:http://technet.microsoft.com/en-us/library/gg682077.aspx

Any ideas what the problem could be?
futureman0Asked:
Who is Participating?
 
rlogCommented:
In your output file "ERROR: Failed to connect to SQL Server database" is mentioned. I believe your connection string to the database server is the problem here. Please specify servername,port (use comma) to connect directly to sql server. You should not use dynamically set port for your server. Check also that SQL Browser replies (and that the fw port is open (udp 1434).
0
 
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
SCCM would need the prescribed version. No use trying without it.

Please upload the logs in the root of c:\ for SCCM server here. (prereq etc)
0
 
futureman0Author Commented:
See Attached

I thought I was using an supported version of SQL - SQL 2008 R2 W/SP2 and no CU
PreReq.txt
0
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

 
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
CUs are needed.

http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLSrvReq


The following table lists the SQL Server versions that are supported by System Center 2012 Configuration Manager.
 
SQL Server version       

SQL Server 2008

    Standard1

    Enterprise

    Datacenter

      

SP2
      

Minimum of cumulative update 9
0
 
futureman0Author Commented:
CU 9 is for SQL 2008 SP2, I have installed SQL 2008 R2 SP2
0
 
futureman0Author Commented:
Perhaps the issue is related to running SQL Express, can someone point me to the trial version of SQL 2008 R2 standard that will work with SCCM 2012?
0
 
futureman0Author Commented:
I think what might have caused the issue was the SQL Browser service was set to disabled. Once I enabled it, re-verified what @rlog said to check, I was able to get SCCM installed.

Interesting enough, the "Assess server readiness" on the splash screen still fails with the same error - but going through the install process doesn't show any errors.
0
 
rlogCommented:
As a general rule the sql browser is not enabled on dedicated systems. If your sccm database runs on a dedicated server I would set a fixed non-default port and specify the port in the connection string. On a general server where you host a number of different databases it's ok to run the sql browser on the server.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.