So the problem was that we had a CreateTransaction call around an AND TransactionScope call. So we had 2 transactions. I did not think that this would cause this type of problem until I realized that when the error occurred, we would get two ROLLBACK calls. The second one will cause the aforementioned error message and actually hide the first. We found this by running SQLProfiler looking for "user error messages"
source
share