Scenario-

A minor annoyance when I tried creating a SCCM report this morning I received “Report Builder click-once application error” out of the blue.  After reviewing it with my fellow colleagues it appeared to be companywide for quiet some time.  Only one other person knew about this (shows how often custom reports are created).  After searching for a solution I could not find a specific resolution.  Here is how I was able to resolve it, if there is a better way please share!

Environment-

SCCM 2012 SP1, Server 2008 R2 running both SCCM+DB locally, SQL 2008 R2.

Error-

The report builder click-once application does not exist on the report server “server”.  Ensure that the report builder application manifest exists on the server and try again.

figure 1

Fix-

Perform the following on the SSRS Server defined by SCCM, in this instance it was a dedicated SQL instance installed locally on the SCCM Server.

Open regedit and change the value  HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/ConfigMgr10/AdminUI/Reporting from ReportBuilder_2_0_0_0.application to ReportBuilder_3_0_0_0.application

figure 2

Remove the Reporting services point role and re-add it to the site server-

figure 3

figure 4

Now a little bit closer the error has changed to Unable to connect to the remote server (which really isn’t remote)

figure 5

You will also see event 7703 spamming the operation manager “SCOM” event viewer-

figure 6

Exception calling “Fill” with “1” argument(s): “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol)”Error occured during CPU Usage for SQL Instances data source executing.

Computer:TESTLAB

Reason: Exception calling “Fill” with “1” argument(s): “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol)”

From here I re-deployed the web sites through SSRS to resolve these errors with a  reboot.

Select Advanced, then Remove

figure 7

Repeat the process but Add “All assigned” IP addresses (for this environment)

figure 8

Now we can create reports 🙂

figure 9

Summary- So a minor annoyance turned out to be quiet the problem.  Hopefully this is limited to our SCCM environment and not re-occurring in others.  I have not seen this in any other environments (Yet).

–End of line

Advertisement