# Errors in wrapper.log

**URL:** <https://forum.inductiveautomation.com/t/errors-in-wrapper-log/15666>\
**Category:** Ignition\
**Created:** [October 14, 2017, 1:06pm UTC](https://forum.inductiveautomation.com/t/errors-in-wrapper-log/15666 "2017-10-14T13:06:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [October 14, 2017, 1:06pm UTC](https://forum.inductiveautomation.com/t/errors-in-wrapper-log/15666/1 "2017-10-14T13:06:44Z")

</div>

Reading through the wrapper.log on one of my installations I find some recurrent errors like:

```auto
INFO | jvm 1 | 2017/10/13 23:37:30 | ERROR [QueryExecutor[KDV] ] [23:37:30,108]: (id=2538b600) Error occurred while loading tag information.
INFO | jvm 1 | 2017/10/13 23:37:30 | com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 59) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

```

and

```auto
INFO | jvm 1 | 2017/10/11 22:31:19 | ERROR [Journal[Journal] ] [22:31:19,052]: Error logging alarm event to the database.
INFO | jvm 1 | 2017/10/11 22:31:19 | java.lang.Exception: Unable to add data to memory buffer, buffer full.

```

Any suggestion? I’m running Ignition 7.8.4, MS Sql Server 2014, Kepware OPC UA Server on some Siemens S7-1500 PLCs.

Thanks in advance,  
regards

---

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [October 16, 2017, 12:13am UTC](https://forum.inductiveautomation.com/t/errors-in-wrapper-log/15666/2 "2017-10-16T00:13:14Z")

</div>

> [@pgmo](#):
>
> com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 59) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Here is a StackOverflow thread that can hopefully give you some insight regarding the SQLServerException:

> <https://stackoverflow.com/questions/5389261/sql-transaction-was-deadlocked>

By the way, the free WrapperLogViewer project might be useful to you. It enables you to see the wrapper.log file from an Ignition client. More info here:  
[http://nickmudge.info/post/view-the-ignition-wrapper.log-file-in-the-designer-or-client](http://nickmudge.info/post/view-the-ignition-wrapper.log-file-in-the-designer-or-client)