
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-04-2010 05:01 PM
Hello,
We recently upgraded to the latest version and I noticed that the "Last Seen Time" went backwards in time? For example, The First Seen time is 08/07/2010, but the Last Seen Time is 04/10/2010? Not sure what happened there. If I do a manual trigger scan, the time does not update to today's date. Server date and time is correct.
We recently upgraded to the latest version and I noticed that the "Last Seen Time" went backwards in time? For example, The First Seen time is 08/07/2010, but the Last Seen Time is 04/10/2010? Not sure what happened there. If I do a manual trigger scan, the time does not update to today's date. Server date and time is correct.
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-04-2010 06:23 PM
I think you are right actually and I'm just a dope today. I'm just reading the date wrong - it's dd/mm like you said doh!
Thanks.
Thanks.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-04-2010 05:33 PM
Don't think so, that looks correct on server. Must be something in the database, other databases on the same server report the correct time. Where would I check in the Lansweeper database for the correct date and time on each of the tables?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-04-2010 05:14 PM
Is it possible that the date format is wrong? (dd/mm)
