Required SQL Server Collation Failed on SCCM server, when no SQL is installed on that Server

Hi,

I've been trawling through the support forums trying to find a resolution to this, but while I find others asking the questions, there are no answers to this particular issue.

I am trying to install SCCM 2012 R2 and a Server 2012 R2, and have an SQL server instance on a separate server. When running the SCCM installation, if reports that Required SQL Server Collation Failed, but reports the system I am installing SCCM to, NOT the SQL server instance. There is no SQL on the SCCM server, other than WID for the WSUS. I have tried installing this with SQL Express with the correct collation, but it still reports tha same collation error.

Is there an issue with this? Can anyone help to point to the collation setting on a server that does not have SQL installed?

Thanks for any help!



August 24th, 2015 9:18am

 I have tried installing this with SQL Express with the correct collation, but it still reports tha same collation error.


That's not supported (SQL express).
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 9:23am

Thanks Torsten, but you mis-understand. I am not trying to install with SQL Express, we are running with full SQL on a separate managed server with the correct collation set.

The Failure error says the collation is incorrect on the SCCM server itself, which has NO SQL INSTALLED.

I stated I even tried installing SQL Express so that I could set a collation, as I can't see any way to set collation on a server that does not have SQL installed.

I have rebuilt the SCCM server, with NO SQL AT ALL, pointed to our full SQL server which  is passing the collation check, but I'm still getting a Collation error reported on the SCCM server itself.

How can this be failing a Collation check when there is no SQL installed on that server?


August 24th, 2015 9:29am

Hi,

Does this still happen if you use a newly installed SQL server? It is highly recommend to do this only on a SQL which is not in use by any other appli

Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 3:38am

Hi,

We had this running OK in a test Lab, but this is our Live deployment. I believe we have traced the issue, no thanks to the misleading errors from the SCCM installer or logs. The production SQL server was installed with a different Server collation (European default), but the SCCM DB instance had the "correct" US specific Collation.

Our DB team had thought the collations were set as required on the SQL server, but obviously had not noted the details of SCCM 2012 requiring the Server Collation to be set specifically too, not just the DB instance collation. This is different to SCCM 2007 where the DB instance is all that is collation specific.

It is not realistic for us to have a dedicated licensed SQL server for one instance, certainly not cost-effective use of very expensive SQL licenses.

It appears we will have to build a new SQL server to meet SCCM 2012's rather unfriendly collation requirements, and migrate our more standard and collation compatible DB instances to that to ensure we are cost and license efficient.

Thanks for the responses guys, apologies for taking your time when this was a collation issue after all, if a somewhat hard to diagnose issue from the logs/errors.

August 27th, 2015 5:08am

Hi,

We had this running OK in a test Lab, but this is our Live deployment. I believe we have traced the issue, no thanks to the misleading errors from the SCCM installer or logs. The production SQL server was installed with a different Server collation (European default), but the SCCM DB instance had the "correct" US specific Collation.

Our DB team had thought the collations were set as required on the SQL server, but obviously had not noted the details of SCCM 2012 requiring the Server Collation to be set specifically too, not just the DB instance collation. This is different to SCCM 2007 where the DB instance is all that is collation specific.

It is not realistic for us to have a dedicated licensed SQL server for one instance, certainly not cost-effective use of very expensive SQL licenses.

It appears we will have to build a new SQL server to meet SCCM 2012's rather unfriendly collation requirements, and migrate our more standard and collation compatible DB instances to that to ensure we are cost and license efficient.

Thanks for the responses guys, apologies for taking your time when this was a collation issue after all, if a somewhat hard to diagnose issue from the logs/errors.

There is not cost for the SQL licensing for CM12, they are included with the cost of CM12. It is not recommend that you share SQL server with any other application. Plus it is recommend that CM12 and SQL be install locally to each other.
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 6:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics