Log Rescue timing out when uncommitted transactions exist on server

Category: Troubleshooting & error messages
Date: 05 Jun 2009
Product: SQL Log Rescue
Versions: 1
Platform: Any

When examining the transaction logs, Log Rescue may throw a timeout exception. Once possible cause is that there is an uncommitted transaction currently running against your database. In this case, Log Rescue will continue waiting for the transaction to complete before returning results. If an improperly-formed transaction has begun on the database which never completes, Log Rescue may wait until the timeout period has elapsed before displaying a query timeout exception.

To diagnose the problem, use a SQL Server management tool to determine if there are uncommitted transactions running against the current database.

In SQL Server 2000 Enterprise Manager:
  - Open the server, then Management, then Current Activity
  - Open Processes
  - Sort on the database whose log you are attempting to analyze
  - Check the Open Transactions column for that database

If the count is greater than 0, consider taking steps to kill the process.

Document ID: KB200703000012 Keywords: Log,Rescue, Timeout, Transactions,open

Was this article helpful?

Search support