You may also want to setup automated database maintenance on all of
your databases, especially the tempdb database.  From the Enterprise
Manager -> Maintenance Wizard, I setup a weekly maintenace for every
single database I have.  If you are doing the initial discovery, you
may want to manually truncate the transaction logs.

One other thing i noticed is make sure your SQL stored procedures are
up to date.  You may see errors in you nv.log refering a certain
version of the stored procedures.  The version of the Microsoft SQL
ODBC driver should be version 3.7x, and after you install the newer
version, run the following command from the \winnt\system32 directory
to update the stored procedures.

isql \Usa \S(yourservername) \iinstcat.sql

To get the latest SQL Server ODBC Drivers, goto the microsoft site and
look for MDAC 2.1.

Hope this helps.
Xu He

--- OGrant <OGrant AT PEC DOT COM> wrote:
> check your nv.log, as well as sql server - you may
> have run out of space in
> one or more of your databases -- usually due to a
> rapidly expanding
> transaction log.
>
> > -----Original Message-----
> > From: Todd E. Lewis
> [SMTP:telewis AT PROVIDENTBANKMD DOT COM]
> > Sent: Tuesday, April 27, 1999 1:09 PM
> > To:   NV-L AT UCSBVM.ucsb DOT edu
> > Subject:      Netview NT Trapd
> >
> > Has anyone ever gotten the message that trapd is
> not communicating with
> > SQL database or it not loaded ? This causes the
> event browser to just
> > display history events. I also seem to have a
> problem with the event
> > browser just stopping even though the trapd is
> running.
>

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com