I am having this problem as well. The guy in this blog post: http://www.jaxidian.org/update/2007/04/06/7/
says the problem is a bug in ADO.Net, and he was able to fix it with the MyGenration team's help by,
\"... keep[ing] an external reference to the connection that is outside the transaction object. So in our case, with the help of the MyGenerations developers, we modified the MyGenerations code to do this and our problem is gone, at last! So expect an update to their software very soon to work around this .NET bug. And if you hit this problem with your own code, now you know how to fix it.\"
Looking at MyGeneration's release dates, and the fact that I have the latest version, I don't think this fix was ever applied.
What should I change in MyGeneration specifically? I know I need to create a refrence to the connection object, but I'm not sure where the best place to do that is.