Please send us email at firstname.lastname@example.org We would very much like to get to the bottom of this problem. In particular, if it is possible, we would like you to send us a reproducible case.
The error message you are getting indicates that you are trying to commit a transaction after it has already failed. This message is not from DevForce since it has been reported elsewhere. The few reports that I have seen on this problem on the Internet indicate that if you do turn off transactions, the symptoms do disappear, but this workaround is super dangerous because it means you are no longer performing transactional saves.
Here are some additional questions:
When did you first started seeig this problem?
Did it happen after changing to a new version of DevForce?
Are you calling SaveChanges from server-side code or client-side code?
Are you mixing transactional and non-transactional code?
Are you using SQL Server Identity columns?
Are you using Stored Procedures and/or Triggers?
Do you have a Stack Trace?
What sort of data provider are you using?
Do you have a DebugLog.XML file?
Do you have a log from the database?
Edited by davidklitzke - 23-Sep-2007 at 10:12pm