You can disable auto-enlistment in existing transactions by specifying Enlist=false as a connection string parameter for a SqlConnection, e.g.
Data Source=localhost;Integrated Security=SSPI;Initial Catalog=Northwind;Enlist=false From: http://msdn.microsoft.com/library/en-us/cpguide/html/cpconenlistingindis tributedtransaction.asp > -----Original Message----- > From: Ron Grabowski [mailto:[EMAIL PROTECTED] > Sent: 07 December 2005 22:21 > To: Log4NET User > Subject: RE: log4net and Microsoft Transactions > > A 587k .bmp attachment?! Yikes that's big. If it were a .png > it probably be less than 10k. Anyway, you may find this thread useful: > > http://tinyurl.com/ceu7m > http://www.mail-archive.com/log4net-user%40logging.apache.org/ > msg02238.html > > It looks like Michael Collier had a similiar issue and was > able to solve it by making FastDbAppender: > > http://tinyurl.com/9f6wn > http://svn.apache.org/viewcvs.cgi/logging/log4net/trunk/exampl > es/net/1.0/Appenders/SampleAppendersApp/cs/src/Appender/FastDb > Appender.cs?view=markup > > extend ServicedComponent and marking the class with the > [Transaction(TransactionOption.NotSupported)] attribute. > > - Ron > > --- Ramaa Davanagere <[EMAIL PROTECTED]> wrote: > > > > > > > We are using MTS transactions. I will try my best to elaborate the > > problem. > > > > > > > > Please open the bmp file before reading. This bmp file > shows how the > > process flows in our product. > > > > > > > > The user will login via the login page and goes to the Main > ASP Page. > > > > > > > > > > Components A, B, C and D are VB COM components and are > listed in COM+ > > applications. The transaction for Component A is set to "Required" > > and the > > transactions for B, C and D are set to "supported" > > > > > > > > Component E is the common tracing COM component that acts > as a bridge > > between vb com components (B,C, D) and the c# error handler > (component > > F) that uses log4net. > > > > > > > > Component F is c#.net component which uses log4net and > writes messages > > to the log file (messages.txt). I have generated a type library of > > this component so that it can be used as a interop in Component E. > > > > > > > > All is working well (actually Prefect) when the transaction > is changed > > to "supported" for component A. But if it's set to > "Required", I see > > the following errors in the log file. > > > > > > > > 2147168246: New transaction cannot enlist in the specified > transaction > > coordinator. > > > > > > > > Please let me know if you need more details > > > > > > > > I desperately need help. > > > > > > > > > > > > -----Original Message----- > > From: Georg Jansen [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, December 07, 2005 10:31 AM > > To: 'Log4NET User' > > Subject: RE: log4net and Microsoft Transactions > > > > > > > > Ramma, > > > > > > > > What kind of transaction, database transactions or mts > transactions or > > .....? > > > > Could you pls. elaborate? > > > > > > > > Best regards > > > > Georg > > > > http://www.l4ndash.com <http://www.l4ndash.com/> - Log4Net > Dashboard > > / Log Viewer > > > > > > > > > > > > > > > > _____ > > > > From: Ramaa Davanagere [mailto:[EMAIL PROTECTED] > > Sent: 7. desember 2005 15:39 > > To: 'Log4NET User' > > Subject: log4net and Microsoft Transactions > > > > > > > > Has anybody had any problem in log4net with Microsoft transactions? > > > > > > > > > >
