I had one client with the same problem again last night, after I updated
the symevent files.  Although the symevent files appear to be new, mine
were at least a couple revs behind.  The sad part is I get shipped new NAV
CD's every month, and one would think the updated files would be included
on the new CD's.  I have servers freshly built within the last month that
had the old symevent files on them.

This is a very flaky problem and hard to reproduce.  4 out of the 5 clients
that had the problem before have been working fine the past couple of days.
I'm just going to shutdown the NAV Auto-Protect service and restart it
again after the backup with pre and postschedulecmd for now.

Let me know if you find out anything new.


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




                    Len Boyle
                    <SNOLEN AT VM DOT SA        To:     ADSM-L AT VM.MARIST DOT 
EDU
                    S.COM>               cc:
                    Sent by:             Subject:     Re: HIGH CPU usage
                    "ADSM: Dist
                    Stor Manager"
                    <ADSM-L AT VM DOT MA
                    RIST.EDU>


                    09/01/00
                    10:16 AM
                    Please
                    respond to
                    "ADSM: Dist
                    Stor Manager"





In article
<OF2F65B6F4.02C7180F-ON8625694A.005DBDE5 AT LIBERTYDIVERSIFIED DOT COM>,
John Monahan <JohnMonahan AT LIBERTYDIVERSIFIED DOT COM> says:
>
>In my testing of the NAV-TSM CPU problem, it seems that updating to the
>latest Symevnt files has solved my problem (at least on my test box).  Has
>anyone else with the same problem tried it also?
>
Good Morning John

We tried the 10.3.1.6 level of the Symevnt files and it does not
appear to work for us  As far as I can tell this is the latest level
and has been that level for a while. The Create date fot the copy
that I have is Friday, March 26 1999. The modified date is aug 29 2000.

We now have a problem ticket opened with both IBM and Symantec. I am
going to try a trace this weekend to try to find the file that
causes the problem so we can send a copy to ibm to give to symantec.

len
-------------------------------------------------------------------------
Leonard Boyle                               snolen AT vm.sas DOT com
Leonard Boyle                               snolen AT vm.sas DOT com
SAS Institute Inc.                          ussas4hs@ibmmail
Room RB448                                  len.boyle AT sas DOT com
1 SAS Campus Drive                        (919) 677-8000 ext 6241
Cary NC 27513