Archive

Archive for the ‘Reporting Point’ Category

Create a Robust, Integrated Reporting Solution using SQL Server Reporting Services and System Center Configuration Manager

Reporting is a crucial ability for most organizations—and the ability to provide robust reporting of various Microsoft System Center Configuration Manager (SCCM) functions is no exception. Reporting is a feature that hasn’t changed much over several versions of Systems Management Server and SCCM. With the release of SCCM R2, reporting has undergone one significant change—the ability to interface and take advantage of SQL Server Reporting Services (SSRS). This one change brings with it the ability to make use of the many robust features SSRS provides. Like any new technology, there is a learning curve associated with SSRS—but the benefits are well worth it.

Steve Rachui has discuss the integration between SCCM and SSRS and walk through a very simple example of building a report in SSRS and publishing for use in SCCM.

Its worth to read it…

http://technet.microsoft.com/hi-in/magazine/ee914611(en-us).aspx 

Thanks and Regards |Abhishek Joshi |www.AbhishekJoshi.com

Incoming search terms:

Troubleshoot the issue of Error 500, when accessing SMS/SCCM reports

November 25, 2009 2 comments

Last month one of our stake holder facing problem while running SCCM report . He was facing error 500 in internet explorer. when checked the IIS logs find below error is appearing

After searching on the web, found SMS 2003 Faq’s http://technet.microsoft.com/en-us/library/cc875797.aspx . However, our servers are installed with SCCM 2007 and IE7. After going through the SMS 2003 FAQ and http://learn.iis.net/page.aspx/373/editing-configuration-files/ we were able to solve the problem. Below are the steps.

Resolution Steps:

1) Open the latest IIS log file using SMS trace utility and filter it by “buffer” (filter by “contains”). You will see error logs as below. You can find the report ID number.

2) Run the report in Internet Explorer and observe whether same error entry is appearing in the IIS logs or not.

3) If yes, go to that report in SMS console, and take the SQL query for that report. Then run the query on the SMS database and check for how many rows it returned?

4) You need to adjust a registry value on the SMS Reporting Point to allow the return of a larger row set. To do that, go to HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Reporting Add a DWORD value Rowcount and assign it a value for the desired maximum limit, the maximum row count is 32767 (decimal) But if you need to return more, then set it to 0xffffffff (Hex). This will return all rows but will significantly increase the workload on your site server database. It is not recommend doing this until it is critical to do these settings.

5) Open console of IIS manager 7.0

6) Select server Name.

7) On the right pane, right click on ASP and click on Open feature

8 ) Change the value of “response buffering time-out”. To decide upon “response buffering time-out “ please check how many maximum rows we expect from the report and based on that do math 1 MB per 1000 records. However, it’s ideal. After changing the value if error is still appearing in IIS logs. Please calculate the “response buffering time-out” value by doing math of 2MB per 500 Records.

9) Change “Script Timeout” value to 180 sec.  The default is 90.

10 ) Run the report

Thank and Regards |Abhishek Joshi| www.AbhishekJoshi.com

Incoming search terms: