I am writing this post to save users of this software hours and hours of frustration, company costs, and headaches.
We just discovered that our Q1 2008 SP1 version of Telerik Reporting fails to work with StateServer. We didn't see this mentioned anywhere in the docs or on this slick web site's demo or feature pages. But perhaps maybe we missed it since we've been working overtime for the past 10 1/2 hours trying to resolve this problem---and have consequently blown a project deadline for our most important client while goofing around with this software's problem.
We, and many other ASP.NET developers, do not use InProc for state management for many reasons -- the most common being that it is unreliable for ASP.NET state management and constantly recycles, which of course destroys session data. This is particuraly true when deploying to a shared host, where server antivirus software can cause InProc to go haywire and wreck session state every few minutes.
Here's the kicker: If you set your web.config to indicate 'StateServer', then Telerik reporting will fail to pass a parameter to the report! In other words, using StateServer (and probably SQLServer as well) will cause the following line of code to fail completely:
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
Dim query As String
query = CStr(Request.QueryString("MyKey"))
Me.ReportViewer1.Report.ReportParameters("MyParam").Value = query
End Sub
There is no error message. No warning. Nothing. Rather, Telerik Reporting simply doesn't conduct the parameter filter and that's that.
We searched extensively (had plenty of time during our 10 1/2 hours lost productivity) on the internet for information. Buried inside a community post on this very web site was an excerpt dated 8/1/2008:
"Report parameters are really not shown when using a state server or sql server modes. This is an issue which will be fixed for the upcoming service pack in a couple of weeks. Your points have been updated for letting us know about the problem." Greetings, Chavdar.
Today is Sept 20, 2008. It's been over 1 1/2 months. Has this been updated or not? If so, how can we get our version working?
I would formally request:
1.) A service pack fix immediately at no cost to our company.
or
2.) A refund for our Telerik reporting purchase if this issue cannot be immediately and at no cost to us be resolved with an updated software version that you currently have.
Our tech feedback provided here (at no cost to your company by the way) should serve to get you started on research and publication into this issue in hopes of saving future users massive problems when dealing with other methods of state management and using the reporting tool.
Another gem: a standard doctype declaration in web pages breaks the UI viewer in the Firefox web browser, which is used by, um, over 33% of our visitors. What is happening with that?
We paid $600.00 for this software and are very unhappy with how buggy and unreliable it appears to be. We are now forced to research into other vendors ASAP for our corporation and may terminate our use of Telerik products later this month if this issue is not resolved or a refund granted. We are not asking for our lost company time, costs for employee's overtime in trying to resolve this bug, although we should have.
To say that we are very unhappy with Telerik's products at the moment is an understatement.
Kind regards,
Chris
the customer using your product
We just discovered that our Q1 2008 SP1 version of Telerik Reporting fails to work with StateServer. We didn't see this mentioned anywhere in the docs or on this slick web site's demo or feature pages. But perhaps maybe we missed it since we've been working overtime for the past 10 1/2 hours trying to resolve this problem---and have consequently blown a project deadline for our most important client while goofing around with this software's problem.
We, and many other ASP.NET developers, do not use InProc for state management for many reasons -- the most common being that it is unreliable for ASP.NET state management and constantly recycles, which of course destroys session data. This is particuraly true when deploying to a shared host, where server antivirus software can cause InProc to go haywire and wreck session state every few minutes.
Here's the kicker: If you set your web.config to indicate 'StateServer', then Telerik reporting will fail to pass a parameter to the report! In other words, using StateServer (and probably SQLServer as well) will cause the following line of code to fail completely:
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
Dim query As String
query = CStr(Request.QueryString("MyKey"))
Me.ReportViewer1.Report.ReportParameters("MyParam").Value = query
End Sub
There is no error message. No warning. Nothing. Rather, Telerik Reporting simply doesn't conduct the parameter filter and that's that.
We searched extensively (had plenty of time during our 10 1/2 hours lost productivity) on the internet for information. Buried inside a community post on this very web site was an excerpt dated 8/1/2008:
"Report parameters are really not shown when using a state server or sql server modes. This is an issue which will be fixed for the upcoming service pack in a couple of weeks. Your points have been updated for letting us know about the problem." Greetings, Chavdar.
Today is Sept 20, 2008. It's been over 1 1/2 months. Has this been updated or not? If so, how can we get our version working?
I would formally request:
1.) A service pack fix immediately at no cost to our company.
or
2.) A refund for our Telerik reporting purchase if this issue cannot be immediately and at no cost to us be resolved with an updated software version that you currently have.
Our tech feedback provided here (at no cost to your company by the way) should serve to get you started on research and publication into this issue in hopes of saving future users massive problems when dealing with other methods of state management and using the reporting tool.
Another gem: a standard doctype declaration in web pages breaks the UI viewer in the Firefox web browser, which is used by, um, over 33% of our visitors. What is happening with that?
We paid $600.00 for this software and are very unhappy with how buggy and unreliable it appears to be. We are now forced to research into other vendors ASAP for our corporation and may terminate our use of Telerik products later this month if this issue is not resolved or a refund granted. We are not asking for our lost company time, costs for employee's overtime in trying to resolve this bug, although we should have.
To say that we are very unhappy with Telerik's products at the moment is an understatement.
Kind regards,
Chris
the customer using your product