SerializationException

I just upgraded from 5.0 to 5.1 and now whenever I try to open a workbook, Toad crashes. Details below:

“Toad Shutdown

Toad encountered a serious error and must close.

Please save your data and close the application.

We apologize for the inconvenience.

Binary stream ‘0’ does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.”

Any help would be highly appreciated!

Thank you!

This is a really uncommon issue. You can try to remove your application data folder which we are using for storing setting information for Toad.
C:\Users****\AppData\Roaming\Quest Software\Toad Data Point 5.1

Try to remove it and start TDP again.
If you still have an issue please go to this AppData location again and try to send us file 'ExceptionTrace.log'

1 Like

Thanks for the tip, Filip. I am a little confused about the implementation. What do you mean when you say "remove" the application data folder? Where should I move it to? Should I delete it? Cut and paste it to another location?

Thank you for your help!

Hi Filip. I wasn't able to resolve this issue earlier. Just today I updated again to the most recent version of Toad (5.1.2), and I still have this serialization exception error. It is preventing me from opening up a previous workbook project of mine which I need to consult. Do you know what could be causing this or how I can fix it?

Thank you!

Hi, were you able to find AppData directory as I mentioned? This folder is only for custom/temporary data. We are storing there your settings, connections or logs. So if you will remove this folder you won't lost any data or some of your toad files.
You can remove or rename it. Toad will create new folder on start.
If you have some issue with WB. Can you tell me little bit more? What exactly issue do you have? Does it load WB file? Are you storing data with it?

Filip

Hi, Filip, I am getting the same error. I just upgraded from 4.2 to 5.1 this week. The .tsm file (created in 4.2) loads and appears to be trying to connect and then I see the same message that was posted above. Let me know if I should start a new thread, not sure if I should since it's the same subject?
New exception: 6/16/2020 3:25:13 PM
Quest.Toad.Exceptions.DatabaseException: ORA-01005: null password given; logon denied
Stack trace:
at Quest.Toad.Oracle.OracleToadConnection.OpenConnection(IDbConnection connection)
at Quest.Toad.Db.Connection.AllocConnection()
at Quest.Toad.Db.Connection.Connect(Boolean notify)
at Quest.Toad.Db.Provider.BackgroundConnector.CreateBackgroundConnection()
New exception: 6/16/2020 3:25:13 PM
Quest.Toad.Exceptions.DatabaseException: ORA-01005: null password given; logon denied
Stack trace:
at Quest.Toad.Oracle.OracleToadConnection.OpenConnection(IDbConnection connection)
at Quest.Toad.Db.Connection.AllocConnection()
at Quest.Toad.Db.Connection.Connect(Boolean notify)
at Quest.Toad.Db.Provider.BackgroundConnector.CreateBackgroundConnection()
New exception: 6/16/2020 3:25:43 PM
System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.
Stack trace:
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at Quest.FastData.FastSerializeSerialize.Deserialize(BinaryReader inStream)
at Quest.FastData.FastTable.DeserializeRow(BinaryReader reader)
at Quest.FastData.FastTable.RowCollection..ctor(BinaryReader reader, FastTable table, Boolean allowSpool)
at Quest.FastData.FastTable..ctor(Stream stream)
at Quest.Toad.Editor.ToadEditorFormat.<>c__DisplayClass3_1.b__0()
at Quest.Toad.Util.Global.<>c__DisplayClass333_0.b__0()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
New exception: 6/16/2020 3:25:43 PM
System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.
Stack trace:
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at Quest.FastData.FastSerializeSerialize.Deserialize(BinaryReader inStream)
at Quest.FastData.FastTable.DeserializeRow(BinaryReader reader)
at Quest.FastData.FastTable.RowCollection..ctor(BinaryReader reader, FastTable table, Boolean allowSpool)
at Quest.FastData.FastTable..ctor(Stream stream)
at Quest.Toad.Editor.ToadEditorFormat.<>c__DisplayClass3_1.b__0()
at Quest.Toad.Util.Global.<>c__DisplayClass333_0.b__0()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
New exception: 6/16/2020 3:25:43 PM
System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.
Stack trace:
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at Quest.FastData.FastSerializeSerialize.Deserialize(BinaryReader inStream)
at Quest.FastData.FastTable.DeserializeRow(BinaryReader reader)
at Quest.FastData.FastTable.RowCollection..ctor(BinaryReader reader, FastTable table, Boolean allowSpool)
at Quest.FastData.FastTable..ctor(Stream stream)
at Quest.Toad.Editor.ToadEditorFormat.<>c__DisplayClass3_1.b__0()
at Quest.Toad.Util.Global.<>c__DisplayClass333_0.b__0()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Outer exception:
System.ApplicationException: Unhandled exception caused. Process is forced to be aborted.
Stack trace:
New exception: 6/16/2020 3:25:43 PM
System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.
Stack trace:
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at Quest.FastData.FastSerializeSerialize.Deserialize(BinaryReader inStream)
at Quest.FastData.FastTable.DeserializeRow(BinaryReader reader)
at Quest.FastData.FastTable.RowCollection..ctor(BinaryReader reader, FastTable table, Boolean allowSpool)
at Quest.FastData.FastTable..ctor(Stream stream)
at Quest.Toad.Editor.ToadEditorFormat.<>c__DisplayClass3_1.b__0()
at Quest.Toad.Util.Global.<>c__DisplayClass333_0.b__0()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Outer exception:
System.ApplicationException: Unhandled exception caused. Process is forced to be aborted.
Stack trace:
New exception: 6/16/2020 3:25:43 PM
System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.
Stack trace:
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at Quest.FastData.FastSerializeSerialize.Deserialize(BinaryReader inStream)
at Quest.FastData.FastTable.DeserializeRow(BinaryReader reader)
at Quest.FastData.FastTable.RowCollection..ctor(BinaryReader reader, FastTable table, Boolean allowSpool)
at Quest.FastData.FastTable..ctor(Stream stream)
at Quest.Toad.Editor.ToadEditorFormat.<>c__DisplayClass3_1.b__0()
at Quest.Toad.Util.Global.<>c__DisplayClass333_0.b__0()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

I know this is late, but I had a user contact me about this same issue and I found that they have three previous versions of TOAD installed as well. Once I uninstalled all but the most recent version of TOAD, the issue stopped happening.

You may want to check under apps to see which version of TOAD you have installed since it seems updating doesn't automatically remove them.