Message: Type 'umbraco.DataLayer.SqlHelperException' in Assembly 'umbraco.DataLayer, Version=0.3.0.0, Culture=neutral, PublicKeyToken=null' is not marked as serializable.
We just got this error on an Umbraco 4.5.2 installation while/after a Windows Update, which reverted the entire site back to "No Nodes" mode. So this might be a bug that needs investigating, unless it's been taken care of in 4.6 or 4.7.
Exception: System.Runtime.Serialization.SerializationException
Hi,
Any idea what this error is? I kept getting this and I couldn't get the site going.
---------------------------------
An unhandled exception occurred and the process was terminated.
Application ID: DefaultDomain
Process ID: 1620
Exception: System.Runtime.Serialization.SerializationException
Message: Type 'umbraco.DataLayer.SqlHelperException' in Assembly 'umbraco.DataLayer, Version=0.3.0.0, Culture=neutral, PublicKeyToken=null' is not marked as serializable.
StackTrace: at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeObject(Object obj, MemoryStream stm)
at System.AppDomain.Serialize(Object o)
at System.AppDomain.MarshalObject(Object o)
We just got this error on an Umbraco 4.5.2 installation while/after a Windows Update, which reverted the entire site back to "No Nodes" mode. So this might be a bug that needs investigating, unless it's been taken care of in 4.6 or 4.7.
is working on a reply...