-----------------------------------------------------------------------------------------------------------

Hi Paul,

We have used your ORMapper with transactions in a application. It works perfectly.

 At this moment we use your ORMapper with system.transaction.transactionscope, via a webservice, using connection pooling.

To use it with a webservice, we stored the object space in the http context current items collection, like your example. 

We have problems with the transactions. Two errors occur:

"The commit transaction request has no corresponding begin transaction. (Microsoft OLE DB Provider for SQL server)"

"The transaction has aborted"

After an error the webservice gives an error for a few minutes.

"New request is not allowed to start because it should come with valid transaction descriptor"  

--------------

for this last error we have installed hotfix KB916002. This reduced the frequency of the error, but didn't eliminate it.

The kb article says the cause is a finishing transaction on an open connection.

Could there be a connection in the ORMapper that stays open?

-------------- 

We get the error on a testing system with limited resources (only 512MB, slow processor).  

We have also tested without the ORMapper with system.transaction.transactionscope, via a webservice, using connection pooling.

This way we couldn't reproduce the errors above. 

We want to use the ORMApper, because it works perfectly before. 

Is there something we could check in relation with the ORMapper? Or could there be another thing causing these errors? 

Any help appreciated, 

With regards,

 Fedor Kauffman / Sander Prost