Configuration Manager 2012 Reports: Fixing the Console Create Report Error

Trying to create a custom report from the Configuration Manager 2012 console’s Reporting node can fail with an error along these lines:

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

Cause

When the CM2012 console is installed, it registers a Report Builder version reference that doesn’t match the version actually required by the console’s “Create Report” button — the console expects a newer Report Builder version than the installer leaves in place.

The Fix

We’ve packaged an MSI installer that applies the corrected registry value for you: CM2012ReportFix.zip. Since it’s an MSI, you can also add it to your Software Catalog and push it out to other admin workstations that hit the same error, rather than fixing each machine by hand. After running it, reopen the Configuration Manager console and try Create Report again from the Reporting node — it should now launch Report Builder correctly instead of throwing the manifest error.

Is This Still Relevant on Current Configuration Manager? (Updated for 2026)

This specific Report Builder version-mismatch bug is tied to Configuration Manager 2012’s own reporting services point integration, which shipped against an older Report Builder release. Configuration Manager 2012 has been out of support for years, and current Configuration Manager (2603) ships with its reporting stack aligned to a modern SQL Server Reporting Services release, so this exact manifest error generally isn’t something you’ll hit on a current site. If you’re still running CM2012 today for any reason, the MSI fix below remains a valid workaround; if you’re on a current version and see a similar-looking Report Builder error, check your SQL Server Reporting Services version and the site’s reporting services point configuration first, since a version mismatch there is a more likely cause than the same CM2012-era registry issue.

Resources

• SQL
• MSI