# Timetag stuck in the current data web service

**URL:** <http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138>\
**Category:** openPDC\
**Created:** [March 21, 2017, 3:38pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138 "2017-03-21T15:38:32Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![mnagostini](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/mnagostini/32/164_2.png) [@mnagostini](http://discussions.gridprotectionalliance.org/u/mnagostini)\
**Post date:** [March 21, 2017, 3:38pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/1 "2017-03-21T15:38:32Z")

</div>

Hi all.

I have noticed that the timetag in the current data web service is stuck at “1995-01-01 00:00:00”:

 ![](http://discussions.gridprotectionalliance.org/uploads/default/original/1X/11fa799a5fee4dbeb10180a9824bb1410fe61933.png)

I captured this snapshot some minutes ago (03/21/2017-15:23:37 UTC) from our openPDC. The measurement is a frequency (60 Hz nominal) from a PMU, running in real time.

It is happening in version 2.3.4, and in the new version 2.4.120 too. We have another one, v2.1.120, receiving the same PMU data, and there the timetag is ok.

Does anyone know somethig about this behavior? Is there some additional configuration in the new openPDC versions (2.3.4 and 2.4.120) for this?

Thanks.

---

<div class="post-metadata">

**Author:** ![marco.gonzalez](http://discussions.gridprotectionalliance.org/letter_avatar_proxy/v4/letter/m/f17d59/32.png) [@marco.gonzalez](http://discussions.gridprotectionalliance.org/u/marco.gonzalez)\
**Post date:** [March 21, 2017, 4:22pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/2 "2017-03-21T16:22:29Z")

</div>

Hi!

I have the same problem with the latest version.

Thank you and BR.

---

<div class="post-metadata">

**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\
**Post date:** [March 21, 2017, 5:32pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/3 "2017-03-21T17:32:22Z")

</div>

I just posted the issue to the GSF project on GitHub.

> <https://github.com/GridProtectionAlliance/gsf/issues/18>
>
> Measurement timestamps are serialized to the openHistorian 1.0 state file incorrectly because the underlying data type used to store TimeTag values...

I simultaneously committed a fix for the issue so this should be resolved in the next nightly build (openPDC v2.4.124).

---

<div class="post-metadata">

**Author:** ![ritchiecarroll](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/ritchiecarroll/32/2_2.png) [@ritchiecarroll](http://discussions.gridprotectionalliance.org/u/ritchiecarroll)\
**Post date:** [March 21, 2017, 7:19pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/4 "2017-03-21T19:19:57Z")

</div>

FYI - we are working on a patch that can be applied to the openPDC 2.4 official release so you won’t have to install a nightly build…

---

<div class="post-metadata">

**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\
**Post date:** [March 21, 2017, 8:08pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/5 "2017-03-21T20:08:33Z")

</div>

We have posted a new download in the [openPDC v2.4 release](https://github.com/GridProtectionAlliance/openPDC/releases/tag/v2.4). You can go there to download the patch. The file is called [OH1.0-time-series-web-service-fix.zip](https://github.com/GridProtectionAlliance/openPDC/releases/download/v2.4/OH1.0-time-series-web-service-fix.zip).

Here are the instructions to apply the patch:

1. Download the zip file.
2. You may need to go to Properties on the zip file and click the `Unblock` button. If you do not see an `Unblock` button, then you do not need to do this.
3. Extract the zip file.
4. Stop the openPDC service.
5. Replace GSF.Historian.dll in the openPDC installation directory (C:\Program Files\openPDC by default) with the one you extracted in step 3.
6. Start the openPDC service.

---

<div class="post-metadata">

**Author:** ![mnagostini](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/mnagostini/32/164_2.png) [@mnagostini](http://discussions.gridprotectionalliance.org/u/mnagostini)\
**Post date:** [March 21, 2017, 8:53pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/6 "2017-03-21T20:53:27Z")

</div>

Thanks guys! I’ll try the patch at night here in Brazil (about 23:00 UTC), and I let you know.

---

<div class="post-metadata">

**Author:** ![mnagostini](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/mnagostini/32/164_2.png) [@mnagostini](http://discussions.gridprotectionalliance.org/u/mnagostini)\
**Post date:** [March 21, 2017, 11:26pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/7 "2017-03-21T23:26:24Z")

</div>

Guys, I did the previous procedure, but unfortunatly the web service stoped working when I tried to use the new “GSF.Historian.dll”. Now I’m getting a refused connection error (ERR\_CONNECTION\_REFUSED) when I try to access the web service.

Any idea?!?!

---

<div class="post-metadata">

**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\
**Post date:** [March 21, 2017, 11:41pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/8 "2017-03-21T23:41:47Z")

</div>

Connection refused means it’s not listening on the port. There may have been an error loading GSF.Historian.dll. Check the error log.

Windows operating systems these days will flag files that come from network locations. The .NET Framework will block the openPDC from loading assemblies that came from network locations. Did you make sure to unblock the zip file before extracting the dll (step 2)? You may also try unblocking the dll itself.

---

<div class="post-metadata">

**Author:** ![ritchiecarroll](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/ritchiecarroll/32/2_2.png) [@ritchiecarroll](http://discussions.gridprotectionalliance.org/u/ritchiecarroll)\
**Post date:** [March 21, 2017, 11:42pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/9 "2017-03-21T23:42:18Z")

</div>

Seems unrelated to change. Perhaps a reboot?

---

<div class="post-metadata">

**Author:** ![ritchiecarroll](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/ritchiecarroll/32/2_2.png) [@ritchiecarroll](http://discussions.gridprotectionalliance.org/u/ritchiecarroll)\
**Post date:** [March 21, 2017, 11:44pm UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/10 "2017-03-21T23:44:32Z")

</div>

Also, you may need to delete ppa\_state.dat and stat\_state.dat file…

---

<div class="post-metadata">

**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\
**Post date:** [March 22, 2017, 1:31am UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/11 "2017-03-22T01:31:32Z")

</div>

We did some additional testing and managed to reproduce the behavior you described. Turns out it was an issue with the patch, and we were able to resolve it. We’ve updated the GitHub site with the fixed patch, so if you download the patch again and follow the steps to apply it, the historian web services should start working again.

---

<div class="post-metadata">

**Author:** ![mnagostini](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/mnagostini/32/164_2.png) [@mnagostini](http://discussions.gridprotectionalliance.org/u/mnagostini)\
**Post date:** [March 22, 2017, 2:14am UTC](http://discussions.gridprotectionalliance.org/t/timetag-stuck-in-the-current-data-web-service/138/12 "2017-03-22T02:14:14Z")

</div>

Guys, it is working great now! Just for the records, I followed the instructions again now, with the new patch, and it worked. No reboot nor historian file deletion were necessary. I´ll reproduce the solution in our production openPDC.

Many thanks for your fast response. Please let us know if we can help you with any other tests here in the MedFasee Project, at this side of the globe.
