5719 will not load

  • Thread starter Thread starter Tim
  • Start date Start date
T

Tim

I have been trying to acquire the new 5719 definitions in
vain. The loader shows the little radar antenna bleeping
away for minutes but the definitions never load. I have
re-booted, again in vain. I have sucessfully loaded
previous definitions with no problem. What could be
different about this one?
Thank for any help.
 
I've seen this kind of failure occasionally, and don't have any clear
understanding. You can let it go--5 minutes ought to be a fair test.

If that fails, one method we've used in the past is to delete the current
definition files. This may well do the job, although it isn't entirely
without risk. See this KB article to know which files are involved.
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519
 
I am curious about this as well. Is it a network issue?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
I don't think so, but I'm uncertain. There are two sets of update issues
which have appeared with some regularity.

1 is like this one--the "hang, on update." It isn't clear whether its a
real hang, or just something taking quite a bit longer than ususal, but we
seem to get a few posts with each update with this symptom--perhaps some
updates more than others, but that is very subjective.

2 are the folks who get "no internet connection" when they go to update.
All else on their machine and networking is working normally, but the
updater, specifically, sees something as wrong. I don't have a clue about
this one.

3 are the folks for whom the update apparently goes normally, and get a
successful completion message, but, in fact, when they check the defs by
some manual method (i.e. the bad checksum messages)--or retry the definition
update, it does it all again, ad infinitum (well--usually not for more than
a day or so.)

I don't have any clear picture of the update process--are temp files
involved? Is there an issue with numbers of temp files or naming? In the
case 3, is some other process locking things up such that after a reboot it
eventually works?


--

Steve Dodson said:
I am curious about this as well. Is it a network issue?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
Click to expand...
 
Back
Top