Hi ALL,

We are having multiple DNN portals running under seperate worker processes. So we have the need to use state server for sessions. We are facing a problem when trying to store a DNN object(s) in session. Apparently, the DNN object in question is not made serializable and hence ASP.Net throws an error saying "Unabe to serialize the session". So the first question is , does DNN support/recommend session state server? The second question is : What is strange is , this works with DNN 4.8.0 . It does allow to store the dnn objects in state server. But when we try it in 4.8.2 it fails. We are clueless as to how that could it be? Any suggestions how to get them working? Our major problem is because of this one problem we are unable to move forward to upgrade to rcent versions of DNN , which we would like to do very much earliest possible.

Please post any suggestions/alternate solutions as this has been a impending problem since long , thanks in advance

Shankar

Thanks for the quick reply. I understand whatever you said on serialisation, however what is perplexing to me is why is it that the core dnn objects are serialisable in 4.8.0 version , although they have not been made serialisable explicitly (looking at the source code)? Obviously i am missing something here. Do you have any suggestions for that? Thanks again for the direction.

Yes , Userinfo is one of them. As i mentioned, If you look at the source of this object , it does not appear to be serialised , but it still does not throw any error when it is being serialised. But the moment i upgrade the DNN version to 4.8.2 it starts throwing the error , Unable to serialise.