Getting an error about date/time stamps being ignored at over 3000 data points. My PC clock is not off so not sure if it is server side or what just cropped up mid flight.

I just got the same thing. First time I have seen that.

Well not just me then good must be a server hiccup.

Here's what I got:

 

 

Yeah thats the exact same thing Im getting as well.

My problem seems to have corrected itself this morning. Must have been a HiFi server issue?

It seems to be an issue that crops up now and then and I've never seen a real fix for it. I tried this and that in the past--this occurred to me over two years ago--then tried simply ignoring it. And you know what?? Everything works fine. It's only an issue if you think it is. When you conside that there must be around 87 million wx stations that report, 3000 are totally irrelevant.

Thank you for your wisdom and sage advice. However, being the inquisitive, engineering sort that I am, whenever I receive an error or, any other anomaly, I naturally seek out its source and a solution, if one is available. If I cannot identify and correct it on my own, I seek the aid of a community of experts. 87 million (?) and only 3000 involved, why that is a paltry number, except if you are IMC on approach to an airport at one of those locations.

While I have exagerated a little (ok more than a little) when it comes to the 87 MM figure, the 3000 still stands as an irrelevancy. I think that the only real useful advice I ever got in regards to the time stamp being out of date is simply to close and restart Active Sky. I started getting this in ASE and it has just carried over into AS2012 (my installed product). If you want real concrete advice you will need to submit a ticket request (or however they word it) at the official web site.