MSAS Expired Dec 30, 1899

  • Thread starter Thread starter Frank
  • Start date Start date
F

Frank

Just got this error from MSAS, it reads:

'This version of Microsoft AntiSpyware has expired as of'
then the rest of the message is choped...

It then reads in section two of the window: 'The
Microsoft Internal Beta Version of Microsoft AntiSpyware
has expired as of December 30, 1899. Please contact
Microsoft for an updated version.'

- December 30, 1899?

I haven't rebooted yet, just thought I would post the
error before I did.
 
1) Check your system date and time.
2) start, control panel
Date, Time, Language, and Regional Options
Regional and Language Options
What does the top box on the Regional Options tab read?
Click Customize next to it.
Click on the Date tab
Click on the Long and Short date format drop-down boxes, and reset each of
them to the topmost setting.

See whether that takes care of the issue.
 
I checked the system clock before I posted and everything
was in order. The error has come up once since I
rebooted. Did a second clean boot and MSAS is now working
fine again... somehow the programs 'timebomb' date got
changed to the year 1899.
 
Keep a close eye on it. I've seen one other post where a date-related issue
was variable in a similar way--it made me wonder whether some overflow
depending on a minutes or seconds counter was involved--rather than a simple
date of the year.

Did you, in fact, check the long and short date formats?

--
 
Yes I checked the long and short formatting and they were
set at the topmost setting. I was running a cg program at
the time when it happened, It could be that the problem
might have been linked to a graphics driver version
issue. I uninstalled the video device and and installed
the drivers again from the oldest version to newest. The
problem has not come up again in the past two days, so I
think I'm in the clear.

If I see the error again, I will do a full scan of my
system setup, and report it again with an included system
log.

Thanks for the feedback, Frank.
 
Thanks for the detail about the graphics driver--that indeed might be
significant. This is the sort of issue that should go away with beta2, so
lots of digging into the precise cause probably isn't worth doing, but it's
nice to be able to get it to go away for the cases in which it does arise.
 
Back
Top