Andrew,

Here's what my Telecomm guy said:"The version of Norton AntiVirus we were
using on that server was 5.01.01 for WinNT. The services I stopped were NAV
Alert and NAV Auto-Protect.  Once those were stopped and disabled, the
scheduler service was started and things ran smoothly without a cpu rise".

Hope this help!

Ed



-----Original Message-----
From: Andrew Webster [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 15, 2000 6:29 AM
To: [EMAIL PROTECTED]
Subject: HIGH CPU USAGE


Hi John, Ed,

     Precisely which Norton Services did you have to stop? I find three
services on my clients:-
     NAV Alert
     NAV Auto-Protect (Stopped for backups)
     Norton Program Scheduler

     As you saying I need to stop all of them, including the "Alert" one. Or
are you saying you need to "disable" them so that they never start?
     Isn't there a Norton Device Driver (Control Panel|Services) do you do
anything with that?

All,

     Anyone have experience backup non-English  languages and gets
hangs/high CPU utilization on NT. We sure do on Japanese NT machines.

Regards
     Andrew



Re: HIGH CPU USAGE
 Forum:     ADSM - ADSTAR Distributed Storage Management
 Date:        Aug 14, 12:56
 From:       Pabalate, Ed <[EMAIL PROTECTED]>

John,

Here is the quote from our Client Guy, "It=92s confirmed!  In order to =
fix my
CPU-at-100% problem, I had to disable the Norton AntiVirus services.  =
Once
this was disabled, everything functions properly and the cpu does not =
clock
up to 100% and stay there like it used to.  I=92m not sure how NAV is =
causing
the ADSM problem, but it is definitely related..!" Thanks to all your
help!.....

Ed

-----Original Message-----
From: John Monahan [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 07, 2000 12:26 PM
To: [EMAIL PROTECTED]
Subject: Re: HIGH CPU USAGE


I also had this problem with the exact same symptoms and had an open =
PMR
for about 2 months on this issue.  After several traces and running
debugging code my problem was narrowed down to a problem or conflict =
with
NAV running and the CreateFile() Win32 API.  TSM calls CreateFile() =
during
backup and this was where it was hanging and driving the CPU up to =
100%.
One of the TSM developers gave me a utility to just test the API call
outside of TSM, and it also caused the high CPU utilization, so the =
problem
was determined to be "outside the scope of TSM".  All my clients are
virtually identical, this problem started on one client and seemed to
spread to another client every 2 weeks.  About 25% of my clients were
experiencing the problem before we found the cause.

Shutting down all NAV services during the backup is a workaround for my
problem, just disabling autoprotect didn't help, the actual services =
had to
be stopped.  If you're also running NAV on your client, try shutting =
the
services down.  If your problem seems similar, I'll be glad to share =
more
specific information.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    John Monahan
    Network Administrator
    Liberty Diversified Industries
    (763) 536-6677
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


Regards

--
Andrew Webster
PC, NetApp Filer, TSM
Sanno Move Project
Deutsche Real Estate Consulting Ltd. - Tokyo
Internal (but outside Tokyo): 88 408-7542
Tel. +81-3-5156-7542
Fax. +81-3--5156-4811
Mobile: 0907 184 8958

[EMAIL PROTECTED]

Reply via email to