System Center 2012 Configuration Manager: 'Create Report' Doesn't Work, so what do I do now?(Updated)

Today I was working in my lab creating custom reports, and when I clicked on Create Report, I received the following message:

“The Request Failed with HTTP status 503: Service Unavailable”.

My first impression was that I forgot a pre-req, as usual - when we don’t make a check list we do often forget stuff! But then I realized there was something more going on within my System Center 2012 Configuration Manager lab.

Read on to find out how I troubleshot it:


The Problem

To give you a better idea of the problem, I:

- launched System Center 2012 Configuration Manager Console

- clicked on Monitoring Workspace > Reporting > Reports

- and then clicked Create Report on the ribbon.


That produced a Configuration Manager dialog box with the error:

The request failed with HTTP status 503: Service Unavailable.


First, I checked the services to make sure all of them were started, and I found that SQL Server Reporting Services was stopped.

So, I right-clicked and chose Start.


But once I started the service, I tried again and got this nice message:

The Report Builder click-once application does not exist on the report server ‘’. Ensure that the report builder application manifest exists on the server and try again.


To fix this I went ahead and downloaded Report Builder 3.0, ran it, and used the wizard to install it.

As a note: when you get to the following screen on the wizard to enter the Default Target Server, make sure you enter the reporting service point you are using for that site.


Note: If the target server is not running SharePoint Integrated Mode, you may need to enter .

Then, I clicked Next and followed the rest of the wizard until I finished the installation.

Now that we’ve finished installing the Report Builder we need to do a small change in the registry in order to use it. (I know is a lot of small steps, but will be worth it once we’ve finished!)

The following link provides more information about the process we will perform: .


The Solutions

1. On the computer running the Configuration Manager console, open the Windows Registry Editor. (Start, type REGEDIT and press Enter)

2. Browse to HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft/ConfigMgr10/AdminUI/Reporting

3. Double-click the ReportBuilderApplicationManifestName value to edit the value data.

4. Change ReportBuilder_2_0_0_0.application to ReportBuilder_3_0_0_0.application, and then click OK.

5. Close the Windows Registry Editor.

Right, that’s done!

Now let’s open the System Center 2012 Configuration Manager Console and try to use the Create Report button again:


Success! Now I can create my custom report!

I hope these steps to fix this problem help you if you’ve run into the same thing.

SP1 Update

As a note for SP1, please use these steps too:

Use Notepad or any text editor to open the file:

*Note Open Notepad as Administrator, otherwise you won’t be able to save the edits.

"C:\Program Files (x86)\Microsoft Configuration
Scroll down to the <ReportBuilderMapping> section.

In my case it originally contained


    <add key="11.0" value="ReportBuilder_3_0_0_0.application"/>
    <add key="10.50" value="ReportBuilder_3_0_0_0.application" />
    <add key="10.0" value="ReportBuilder_2_0_0_0.application"/>
    <add key="DEFAULT" value="ReportBuilder_2_0_0_0.application"/>


We want to replace the 2's in those last two lines with 3's, so it looks like this:


    <add key="11.0" value="ReportBuilder_3_0_0_0.application" />
    <add key="10.50" value="ReportBuilder_3_0_0_0.application" />
    <add key="10.0" value="ReportBuilder_3_0_0_0.application"/>
    <add key="DEFAULT" value="ReportBuilder_3_0_0_0.application"/> 


If these steps helped you, please leave a comment!

Thanks for those that has contribute to this post to make it better, your assistance is very appreciated.

 Note* if you are looking for some R2, Check out my post on RBA.

Santos Martinez - Premier Field Engineer - SMS/ConfigMgr/SQL


Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of any included script samples are subject to the terms specified in the Terms of Use