Jump to content

Recommended Posts

Posted

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..

 

sqlfail.PNG

Posted

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 ?

Posted
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).

  • Thanks 1
Posted (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 by MYK-IT
  • Thanks 1
Posted

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)

Posted
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.
  • 11 months later...
Posted

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 ?-)

 

SCCM error.PNGSQL now.PNG

Posted
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.
Posted

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.

Posted
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 :D

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...