none
Can't create reports RRS feed

Answers

  • I found a Fix!

    Edit in a text editor the file:
    "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe.config"

    Scroll down to the <ReportBuilderMapping> section. In my case it originally contained

      <ReportBuilderMapping>
        <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" />
      </ReportBuilderMapping>

    Replace the 2's with 3's so it looks like this:

      <ReportBuilderMapping>
        <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" />
      </ReportBuilderMapping>

    Close and open the console and you now can edit reports...


    Neil Clinch

    • Proposed as answer by Neil Clinch Thursday, February 7, 2013 5:43 PM
    • Marked as answer by Witchdoctor12 Saturday, February 9, 2013 4:08 AM
    Thursday, February 7, 2013 5:43 PM

All replies

  • No. SSRS is perfectly fine on the SQL Server. Did you install ReportBuilder 3.0 on the SQL Server?

    Jason | http://blog.configmgrftw.com

    Monday, February 4, 2013 8:42 PM
  • Ok the SQL admin just installed Report Builder 3.0 on the SQL server and I'm still getting the same message.   The message refers to the SCCM server not the SQL server.   Does Report Builder need to be installed on the SCCM server as well?

    Thanks again

    WD

    Monday, February 4, 2013 10:01 PM
  • Ok we've added Report Builder 3.0 to the SQL server, the SCCM server and the console machine.   We are still getting the same message.

    Should we add the Reporting Services Point to the Primary site and the secondary site?

    Monday, February 4, 2013 10:59 PM
  • When launching the admin console, make sure you launch it elevated.

    Jason | http://blog.configmgrftw.com

    Tuesday, February 5, 2013 2:07 AM
  • Yes I am running the console as administrator.   This is getting frustrating.

    I appreciate all your help.

    WD

    Tuesday, February 5, 2013 4:04 PM
  • Did you install this on the computer where the console is running?
    • Edited by Maartentje Wednesday, February 6, 2013 9:28 AM
    Wednesday, February 6, 2013 9:27 AM
  • Ok I've installed the Report Builder 2.0 and I still get the same results.    The message 'The Report Builder click-once application does not exist on the report server 'sccmprimary.ourdomain.bc.ca'.', is specifically referring to the machine running our SCCM primary site.   This machine does not have the Reporting Services Point on it.  Instead the RSP is running on the machine that has the SQL server on it.   Does RSP have to be on the primary site server?

    All thoughts and comments greatly appreciated.

    WD

    Wednesday, February 6, 2013 3:53 PM
  • I have the same issue... after SP1 upgrade of SCCM 2012.

    As part of the upgrade I upgraded my SQL server 2008 R2 SP1 (CU6 I think?) to SP2 and CU4. I only have one SCCM server and it is the SQL server also. So I was wondering if Witchdoctor12 did the same thing I did to get the error.

    I can install report builder if I access the Reports website. If I try through the SCCM console I get the above error. So as a workaround just use the website


    Neil Clinch

    Wednesday, February 6, 2013 11:00 PM
  • The Reports website can be accessed at http:// <Server>/Reports


    Neil Clinch


    • Edited by Neil Clinch Wednesday, February 6, 2013 11:07 PM
    Wednesday, February 6, 2013 11:04 PM
  • Or just install the full Report Builder 3.0 on your local system. Easier than killing yourself over the 1-click install.

    Jason | http://blog.configmgrftw.com

    Thursday, February 7, 2013 1:03 AM
  • I am also having this same problem after upgrading to SP1.   We have installed Report Builder 3.0 / changed the registry key for the AdminUI \ Reporting \ ReportBuilderApplicationManifestName to ReportBuilder_3_0_0_0.application.

    Any updates on this?  -- there appears to be a few threads reporting this same issue.

    Thursday, February 7, 2013 1:53 PM
  • Jason...

    I have already tried to install the full report builder 3 on my PC...The issue is the SCCM console wants to open the One-Click version on the reporting server and then you get the error.  So you can't edit reports by right clicking on them in SCCM console.  It is a convenience issue/training issue to get people to just use the website.


    Neil Clinch


    • Edited by Neil Clinch Thursday, February 7, 2013 5:11 PM
    Thursday, February 7, 2013 5:09 PM
  • I found a Fix!

    Edit in a text editor the file:
    "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe.config"

    Scroll down to the <ReportBuilderMapping> section. In my case it originally contained

      <ReportBuilderMapping>
        <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" />
      </ReportBuilderMapping>

    Replace the 2's with 3's so it looks like this:

      <ReportBuilderMapping>
        <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" />
      </ReportBuilderMapping>

    Close and open the console and you now can edit reports...


    Neil Clinch

    • Proposed as answer by Neil Clinch Thursday, February 7, 2013 5:43 PM
    • Marked as answer by Witchdoctor12 Saturday, February 9, 2013 4:08 AM
    Thursday, February 7, 2013 5:43 PM
  • My God you are a freakin genius.    How you found that I'll never know but it worked for me.   Now comes the painstaking task of learning how to create the reports the boss is looking for.

    WD

    Friday, February 8, 2013 4:33 PM
  • Good to hear that it worked for you too...

    Can you mark my response as the answer.


    Neil Clinch

    Friday, February 8, 2013 10:31 PM
  • I should add, I tried your answer on another machine that had the console and it worked.   The difference between the two machines was I had done a lot of other things to the first machine to try and get this working, installing Report Builder 3.0 and other things.  So I wasn't sure that it wasn't a collection of things that made the first machine work.  Since the second machine didn't have all the extra things done to it, it was simply your solution that fixed the problem.

    Thanks to everyone who made comments and suggestions.

    WD

    Saturday, February 9, 2013 4:11 AM
  • Did absolutley nothing else besides this fix and it worked.  SP1 must have borked this file somehow.  Have some newpeople installing the console for the first time on their workstations soon.  We'll see if they need this fix also.

    Thanks again!!

    Friday, April 26, 2013 4:01 PM