# Database, Tag History Error Issues

**URL:** <https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983>\
**Category:** Ignition Early Access\
**Tags:** database\
**Created:** [March 1, 2019, 1:41am UTC](https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983 "2019-03-01T01:41:05Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![roger\_larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/roger_larson/32/8574_2.png) [@roger\_larson](https://forum.inductiveautomation.com/u/roger_larson)\
**Post date:** [March 5, 2019, 5:28pm UTC](https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983/21 "2019-03-05T17:28:38Z")

</div>

So, I ended up solving the problem and was able to revert back to Ignition 8.

As it turns out, the gateway backup from 7.9.10 _does_ bring drivers that _do_ work with Ignition 8.0, even if they are older. The auth .dll file that was posted above from the KBA for the older version also works fine.

The newer versions from the vendor _do not_ work! Any combination of those tended to fail on me.

The problem I actually had was that the Ignition Gateway service in services.msc was re-initialized and the user log-on property that was there had to be refreshed and saved. After that, the service was stopped/started. With the older gateway SQL Server drivers (and same user log-on with Windows Auth), and the related auth .dll file, the databases successfully connected!

Thanks for the help @paul-griffith! Hopefully that helps someone else out in the future.

Cheers,  
Roger

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 5, 2019, 5:29pm UTC](https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983/22 "2019-03-05T17:29:37Z")

</div>

Interesting. What version(s) of SQL Server do you have?

---

<div class="post-metadata">

**Author:** ![roger\_larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/roger_larson/32/8574_2.png) [@roger\_larson](https://forum.inductiveautomation.com/u/roger_larson)\
**Post date:** [March 5, 2019, 5:39pm UTC](https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983/23 "2019-03-05T17:39:06Z")

</div>

Looks like it is this (via: SELECT @@version;):

```auto
Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64)   
Mar 18 2018 09:11:49   
Copyright (c) Microsoft Corporation  
Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) 

```

---

<div class="post-metadata">

**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:** [March 5, 2019, 5:43pm UTC](https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983/24 "2019-03-05T17:43:38Z")

</div>

You guys are dealing with bigger issues, but I just wanted to mention that errors storing data flooding the logs was fixed on 3/2. Any errors on history storage are logged on debug, and will soon be exposed through tag diagnostics.

---

<div class="post-metadata">

**Author:** ![ASF](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@ASF](https://forum.inductiveautomation.com/u/ASF)\
**Post date:** [March 6, 2019, 1:27am UTC](https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983/25 "2019-03-06T01:27:18Z")

</div>

> [@roger\_larson](#):
>
> The auth .dll file that was posted above from the KBA for the older version also works fine.
> 
> The newer versions from the vendor _do not_ work! Any combination of those tended to fail on me.
> 
> The problem I actually had was that the Ignition Gateway service in services.msc was re-initialized and the user log-on property that was there had to be refreshed and saved. After that, the service was stopped/started. With the older gateway SQL Server drivers (and same user log-on with Windows Auth), and the related auth .dll file, the databases successfully connected!

I'm using SQL Server 2017, which may be why I needed the newer dll's and you didn't.

I also had to run the Ignition Gateway service with a specific login (rather than the system login) to connect.

[Previous page](https://forum.inductiveautomation.com/t/database-tag-history-error-issues/22983.md?page=1)