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?
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.
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.
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.
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.