# Weird Gateway Logs: Full of starting up client project monitor, sqltaghistory error

**URL:** <https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 3, 2022, 12:56pm UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155 "2022-05-03T12:56:15Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [May 3, 2022, 12:56pm UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155/1 "2022-05-03T12:56:15Z")

</div>

My gateway logs are full of these messages, especially number 1

1. Starting up client project monitor. project=PackingStation scope=4
2. The datasource ‘millroom’ cannot accept data of the given type [**sqltaghistory**].

Regarding number 2, there is nothing in the store and forward quarantine. I thought I would ask here before contacting support.

---

<div class="post-metadata">

**Author:** ![stat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/stat/32/32530_2.png) [@stat](https://forum.inductiveautomation.com/u/stat)\
**Post date:** [May 3, 2022, 9:03pm UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155/2 "2022-05-03T21:03:52Z")

</div>

For number 1, that log message looks like a Vision client opened for project PackingStation.  
For number 2, that log message can occur when you have a tag configured to store tag history to a historical provider that is disabled. If you check Config \> Tags: History, is your “milroom” provider disabled?

---

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [May 3, 2022, 9:13pm UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155/3 "2022-05-03T21:13:06Z")

</div>

For number 1, I’m getting that message very often

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/a/6af46a44a7600d8b6d0f025b4e5d6824329dbe97.png)

Number 2, my _millroom_ source is enabled. I was running on a temporary gateway until I fully converted to v8.1 from v7.9. I downloaded a gateway back up from the temp and imported it to my production gateway (both used the same DB connections). That is when I started to see this message.

I’ve contacted support: #47269

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [February 2, 2023, 11:55am UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155/4 "2023-02-02T11:55:59Z")

</div>

Today I found that on one Gateway at one of our customers, we also have a log full of this:

 ![Screenshot_59](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/2/d263ae0f7887fc6eca1b28dbc85a19a0b3504cb6.png)

---

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [February 2, 2023, 12:49pm UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155/5 "2023-02-02T12:49:01Z")

</div>

I should have come back and posted the answer ☹.  
For us, the problem was a logout script that was running based on inactivity seconds. We have a default, read-only user that is logged in after a certain amount of inactivity, but there was a bug in the logout script. It wasn't looking at the current user, so after the client switched to the default user, it kept logging the default user in everytime the timer script was executed.

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [February 2, 2023, 1:44pm UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155/6 "2023-02-02T13:44:21Z")

</div>

The thing is, that I have a Client Timer script, but inside these scripts, there's nothing to do with inactivity or changing the user... 😕

---

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [February 2, 2023, 1:57pm UTC](https://forum.inductiveautomation.com/t/weird-gateway-logs-full-of-starting-up-client-project-monitor-sqltaghistory-error/59155/7 "2023-02-02T13:57:05Z")

</div>

These definitely look like project login events, but I don't know where else to check.
