# Best way to troubleshoot transaction error? **URL:** \ **Category:** Ignition\ **Created:** [August 1, 2014, 7:27pm UTC](https://forum.inductiveautomation.com/t/best-way-to-troubleshoot-transaction-error/8843 "2014-08-01T19:27:59Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\ **Post date:** [August 1, 2014, 7:27pm UTC](https://forum.inductiveautomation.com/t/best-way-to-troubleshoot-transaction-error/8843/1 "2014-08-01T19:27:59Z")
Keep getting this in my logs, not sure how to go about finding where it is coming from. We dont have any scripts that run fast enough to log an error every 5-6 seconds and our transaction groups that do run faster than 5-6 seconds seem to be running fine. I even disabled the transaction groups to see if it would stop but it didnt. also disabled and enabled the database connection but that didnt make a difference either. > [@](#): > > ``` > Time Logger Message > > ``` > > [WARN] 2:23:54 PM TxTimoutDaemon Transaction "98925f09-bb75-412b-a016-7a3f86b4a958" threw an error while being closed. > > com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. > > more > [WARN] 2:23:54 PM TxTimoutDaemon Transaction "98925f09-bb75-412b-a016-7a3f86b4a958" being closed due to inactivity timeout. Make sure you close your transactions. > [WARN] 2:23:54 PM TxTimoutDaemon Transaction "5f312706-9947-4958-a334-a3ab4fccde59" threw an error while being closed. > > com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. > > more > [WARN] 2:23:54 PM TxTimoutDaemon Transaction "5f312706-9947-4958-a334-a3ab4fccde59" being closed due to inactivity timeout. Make sure you close your transactions. > [WARN] 2:23:48 PM TxTimoutDaemon Transaction "98925f09-bb75-412b-a016-7a3f86b4a958" threw an error while being closed. > > com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [August 7, 2014, 4:21pm UTC](https://forum.inductiveautomation.com/t/best-way-to-troubleshoot-transaction-error/8843/2 "2014-08-07T16:21:07Z")
Hi, What version are you currently running? I vaguely remember a possible issue with transactions not being cleaned up correctly. If you see the same transaction ids reported multiple times, that must be what’s going on, instead of real errors occurring. To explain it differently, this started off with a transaction in scripting. The transaction perhaps wasn’t closed, and there’s a daemon that monitors those, and closes them after a period of time. However, I _think_ there was a bug (which I can go try to confirm), where that system would keep trying to shut down the same bad transactions over and over. Regards, ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [August 7, 2014, 4:22pm UTC](https://forum.inductiveautomation.com/t/best-way-to-troubleshoot-transaction-error/8843/3 "2014-08-07T16:22:46Z")
The bug I had in mind was fixed in 7.6.6, and could cause something like this. Regards, ---
**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\ **Post date:** [August 7, 2014, 5:17pm UTC](https://forum.inductiveautomation.com/t/best-way-to-troubleshoot-transaction-error/8843/4 "2014-08-07T17:17:26Z")
Colby, we are running: Ignition Platform 7.5.11 (b1526) Would this issue go back to 7.5? It sounds similar to what you are talking about because we just dont have anything that I can find or remember that is running fast enough to log at the rate the error is being logged. ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [August 7, 2014, 5:54pm UTC](https://forum.inductiveautomation.com/t/best-way-to-troubleshoot-transaction-error/8843/5 "2014-08-07T17:54:24Z")
Yes, looks like 7.5 could have the same problem. We can back port the fix, I think 7.5.13 will be released within a few weeks. You can try the following right now to stop the messages: Try going to the script playground in the designer and run ```auto system.db.closeTransaction("98925f09-bb75-412b-a016-7a3f86b4a958") ``` Do that for the ids being reported for the errors. You shouldn’t get any more messages for that id afterwards. Regards, ---
**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\ **Post date:** [August 7, 2014, 6:33pm UTC](https://forum.inductiveautomation.com/t/best-way-to-troubleshoot-transaction-error/8843/6 "2014-08-07T18:33:18Z")
Looks like it worked. Thanks for your help.