Re: Event ID 2019 and Event ID 333
- From: "Dave Patrick" <DSPatrick@xxxxxxxxxxxxxxxx>
- Date: Mon, 20 Nov 2006 10:08:59 -0700
I'd try to work through the issues. Also check the symantec site since there are known issues.
http://service1.symantec.com/SUPPORT/sunset3.nsf/4a466c543a83dec985256c92005cb9ae/95ae9dd0acccc1f985256c92005b5975?OpenDocument&src=bar_sch_nam
http://service1.symantec.com/SUPPORT/ent-security.nsf/0/6d204c10340de3648025706c003485ed?OpenDocument&seg=hm
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"james" wrote:
Typical cpu usage is under 5%
memory usage usually sits around 650-700MB out of 2GB
network usage is around 0-1%
the time that the server actually starts to crash is at a period when there
is little to no use.
The server is home to symantec AV corp edition 10.1.4 (i think) about 700
home folders and roaming and mandatory profiles. It also oes WSUS, and runs
peachtree acct for 1 user.
From the task manager stats it does not seem to be overloaded
.
- References:
- Re: Event ID 2019 and Event ID 333
- From: Dave Patrick
- Re: Event ID 2019 and Event ID 333
- From: james
- Re: Event ID 2019 and Event ID 333
- From: Dave Patrick
- Re: Event ID 2019 and Event ID 333
- From: james
- Re: Event ID 2019 and Event ID 333
- Prev by Date: Re: Site Creation
- Next by Date: Re: Site Creation
- Previous by thread: Re: Event ID 2019 and Event ID 333
- Next by thread: Re: Event ID 2019 and Event ID 333
- Index(es):
Relevant Pages
|
Loading