I ran into this issues last night when I was installing System Center 2012 R2: Data Protection Manager in my lab. The Error itself is self-explanatory, however for someone who’s new to DPM or someone who has little knowledge about SQL server, might not really understand why this is failing.
Data Protection Manager uses a SQL Server to store it’s data in a database that is created during the installation of DPM. DPM also relies on SQL Server Reporting Services for certain reporting functionalities, in fact, Reporting Services is a requirement for the deployment of DPM. When I initially deployed SQL Server 2012 R2, I also deployed the Reporting Services feature, however I forgot to setup the Reporting Services database and so I ran into this issue:
We can typically do this step during the SQL server installation, there’s normally an option that you can chose to either install the service with or without configuration. I obviously chose to install the feature without Reporting Services configuration, so the database was never created. This is why I needed to create it post-installation. With that said, let’s take a quick look at how we can configure the Reporting Services database, post-installation.
First, you’ll need to connect to your SQL server, and just to throw it out there, the steps are very similar with SQL Server 2008 R2. In our case, for the demonstration purposes of this blog post, we’re going to be using SQL Server 2012 R2 instead. So, once connected to the SQL Server, we’ll need to open Reporting Services Configuration Manager which can be found in the start menu
Once the database wizard is launched, we’ll need to chose to either create a new database or use an existing database. Of course the choice is yours, however in my case, I did not create the database manually so I had no databases to chose from, hence I chose to create a new database
Before creating a new database, we’ll need to use a service account to connect to the database server, in my case, I used a SQL server service account. By default if you use the integrated security authentication option, then the account that you login with with, will be selected by default, you can however chose to use a SQL server account, but you’ll need to make sure you’ve enabled your SA account for that. Once the connection has been validated, we can proceed to the next part.