MAS 1.0.614 downleveled itself from 5729 to 5725

  • Thread starter Thread starter Leo Feret
  • Start date Start date
I can see that this issue is experienced by a number of users here and is
clearly documented (not necessarily the downleve, but the failure to
update.)

However, I'm not clear that it is a universal experience, and I'm not clear
that the proportion of users experiencing this is greater than those
experiencing similar issues with the previous build, which I'm sure you can
recall.

--
 
Bill Sanderson said:
I'll try to replicate this too, but as I've mentioned, I may run out of
time.
Click to expand...

Replacing the def files worked for me and others after a clean
install of build 614.

Bob Vanderveen
 
May be it will be helpful (error.log):
91::Object variable or With block variable not
set::Updates:LatestRulesetVersionID::30::27.06.2005 12:52:47
7::ln 10:Out of memory::gcasDtServ:ScheduleScans:Update::27.06.2005
12:52:55:XP:1.0.614
91::Object variable or With block variable not
set::Updates:LatestRulesetVersionID::30::27.06.2005 14:29:12
438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::27.06.2005 14:29:25:XP:1.0.614
438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::27.06.2005 17:11:31:XP:1.0.614
7::ln 10:Out of memory::gcasDtServ:ScheduleScans:Update::28.06.2005
02:00:07:XP:1.0.614
All symptomes are the same (upgrade, clear cache, then clean install of
1.0.614)
Alexey

"Bill Sanderson" <[email protected]> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ ×
ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:%[email protected]...
 
When you say replacing the def files, and clean install in the same
sentence--I'm not sure of the process.

Was that an uninstall, but leaving the installation folder content (and thus
the previous def files?)

Thanks!
--
 
I'm with Bob--explain the procedure and what didn't work.

I'm intrigued by these issues. 613 was quickly replaced by 614, so my
ASSumption is that there was an issue with 613. However, what I'm seeing
here are issues with 614--so maybe 613 is completely irrelevant, or maybe it
will turn out to be relevant whether 613 was ever on a given box--dunno.

--
 
I'm afraid I can't see anything in that log excerpt that helps me--the
errors.log file is filled with similar looking entries, even on machines
were all appears to be working perfectly well.

--
 
Bill Sanderson said:
When you say replacing the def files, and clean install in the same
sentence--I'm not sure of the process.

Was that an uninstall, but leaving the installation folder content (and thus
the previous def files?)

Thanks!
Click to expand...

Sure Bill,
I uninstalled using the installer.
Deleted the antispyware folder and all it's contents. Downloaded
build 614 and installed. I did *not* run it and did *not* select
auto update.
Replaced the def files.
Selected manual update and verified that software and definitions
are current.

Bob Vanderveen
 
Anonymous Bob said:
Sure Bill,
I uninstalled using the installer.
Deleted the antispyware folder and all it's contents. Downloaded
build 614 and installed. I did *not* run it and did *not* select
auto update.
Replaced the def files.
Selected manual update and verified that software and definitions
are current.

Bob Vanderveen
Click to expand...

Thanks--that's very clear. I don't know what the issue is when definition
updates "stick" like this--plun thinks that it is different in this build,
but I'm not convinced--I've seen the symptom multiple times over the course
of the beta. It does seem to be a little harder to get by this time,
though. I'm trying to find a machine where I can see it first hand, but
haven't yet.
 
Sure Bill,
I uninstalled using the installer.
Deleted the antispyware folder and all it's contents. Downloaded
build 614 and installed. I did *not* run it and did *not* select
auto update.
Replaced the def files.
Selected manual update and verified that software and definitions
are current.

Bob Vanderveen
Click to expand...

This seems to be the way to fix this problem. If I run the program and run
auto update before replacing the definitions I still have the problem. I now
have 5729. Thanks.
 
Gary said:
This seems to be the way to fix this problem. If I run the program and run
auto update before replacing the definitions I still have the problem. I now
have 5729. Thanks.
Click to expand...

Good morning Gary,

I'm happy to hear of your success. Thanks for the feedback.

Bob Vanderveen
 
Back
Top