Problem : The current transaction cannot be committed and cannot support operations that write to the log file.
Msg 3930, Level 16, State 1, Line 49
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
what does this mean?
Solution : The current transaction cannot be committed and cannot support operations that write to the log file.
SQL Server 2005 has a transaction state: doomed. The doomed transaction is similar to a read-only transaction. You can continue to perform reads after a doomed transaction, but when you commit, write to the transaction log, it will fail with 3930.
Do you rollback any failed transactions before you commit?
