RabbieBurns Posted February 28, 2012 Posted February 28, 2012 Im trying to have a play with SCCM 2012 and I cant seem to get past the pre requesite check (see attached) Ive added the sccm2012 machine account to the administrators group on the SQL server, Ive disabled all firewalls to make sure its not a port thing, cant really find any other info on what I should be doing..
Arthur Posted February 28, 2012 Posted February 28, 2012 Are you using SQL Server 2008 SP2 with Cumulative Update Package 6?
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 Nope, using SQL Server 2008 R2 SP1 with CU4 Supported Configurations for Configuration Manager
Arthur Posted February 28, 2012 Posted February 28, 2012 I thought you might be using the latest version of SQL but wasn't sure. Are there any things listed in this guide which you may have missed?
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 Thats the guide I followed actually. I'm pretty sure I followed it precisely but Ill double check, one thing though I'm not sure about the bit that says about SQL_Latin1_General_CP1_CI_AS collation. The SQL Collation is one of the checks that fails. How do I check the SQL server is using SQL_Latin1_General_CP1_CI_AS collation ?
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 Also my SQL is on a separate server not sure if that makes a difference?
Arthur Posted February 28, 2012 Posted February 28, 2012 How do I check the SQL server is using SQL_Latin1_General_CP1_CI_AS collation? One way to check the collation would be to use this PowerShell script. To change it, try the script shown here (I haven't tried it myself though). 1
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 the script to change it only seems to change an existing db not the actual server. Ive also tried the method here Setting and Changing the Server Collation This is the output of the check script, is this the wrong one? I might have to uninstall and reinstall SQL I guess. Where abouts is the collation stuff in the setup steps I dont seem to remember it.
MYK-IT Posted February 28, 2012 Posted February 28, 2012 (edited) Apologies in advance if this is duff information, but i thought that I had come across SQL_Latin1_General_CP1_CI_AS before. Just looked through my book Migrating to Windows 7 using MDT 2010 Lite Touch and WDS and it's mentioned in relation to the MAPS Database installation for MDT. Within SQL Server Installation Centre, select Service Accounts Tab {numerous steps for new setting up new database, and after you've completed the Instance Root Directory and Disk Space Requirements} sections On the Collation Tab; Make sure that the Database Engine is set to SQL_Latin1_General_CP1_CI_AS Hope this helps is some way (still learning it myself! MDT 2010 that is) Edited February 28, 2012 by MYK-IT 1
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 Thanks.. I guess Ill just blow away this SQL server and re-install.
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 although Im assuming this will only fix the Collation error in my first post, I guess I should try to fix the other 2 as well before I go reinstalling.
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 right reinstalled SQl with the correct collation but it still fails the pre-req check (i think the pre-req check is looking for SQL on the local server) So Im trying to install it anyway and specify the remote server, but its failling when trying to connect to the SQL DB: Exception message: [A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)], Exception details: [system.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
theriver Posted February 28, 2012 Posted February 28, 2012 Worth taking the setup app out of the equation? Try setting up an ODBC alias to the SQL Server using the credentials you're plugging into the setup, show you whether you can connect to the database server in the first place.
RabbieBurns Posted February 28, 2012 Author Posted February 28, 2012 I used the same SQL server to install SCVMM 2012 and SCOM 2012 no problem so the database and the credntials seem to be working OK..
genie Posted February 6, 2013 Posted February 6, 2013 I have the semilar problem with the one with i reinstall SQL 2008 R2 just to change collation from "Latin1_general_CI_AS" to "SQL_Latin1_general_CP1_CI_AS" and after reinstall is still have that error that i dont have "SQL_Latin1_general_CP1_CI_AS" here are two pic one of is from SQL and one from SCCM install my question if my SQL is SQL_Latin1_general_CP1_CI_AS how come is error under installation of SCCM 2012 ?-)
andyfield Posted February 11, 2013 Posted February 11, 2013 Took me ages to get this working. Managed to work out that I had to configure the dynamic ports. Check this http://www.sccm.biz/2012/03/sccm-2012-setup-on-dedicated-sql-2008.html?m=1#! Hope it helps
free780 Posted February 12, 2013 Posted February 12, 2013 Create a domain user account to run the sql services. Disable interactive logon. Add domain admins to users during sql setup who can administer the server. It is a bit confusing at first. Correct collation needed and cu6 for sql 2008 r2 sp1. Looks like you need to install wsus on the sccm server.
Tall_Paul Posted February 13, 2013 Posted February 13, 2013 I had the same collation problem after installing SQL Server 2012. To fix it you have to essentially reinstall SQL Server which is what the link you provided details how to do. I didn't use the strong password switch, and it ran fine and passed the prerequisite check.
genie Posted February 14, 2013 Posted February 14, 2013 Hello Thank you so much after i Remove 0 and download some hotfix to sql 2008 r2 and it could begin to install and thx again
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now