|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 958090 - Last Review: February 23, 2009 - Revision: 1.0 FIX: The System.EnterpriseServices.TransactionProxyException exception cannot be caught from other application domains when it is triggered during a transaction completionWhen 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.
This problem occurs because the TransactionProxyException exception is not serialized, and then cannot be caught from another application domain. Hotfix informationA 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: 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 requirementYou do not have to restart the computer after you apply this hotfix. Hotfix replacement informationThis 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 versionCollapse this tableExpand this table | File name | File version | File size | Date | Time | Platform |
|---|
| System.enterpriseservices.dll | 2.0.50727.1857 | 258,048 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.dll | 2.0.50727.1857 | 40,960 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.thunk.dll | 2.0.50727.1857 | 55,160 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.wrapper.dll | 2.0.50727.1857 | 113,664 | 12-Dec-2008 | 04:47 | x86 |
The .NET Framework 2.0, x64 versionCollapse this tableExpand this table | File name | File version | File size | Date | Time | Platform |
|---|
| System.enterpriseservices.dll | 2.0.50727.1857 | 33,280 | 11-Dec-2008 | 20:11 | x64 | | System.enterpriseservices.dll | 2.0.50727.1857 | 258,048 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.dll | 2.0.50727.1857 | 40,960 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.dll | 2.0.50727.1857 | 245,760 | 14-Dec-2008 | 20:37 | x64 | | System.enterpriseservices.thunk.dll | 2.0.50727.1857 | 55,160 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.thunk.dll | 2.0.50727.1857 | 61,304 | 14-Dec-2008 | 20:37 | x64 | | System.enterpriseservices.wrapper.dll | 2.0.50727.1857 | 133,120 | 11-Dec-2008 | 19:44 | x64 | | System.enterpriseservices.wrapper.dll | 2.0.50727.1857 | 113,664 | 12-Dec-2008 | 04:47 | x86 |
The .NET Framework 2.0, Itanium-based versionCollapse this tableExpand this table | File name | File version | File size | Date | Time | Platform |
|---|
| System.enterpriseservices.dll | 2.0.50727.1857 | 33,280 | 11-Dec-2008 | 20:55 | IA-64 | | System.enterpriseservices.dll | 2.0.50727.1857 | 258,048 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.dll | 2.0.50727.1857 | 40,960 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.dll | 2.0.50727.1857 | 245,760 | 14-Dec-2008 | 21:00 | IA-64 | | System.enterpriseservices.thunk.dll | 2.0.50727.1857 | 55,160 | 12-Dec-2008 | 04:47 | x86 | | System.enterpriseservices.thunk.dll | 2.0.50727.1857 | 121,208 | 14-Dec-2008 | 21:00 | IA-64 | | System.enterpriseservices.wrapper.dll | 2.0.50727.1857 | 175,616 | 11-Dec-2008 | 20:18 | IA-64 | | System.enterpriseservices.wrapper.dll | 2.0.50727.1857 | 113,664 | 12-Dec-2008 | 04:47 | x86 |
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Stack trace when the SerializationException exception occursat 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)
APPLIES TO- Microsoft .NET Framework 2.0 Service Pack 1 (x86)
| kbhotfixserver kbexpertiseadvanced kbqfe kbsurveynew KB958090 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
 |
 |
 |
 |
 |
 |
 |
| |