On a test environment, we had this exception on one of the two BizTalk Server 2004 SP1 nodes:
Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks
This was a BizTalk Server 2004 event in Application event log
On the other node, they were .NET Framework 2.0 and BizTalk events (meaning that some code was not correctly written from a multithreading perspective).
In fact, what happened was that BizTalk Server 2004 was running on top of .NET Framework 2.0 on one node and on top of .NET Framework 1.1 on the other node. So, an orchestration dehydrating on none node and rehydrating on the other node was just serialized with a Framework and deserialized with another Framework.
Here are two KB articles related to that:
Excerpt from KB841405:
To run BizTalk Server 2004 on a computer that also has the .NET Framework 2.0 installed, upgrade the computer that is running BizTalk Server 2004 to BizTalk Server 2004 SP2. BizTalk Server 2004 is only supported on a computer that has the .NET Framework 2.0 installed if BizTalk Server 2004 SP2 is also installed.