ConfigMgr 2012 SMS SRS REPORTING POINT Component Failure

Reposting this because page was deleted

Written by Phil Schwan

Ran into an interesting issue in the ConfigMgr 2012 lab today.  When I went into Monitoring and expanded the Reporting node, there weren’t any reports listed as available. I hadn’t yet gone into the Reporting since building the lab, so this was the first I was aware that something was wrong. I checked the System Status and sure enough the Reporting Point component was showing errors:

Error 7403: The report server service is not running on Reporting Service Point server “CM01.LAB.local”; start the service to enable reporting.

Looking in the System Event Log there were more indications of problems:

Event ID: 7009
A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.

Event ID:      7000
The SQL Server Reporting Services (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Doing a little research, it looked as though others had a similar issue with previous SQL Server versions following installation of certain Microsoft updates or hotfixes such as KB948109.  In this case during the lab setup, I installed SQL Serve 2008 R2, the SP1 update, and the Cumulative Update 5 (CU5) per current requirements.  I attempted to re-run CU5 just to be certain, but setup indicated that there were no components requiring update and that everything was current.

Because the event log errors indicated a timeout (and because I didn’t want to get into uninstalling/reinstalling some or all of SQL just yet), I extended the ServicesPipeTimeout registry value to 60 seconds.  Upon reboot, SQL Reporting Services fired right up, and the Reports were populated and available to run in the console.

Here are the steps from the site linked above:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane, locate the ServicesPipeTimeout entry.
   Note: If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
   On the Edit menu, point to New, and then click DWORD Value.
   Type ServicesPipeTimeout, and then press ENTER.
   Right-click ServicesPipeTimeout, and then click Modify.
4. Click Decimal, type 60000, and then click OK.
   This value represents the time in milliseconds before a service times out.
5. Restart the computer.

Share on Google Plus

About Tom DeMeulenaere

Highly accomplished information technology professional with extensive knowledge in System Center Configuration Manager, Windows Server, SharePoint, and Office 365.