Episerver specialized property error

ramesh@ares.com.au

Vote:

Hi, I am getting the following error on my search results page.

Type 'EPiServer.SpecializedProperties.PropertyXhtmlString+UrlString' in Assembly 'EPiServer, Version=5.1.422.4, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' is not marked as serializable.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.Serialization.SerializationException: Type 'EPiServer.SpecializedProperties.PropertyXhtmlString+UrlString' in Assembly 'EPiServer, Version=5.1.422.4, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' is not marked as serializable.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SerializationException: Type 'EPiServer.SpecializedProperties.PropertyXhtmlString+UrlString' in Assembly 'EPiServer, Version=5.1.422.4, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' is not marked as serializable.]    System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType type) +2700482    System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context) +245    System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo() +88    System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) +175    System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) +50    System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck) +438    System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck) +131    System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph) +13    System.Web.UI.ObjectStateFormatter.SerializeValue(SerializerBinaryWriter writer, Object value) +3010  [ArgumentException: Error serializing value 'EPiServer.Core.PageDataCollection' of type 'EPiServer.Core.PageDataCollection.']    System.Web.UI.ObjectStateFormatter.SerializeValue(SerializerBinaryWriter writer, Object value) +3217    System.Web.UI.ObjectStateFormatter.Serialize(Stream outputStream, Object stateGraph) +126    System.Web.UI.ObjectStateFormatter.Serialize(Object stateGraph) +52    System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Serialize(Object state) +4    System.Web.UI.Util.SerializeWithAssert(IStateFormatter formatter, Object stateGraph) +37    System.Web.UI.HiddenFieldPageStatePersister.Save() +106    System.Web.UI.Page.SavePageStateToPersistenceMedium(Object state) +82    System.Web.UI.Page.SaveAllState() +550    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2357

I am using episerver index searching. I cannot figure out what the problem. Can anyone shed some light on this.

Thank you.
Ramesh

#19587

Apr 21, 2008 3:37

Tobias Nilsson

Vote:

This is a known bug in our system:

Bug 50566: String fragments are not serializable which may cause failure on serialization of PageData objects

It has been fixed in CMS 6 R2 release.

#49297

Mar 11, 2011 15:05

Linus Ekström

Vote:

Hi!

The exception message seems to deal with EPiServer CMS 5 so it's probably not the bug Tobias assumed. The exception states that there are built in properties that are not serializable. I don't know if this is the case but perhaps you could solve this by not serializing an entire PageData-object. Perhaps store a PageReference instead?

Regards
Linus Ekström

#49298

Mar 11, 2011 15:57