ADO.NET DataSet to SSRS – Links

By using is as XML Data Extension – http://blogs.msdn.com/b/bimusings/archive/2006/03/24/560026.aspx

By using Reporting Services data processing extensions –

http://msdn.microsoft.com/en-us/library/ms152917(v=sql.100).aspx

http://www.devx.com/dbzone/Article/31336/0/page/2

By Dynamically creating rdl and load it using CreateReport method – http://stackoverflow.com/questions/18437741/ssrs-with-custom-dataset-system-data-dataset

Default supported data sources – http://msdn.microsoft.com/en-us/library/ms159219(v=sql.100).aspx

 

Know more about the Report Server Settings, Report Server Service Trace Log

Know more about following in Microsoft Report Server using

http://technet.microsoft.com/library/ms156500.aspx

http://technet.microsoft.com/library/ms159110.aspx

• System information, including operating system, version, number of processors, and memory.
• Reporting Services component and version information.
• Events logged the Application log.
• Exceptions generated by the report server.
• Low resource warnings logged by a report server.
• Inbound SOAP envelopes and summarized outbound SOAP envelopes.
• HTTP header, stack trace, and debug trace information

Use the Report Log Viewer tool to get more information on the reporting service trace log and reporting service execution log …

Download the Report Log Viewer Tool @ http://www.microsoft.com/en-us/download/details.aspx?id=24774

Run the executable ReportViewer.exe from C:\Program Files (x86)\Microsoft\Reporting Services folder and select the log files location (C:\Program Files\Microsoft SQL Server\MSRS11.<instance name>\Reporting Services\LogFiles) and select one of following 3 views to analyze the data.

Trace Log Histogram – Shows the histogram view of event and number of times it occured. This view should help us pinpoint bottleneck areas if we look for spikes in certain events
Raw – Provides more information on bottleneck events because it has the “Time” component built-in
Threads – Find resource contention thru threads to get to know where the waits occur

Default timeout for reporting server webservice is 100000 milliseconds (1.666666667 mins) – link

Calling Reporting webservice from c# code to generate the reports is timing out due to long running reports. Resetting timeout period to high value is a quick solution before fixing  report performance issue.

http://msdn.microsoft.com/en-us/library/reportexecution2005.reportexecutionservice%28v=sql.105%29.aspx

ERROR: The number of requests for XXXServer\XXXUser has exceeded the maximum number allowed for a single user

The reason for this error is the default value  for MaxActiveReqForOneUser key in RSREPORTSERVER.config file is 20 which need to be changed  to 0 (unlimited access) or increased to some higher value. After changing this setting IIS need to be reset in the reporting server machine.

Reportserver.config file exist in the following path (path may be little different based on the sql server reporting server version that is installed).

C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer

Reference:

http://www.sqlservercentral.com/Forums/Topic410741-162-1.aspx#bm507713

http://blogs.msdn.com/b/selvar/archive/2007/12/13/error-the-number-of-requests-for-xxxserver-xxxuser-has-exceeded-the-maximum-number-allowed-for-a-single-user.aspx