SCOM2012: OpsMgr 2012 fails to launch due to SDK service not running

I bumped in to this error today when i was about to launch my new OpsMgr12 Installation:

 

So what could be the reasons for this kind of error?

1. Check firewall settings so that nothing is preventing the connection betwen the target machine.

2. If that’s not the problem, then check if these to services are running  “System Center Data Access (OMSDK)” if not try to start it manual. Also check if OpsMgr VSS Writer” Service is running. If not, start it.

3. Check SQL account’s so that everything is ok.

 

Error: the data access service is either not running or not yet initialized

Advertisements

SCCM2012: SQL collation error

If you are planning on installing Configuration Manager 2012 then before you do you need to be sure that your SQL collation is set to SQL_Latin1_General_CP1_CI_AS. If you live in the US then that’s probably what it is set to already but if not, and if you are using regional settings that may change the default collation (for example Swedish) then you will need to reinstall SQL from scratch to change the SQL collation or  try some unsupported hacks to resolve your collation issues. If you are wondering why then it’s because ConfigMgr setup will not let you continue without the correct Collation. Full. Stop.

Configuration Manager 2012 requires SQL collation set toSQL_Latin1_General_CP1_CI_AS. Yup that’s it. And here’s where it states that on Technet. Expand the SQL Server Requirements section and look at the Collation field. And I quote: “The instance of SQL Server in use at each site must use the following collation: SQL_Latin1_General_CP1_CI_AS.”

If you have already install SQL and want to verify the collation settings prior to running ConfigMgr setup, then you can start SQL Server Management Studio and look at theServer Collation section of the General page as in this screenshot by right clicking on the database server and choosing properties.

How can i set the collation? If you are installing SQL server and want to set the collation manually, you can do so on the Server Configuration screen as pictured below, simply click on the collation tab.

Now you need to uninstall your SQL instance, this is what technet say about it: http://support.microsoft.com/kb/955499

  • We recommend that you use the Add or Remove Programs feature in Control Panel to uninstall SQL Server.

Then install SQL again it might complain about reporting files that may be left over. Just ignore the reporting part of the SQL installation.

 

//Karl