We have a problem on some of our asp.net pages when the user tries to access the database in the event handler for a button. Sometimes we get the transaction exists from the database usually the first time the user access the dB. We handle the error by showing the exception text to the user. When the user tries again the call to the dB is successfully executed. We don't even start a transaction just doing select against the dB so it's hard to understand the error. All of the pages where we see the problem uses partial updates and has a ScriptHandler (don't know if that's part of the problem). We use .Net 2.0 and Oracle 10g on a Windows server 2003 x64 SP2 and the System.Data.OracleClient.