Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

August 24, 2010 r2 definition - brought computers to a crawl

Created: 24 Aug 2010 | 4 comments
tekkid's picture
0 0 Votes
Login to vote

The definition entitled August 24, 2010 r2 that went out today to our computers around 2:30 p.m. brought our systems down to a crawl (computers ot servers).   Was there anything significant in this update?   Typically this only happens if the are having perf problems on the SEPM server, but this was not the case this time.   

Comments

Rafeeq's picture
24
Aug
2010
0 Votes 0
Login to vote

hi

as per this document rollback the defs on one group of clients; check if performace is normal

http://service1.symantec.com/support/ent-security.nsf/docid/2007111515160948

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

tekkid's picture
24
Aug
2010
0 Votes 0
Login to vote

It was the process of

It was the process of updating, computers returned to normal after the update.   This typically does not occur. 

tekkid's picture
24
Aug
2010
0 Votes 0
Login to vote

Received this error on our

Received this error on our file server, whatever it is, it has hosed all of computers on our network:

Event Type:        Warning
Event Source:    Symantec AntiVirus
Event Category:                None
Event ID:              42
Date:                     8/24/2010
Time:                     2:32:46 PM
User:                     N/A
Computer:          FS1
Description:
 
 
Auto-Protect Error: Auto-Protect is disabled because registration of the virus databases failedApplication has encountered an error.
For more information, please go to: http://www.symantec.com/techsupp/servlet/ProductMessages?product=SAVCORP&version=11.0.5002.290&language=english&module=1000&error=0074&build=symantec_ent

tekkid's picture
24
Aug
2010
0 Votes 0
Login to vote

Update: The error appeared to

Update:

The error appeared to only occur on our file server which locked up the server in question along with computers connecting to it via network mapped drive.