FIX: The System.EnterpriseServices.TransactionProxyException exception cannot be caught from other application domains when it is triggered during a transaction completion

Article translations Article translations
Article ID: 958090 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

When a System.EnterpriseServices.TransactionProxyException exception is triggered during a transaction completion, it cannot be caught from other application domains. Instead, you receive a System.Runtime.Serialization.SerializationException exception that resembles the following:
Unhandled Exception: System.Runtime.Serialization.SerializationException: Type 'System.EnterpriseSer vices.TransactionProxyException' in Assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=ne utral, PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable.

Cause

This problem occurs because the TransactionProxyException exception is not serialized, and then cannot be caught from another application domain.

Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

After you install the hotfix, the TransactionProxyException exception can be caught from the same domain as follows.
System.EnterpriseServices.TransactionProxyException (0x8000FFFF): 
Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown. 
---> System.Transactions.TransactionException: The operation is not valid for the state of the transaction. 
---> System.TimeoutException: Transaction Timeout.

Prerequisites

You must have the Microsoft .NET Framework 2.0 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
The .NET Framework 2.0, x86 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.enterpriseservices.dll2.0.50727.1857258,04812-Dec-200804:47x86
System.enterpriseservices.dll2.0.50727.185740,96012-Dec-200804:47x86
System.enterpriseservices.thunk.dll2.0.50727.185755,16012-Dec-200804:47x86
System.enterpriseservices.wrapper.dll2.0.50727.1857113,66412-Dec-200804:47x86
The .NET Framework 2.0, x64 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.enterpriseservices.dll2.0.50727.185733,28011-Dec-200820:11x64
System.enterpriseservices.dll2.0.50727.1857258,04812-Dec-200804:47x86
System.enterpriseservices.dll2.0.50727.185740,96012-Dec-200804:47x86
System.enterpriseservices.dll2.0.50727.1857245,76014-Dec-200820:37x64
System.enterpriseservices.thunk.dll2.0.50727.185755,16012-Dec-200804:47x86
System.enterpriseservices.thunk.dll2.0.50727.185761,30414-Dec-200820:37x64
System.enterpriseservices.wrapper.dll2.0.50727.1857133,12011-Dec-200819:44x64
System.enterpriseservices.wrapper.dll2.0.50727.1857113,66412-Dec-200804:47x86
The .NET Framework 2.0, Itanium-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.enterpriseservices.dll2.0.50727.185733,28011-Dec-200820:55IA-64
System.enterpriseservices.dll2.0.50727.1857258,04812-Dec-200804:47x86
System.enterpriseservices.dll2.0.50727.185740,96012-Dec-200804:47x86
System.enterpriseservices.dll2.0.50727.1857245,76014-Dec-200821:00IA-64
System.enterpriseservices.thunk.dll2.0.50727.185755,16012-Dec-200804:47x86
System.enterpriseservices.thunk.dll2.0.50727.1857121,20814-Dec-200821:00IA-64
System.enterpriseservices.wrapper.dll2.0.50727.1857175,61611-Dec-200820:18IA-64
System.enterpriseservices.wrapper.dll2.0.50727.1857113,66412-Dec-200804:47x86

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information

Stack trace when the SerializationException exception occurs

at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurr
ogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFor
matterConverter converter, ObjectWriter objectWriter)
   at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogat
eSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatt
erConverter converter, ObjectWriter objectWriter)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] i
nHeaders, __BinaryWriter serWriter, Boolean fCheck)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationS
tream, Object graph, Header[] headers, Boolean fCheck)
   at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeMessageParts(ArrayList args
ToSerialize)
   at System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage..ctor(IMethodReturnMessage mrm)
   at System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage.SmuggleIfPossible(IMessage msg)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMeth
odCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatchCallback(Object[] args
)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg
)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

Stack trace when the TransactionProxyException exception occurs

   at System.Transactions.TransactionState.Promote(InternalTransaction tx)
   at System.Transactions.Transaction.Promote()
   at System.Transactions.TransactionInterop.ConvertToOletxTransaction(Transaction transaction)
   at System.Transactions.TransactionInterop.GetDtcTransaction(Transaction transaction)
   at System.EnterpriseServices.TransactionProxy.Promote()
   at System.EnterpriseServices.TransactionProxyException.ThrowTransactionProxyException(Int32 hr, T
ransactionException exception)
   at System.EnterpriseServices.TransactionProxy.MapTxExceptionToHR(TransactionException txException
, Boolean isInCommit)
   at System.EnterpriseServices.TransactionProxy.Promote()
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

Properties

Article ID: 958090 - Last Review: June 21, 2014 - Revision: 2.0
Applies to
  • Microsoft .NET Framework 2.0 Service Pack 1 (x86)
Keywords: 
kbHotfixServer kbexpertiseadvanced kbqfe kbsurveynew KB958090

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com