Error in report generation if I use sessionstate mode="StateServer"

[Vatsal]

Hi,

I have a report and it's sub report in my application. There are two parameters in sub report. I am passing values from my main report to the sub report using these parameters.

The report working fine if I use in-proc as session state, but when I use mode="StateServer" it gives me below error.

"Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode, ASP.NET will serialize the session state objects, and as a result non-serializable objects or MarshalByRef objects are not permitted. The same restriction applies if similar serialization is done by the custom session state store in 'Custom' mode."

Do I need to do any thing extra in telerik report if I use out-proc as session state?

Please help me ASAP.

Thanks,
Vatsal Desai

[Steve]

Hello Vatsal,

There was such a problem in Q2 2010 release that has been fixed in subsequent versions. Please upgrade and if you're still having problems we will need a runnable project which reproduces the issue or the complete stack trace of the exception. If you would like to send us a project you should open a support ticket for this.

One of the possible reasons for the problem is when a class which cannot be serialized binary is used for a data source, so check this first.

All the best,
Steve
the Telerik team

[Vatsal]

Hi,

I have download and test this solution with Q1 2011, but it's not working yet. Then I removed session state mode and start using In-Proc as session state. Now, If I run report from IE, the report viewer showing me message " Internet explore can not display the web page". The main problem is this message does not come in all machine. Only in one machine. The configuration of this machine is:

OS: Windows Vista Home Premium
IE Version: 9.0 ( The same problem was in IE 8.0 also so I updated it to 9.0 just 2 days back )

One point I want to mention here is we are using https secure connection to connect server.

I tried all these options but can't resolve the problem :(

Any help will be appreciated.

Thanks!

[Hrisi]

Hi Vatsal,

Because the problem is observed only on one machine, we need your collaboration to understand what happens. Please try using the Fiddler proxy to collect more information about the problematic report.

Best wishes,
Hrisi
the Telerik team