We haven't seen this problem in a while.  When the problem was hot
Jason Hughes, John Lantz, and Kurt Sahlberg posted some tips for
resolving the issue.

#1
"There is an executable I got from IBM called listdlls that will list
the processes and what libraries they are using.  Just run this and
look for any:sqllib\bin references.  These are the processes you need
to stop." IBM support used to be able to give the software.  I know
you can obtain it at:
http://www.sysinternals.com/ntw2k/freeware/listdlls.shtml

#2
Make sure the HTML Search Server is stopped.  DB2 may have put the
Start HTML Search Server shortcut in the Startup folder upon install.
I'm not sure what process/service this shows up as.  I use the Stop
HTML Search Server shortcut in the DB2 for Win NT folder.

#3
Try putting the PSAPI.DLL (from nt resource kit)
in the x:\xxxxx\system32 directory.
This will allow you to kill the db2 processes at fixpak install time.

#4
Try running 'C:\SQLLIB\BIN\db2perfi /u', this will tell you if there
are any performance monitors on, so that wasn't the problem.

This can be caused by the NT performance monitor (even on someone
else's PC looking at yours!) or TIVOLI and other remote control type
programs.

"William R. Mussatto" wrote:

> I had an NetCommerce client come back from the dead so the versions are a
> bit old.
>
> I am trying  to install a fix pack (July '98 against v 5.0 of UDB).
> However, it won't go in since the install program claims that there a DB2
> service or instance is still running.  System is NT4.0 Net Commerce V3.01
> I've stopped everything which has DB2 in its name on the services list.
>
> Any thoughts?
>
> Sincerely,
>
> William Mussatto, Senior Systems Engineer
> CyberStrategies, Inc
> ph. 909-920-9154 ext. 27
>
> =====
> To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod


=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod

Reply via email to