# Error occurred while loading tag information, Transaction (Process ID 95) was deadlocked on lock resources **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [May 21, 2024, 4:48am UTC](https://forum.inductiveautomation.com/t/error-occurred-while-loading-tag-information-transaction-process-id-95-was-deadlocked-on-lock-resources/90652 "2024-05-21T04:48:24Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Lina\_Su](https://avatars.discourse-cdn.com/v4/letter/l/7ba0ec/32.png) [@Lina\_Su](https://forum.inductiveautomation.com/u/Lina_Su)\ **Post date:** [May 21, 2024, 4:48am UTC](https://forum.inductiveautomation.com/t/error-occurred-while-loading-tag-information-transaction-process-id-95-was-deadlocked-on-lock-resources/90652/1 "2024-05-21T04:48:24Z")
Hi , I got below errors in my logs, keeps updating. There are Id and Process ID , from this two IDs, how I can find out which tag is locked and by whom. Can anyone give some guidance , thanks. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/5/9591317d1392788a03849561cb2654359475db37.png) com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 95) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:265) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 21, 2024, 11:48am UTC](https://forum.inductiveautomation.com/t/error-occurred-while-loading-tag-information-transaction-process-id-95-was-deadlocked-on-lock-resources/90652/2 "2024-05-21T11:48:54Z")
You should investigate this from the database side. Most likely, there are two different stored procedures making table or other locks, and they are not following the same **order** of locks. This presents opportunities for "AB-BA" deadlocks. You will need to look at SQL Server's own logs to identify the sources.