A short time ago I wrote a post where I made some comments about problems involving System Center Configuration Manager (SCCM) 2012 Reporting Point and SQL Server.
Today I have faced a similar situation, during the installation of System Center Operations Manager (SCOM) 2012.
As well as with SCCM, during the the installation of SCOM’s Reporting Service it is common to have problems when listing available instances of SSRS, in fact, the instances are NOT listed.
I can’t be really sure that is the same problem I had with SCCM, since my environment is already “fixed” for that problem (I have a default SSRS instance and everything I explain on the previous post), but aparently it is the same problem. Anyway, there are a few things worth mentioning.
One of them is that to install SCOM’s “Reporting Service” you must first install “Management Server” on its respective server (since it problably won’t be the same server as the one where SQL Server will be) without installing “Reporting Server”.
After that the installation of SCOM’s Reporting Service MUST be done by starting the installer from the same box where SQL Server is at.
Another important point is that we may NOT install SCOM’s Reporting Service on the same SSRS that is being used by another service, like SCCM, since SCOM has its own security mode and may (problably will) change all your SSRS security configuration and you may end with no access to your existing reports on that instance.
So there comes an interesting point. We should have an exclusive SSRS instance for SCOM and, as we know, the collation of the database engine hosting its databases (and the databases for any service from System Center 2012) must be “SQL_Latin1_General_CP1_CI_AS“, but it does NOT mean that you must have another database engine!
What you can do is to install another SSRS instance, BUT host the databases on the SAME instance where you host the databases from other System Center program, like SCCM.
To do this you just need to install SSRS without configuring the service and, later, when configuring and it is time to create the database, select an instance that uses the collation needed to host SCOM’s database.