asp.net serialization issue on testing server

Question

I have been working on a project and it works fine on my development machine. When I move it to the stage server for testing I get the following error:

Unable to serialize the session state. In 'StateServer' and 'SQLServer'

The error message goes on to specify one of my business objects as the issue. The code was actually developed by another developer but I believe the issue is when a business object is saved into the session.

Why would that work on my local machine but not on the remote server?

Are u sure web.config is absolutely equal on both machines? if you use a state server all objects in the session MUST be serializable. — Davide Piras
– Davide Piras, Commented Oct 18, 2011 at 19:24
They are definitely not equal. Not even close. Is there a particular thing I should be looking for? — William
– William, Commented Oct 18, 2011 at 19:35
yes the session configuration. you should make sure all objects you put in the session are serializable or it wont work. — Davide Piras
– Davide Piras, Commented Oct 18, 2011 at 19:46
Is the object that you're serializing marked Serializable? — James Johnson
– James Johnson, Commented Oct 18, 2011 at 19:49

Wiktor Zychla · Accepted Answer · 2011-10-18 19:28:47Z

2

You development machine probably uses the InProc session provider which serializes onto memory. When the SQLServer session provider is used, there are are much stronger requirements on your objects.

Most probably - one of your objects is just not serializable. Reasons could vary, from simple "not marked as serializable" to "relying on external types which are not serializable".

Try to track down the problematic type by inspecting the inner exception. Usually you'll find a meaning information there.

answered Oct 18, 2011 at 19:28

Wiktor Zychla

48.5k6 gold badges83 silver badges114 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

William Over a year ago

Is there a way I can check to see if the InProc is being used? Unfortunately the server is a client machine so I don't have much control over it. I did find another article that gave some code I can use to test if my object is serializable so I'll be testing that when I get a chance.

Wiktor Zychla Over a year ago

The sessionState element of the web.config controls the way your data is persisted in the session container. Apparently it's configured to InProc or SqlServer on your client's machine. Ask him to change it to InProc temporarily to make sure that the problem is there and take some time to fix your objects so that they could be serialized. msdn.microsoft.com/en-us/library/h6bb9cz9(VS.71).aspx

William Over a year ago

I don't have a sessionState tag in my local web config. What would the default be?

Wiktor Zychla Over a year ago

The default is InProc, that's why the application works for you locally. The client could have probably changed this setting in his local web.config, server-level web.config or machineHost.config.

Nikki9696 Over a year ago

It would inherit from machine.config if no web config overrode it.

|

Collectives™ on Stack Overflow

asp.net serialization issue on testing server

1 Answer 1

6 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

6 Comments

Your Answer

Sign up or log in

Post as a guest

Related