NetView 5.0 RevB was never tested with SP4 to my knowledge.  And the
release notes for 5.0 clearly specified SP3.  SP4 wasn't tested until 5.1.

But I still think Oliver's problem is covered by the new APAR PJ26414 for
folks using SQL Server.  We are shipping an efix for that today.  Call
Support if you want to try it.

James Shanks
Tivoli (NetView for UNIX) L3 Support



"Wigg, David" <David.Wigg AT WANG DOT COM> on 05/06/99 11:44:41 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  Re: Netview 5.0 RevB/NT4 sp4/ODBC problem?





Thanks for the info. Is there any info from Tivoli about this? Is NV 5.0
RevB not supported on NT4 sp4?

Dave

> -----Original Message-----
> From: OGrant [SMTP:OGrant AT PEC DOT COM]
> Sent: Thursday, May 06, 1999 3:23 PM
> To:   NV-L AT UCSBVM.ucsb DOT edu
> Subject:      Re: Netview 5.0 RevB/NT4 sp4/ODBC problem?
>
> I had some similiar problems with an earlier attempted install of sp4 and
> nv
> 5.1; as in your case, odbc drivers appeared to be the likely culprit,
> although I was never able to determine why nv 5.1 would be so sensitive
to
> them.  I finally re-staged the server, re-installed nt 4.0 w/ *sp 3*, nv
> 5.1, and sql server *with no patches* - results seemed to be quite good.
> However, as I described in earlier posts, upgrading to nv 5.1.1/mdac 2.0
> appeared to have *again* put the khybash (sp?) on my netview
> server...again,
> newer odbc drivers seem to be wreaking havoc.   After some wrestling with
> trapd and the object database, I retreated to the safe territory of nv
> 5.1.
> My $0.02.
>
> > -----Original Message-----
> > From: Wigg, David [SMTP:David.Wigg AT WANG DOT COM]
> > Sent: Thursday, May 06, 1999 9:41 AM
> > To:   NV-L AT UCSBVM.ucsb DOT edu
> > Subject:      Netview 5.0 RevB/NT4 sp4/ODBC problem?
> >
> > Hi, I am installing Netview V5.0 RevB on NT4 Sp4. The installation
> > completes
> > ok and everything looks ok except for netmon and snmpcollect.
> >
> > There seems to be a problem with the ODBC access. If I set snmpcollect
> to
> > not use ODBC it starts up ok. This is not the real problem however. I
> > cannot
> > get netmon to run. (fairly basic requirement!)
> >
> > The netview logfile shows:
> >
> > 05/06/99 08:27:38 [trapd] The ODBC data source Tess_ds does not seem to
> be
> > configured correctly in the registry.
> >
> > 05/06/99 08:27:38 [trapd] Trapd: (initODBC) SQL could not connect to
> data
> > source tess.
> >
> > 05/06/99 08:27:38 [trapd]   1. () [Microsoft][ODBC Driver Manager] Data
> > source name not found and no default driver specified
> >
> > 05/06/99 08:27:38 [trapd] trapd.exe: ODBC database setup failed. Trapd
> > will
> > continue, but will
> >
> > log events in \usr\ov\log\trapd.log only.
> > 05/06/99 08:27:41 [nvcold] Initialization complete.
> > 05/06/99 08:27:42 [netmon] The ODBC data source Snmpcollect_ds does not
> > seem
> > to be configured correctly in the registry.
> >
> > 05/06/99 08:27:42 [netmon] (ConnectToODBC) Couldn't connect to data
> source
> > snmpcollect_ds.  Exiting snmpodbc.
> >
> > 05/06/99 08:27:42 [netmon]   1. [Microsoft][ODBC Driver Manager] Data
> > source
> > name not found and no default driver specified
> >
> > 05/06/99 08:27:42 [snmpcollect] snmpcollect starting up
> >
> > 05/06/99 08:27:42 [snmpcollect] snmpcollect about to spin thread
> >
> > 05/06/99 08:27:42 [ovstart] Done
> > 05/06/99 08:27:42 [snmpcollect] Output storage mode: flat files
> >
> > 05/06/99 09:53:02 [nmpolling] Failed to connect to netmon's shared
> memory
> > segment; error: The system cannot find the file specified.
> >
> > 05/06/99 09:53:25 [ovstatus] Done
> >
> > ODBC looks like the culprit but why? I have had to reinstall NT for
> > another
> > reason and the problem is still there. I have tried installing the ODBC
> > drivers from the netview cd - still no go. I don't want to use ODBC
> > anyway.
> > How can I get netmon to start up? Am I doing (or missing) something
> daft?
> >
> > TIA
> >
> > Dave