RunningJobContext.IsClientConnected

I’ve seen a few people get confused over what this error message in the Reporting Services log file indicates. This message is generated when the Reporting Services web server detects that an HTTP request has experienced a remote disconnect.  In practice, this means that we queried the property HttpResponse.IsClientConnected and it returned false. So how…

1

Hiding parameter area when viewing reports

When rendering reports, oftentimes the application would like to minimize as much of the non-report area of the viewer control as possible.  This is easily accomplished when rendering the report through the built-in report viewer control hosted in the ReportServer web site (http://servername/reportserver).  There are two parameters which control the rendering of the viewer control…

1

Hiding Rendering Extensions

This is documented behavior, but we see lots of questions on it.  A good mechanism for preventing users from accidently exporting reports to a format that you don’t want (for example, you might know that the report doesn’t render quite right in a particular format) is to mark the extension as “invisible” in the Report…

1

RS Blogger shout-outs

If you are interested in Reporting Services, you probably already know about these blogs … because frankly they have more interesting things to say than me!  At any rate, just in case they happened to slip through the cracks for you, I thought I would point you towards their blogs: Robert Bruckner – Robert is…

1

Avoid using HttpContext in your reports

On one of our internal mailing lists, someone was asking trying to retrieve some HTTP Headers that their internal application was submitting to the Report Server within the report.  Someone else responded with a code snippet containing the custom code that you can put into an RDL expression to do just that.  This is a…

0