I've never seen that message before, but in my experience, sql server (I
assume you're running that with netview/nt) needs some routine maintenance
to keep it functioning smoothly. In particular, you'll have to ensure that
the transaction log doesn't run out space (otherwise, you may be prevented
from writing to that particular database). I don't remember the exact
sequence, but most configurations for sql server are done through its
enterprise manager (I believe). On a few occasions, enterprise manager
prevented me from changing the database settings due to full transaction
logs -- I was locked out, in short, with no apparant way of clearing the
error through the gui. In those instances I ran some sql server scripts via
isql to manually dump the transaction logs, and then expand the size of the
The info above might not be helpful - are you getting any error messages in
NT's event log concerning netview/sql server? Also, can you tell how many
events are currently stored in the events database (contained in the Netview
schema)? snmpodump should be configured to periodically dump the event log,
as well as the sql database. You've probably set it up properly, but check
AT (or WINAT) for the snmpodump command.
> -----Original Message-----
> From: Todd E. Lewis [SMTP:telewis@PROVIDENTBANKMD.COM]
> Sent: Tuesday, April 20, 1999 11:09 AM
> To: NV-L@UCSBVM.ucsb.edu
> Subject: Re: Version 5.1.1 for NT Problem
> If I reboot everything is ok for awhile. The NV.log has the following
> "Trapd caught exception, attempting to recover"
> "exception in do purge"
> I've got it setup to purge after 500 events. Maybe there's a problem with
> the purge.
> How do you tell?
> >>> OGrant <OGrant@PEC.COM> 04/20 10:19 AM >>>
> I wonder what nv.log says -- what, if any, type of error messages are you
> > -----Original Message-----
> > From: Todd E. Lewis [SMTP:telewis@PROVIDENTBANKMD.COM]
> > Sent: Tuesday, April 20, 1999 10:10 AM
> > To: NV-L@UCSBVM.ucsb.edu
> > Subject: Version 5.1.1 for NT Problem
> > I just upgraded to version 5.1.1 and I now appear to have a trapd
> > with the event log not connecting to the sql database, so no new entries
> > get logged. Should the NT patch 4.0 be applied after the upgrade ?