I've got an OLD classic-asp script that was originally written by a contractor that's giving me fits. It keeps giving me an error that says:Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.
All I did was create a new stored procedure and change an existing call to a stored procedure to point to the new one instead of the old one. The new stored procedure has been trimmed back to be EXACTLY what the old one was except for an additional paramter (which is not used in the current testing state -- the sql that uses it is commented out for the purpose of this test).
In fact, the code get past the new stored procedure and chokes on code that is unchanged. Then, when it chokes, the transaction is rolled back and all of the db changes are gone.
How the heck can I debug this transaction related stuff? There is nothing in the Windows event log. No runtime errors from IIS. Just gets to a certain sql read statement and everthing backs-out and stops.
HELP!?!?