March 31, 2009 at 2:03 pm
have application generate somtime this two event did you have some idea about this
Exception Error: 3910, Severity: 16, State: 2 .Net SqlClient Data Provider usr 0 249 2009-03-26 14:58:39.707
Exception Error: 8525, Severity: 16, State: 1 .Net SqlClient Data Provider usr 0 249 2009-03-26 14:58:39.707
3910 is Transaction context in use by another session.
8535 is Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction
March 31, 2009 at 2:09 pm
In a .NET application in 2000 you need MSDTC because if your application is using application layer none atomic transaction 2000 is not equiped to resolve these so MSDTC is required. I would need more code to help but the most important is you must run MSDTC.
Kind regards,
Gift Peddie
March 31, 2009 at 2:27 pm
mmm yes MSDTC running into my SQL and IIS server too.
my problemes have not code source of this application and my supplier is not able to reproduce this error occur 4 or 5 time each day
March 31, 2009 at 2:35 pm
3910 is Transaction context in use by another session.
8535 is Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction
This error means some code needs to be cleaned up but if you don't have code your only option is to make changes to your SQL Server code until that error goes away not easy because some one is passing in application layer transactions without writing code to convert to T-SQL atomic transactions.
I can help but I generally ask for code so I can show you what to clean up.
Kind regards,
Gift Peddie
March 31, 2009 at 2:48 pm
tanks a make more presure on my supplier to fix this.
viva the revolution 😉
March 31, 2009 at 3:05 pm
The other option is to upgrade to 2008 Microsoft implemented ANSI SQL Transaction Connection changes in 2008 so that code would actually run without MSDTC and error in 2008.
Kind regards,
Gift Peddie
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply