If you have the W2K Support Tools loaded or the NT 4.0 Resource Kit, you
can use kill -f <ProcessID> to kill the BPBKAR32.EXE Process.  This has
always worked for us on a W2K server.

-----Original Message-----
From: Bob Bakh [mailto:bob.bakh AT home DOT com] 
Sent: Thursday, October 11, 2001 2:13 PM
To: Carlos Perales; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] BPBKAR32.exe Processes

The last time I saw this I ran the bpbkar log and found the NT TCP 10054
error, updating your NT patches, and checking for duplexing issues on
the
network help resolve this problem.

The only way to get rid of them once they get stuck is a reboot.

If you look at the bpbkar log and the bptm log on the media server
you'll
see a loss of communication, sometimes the network port on the master is
full and causes a time out that causes the client to close down and
hang.
It's supposed to error out, but sometime the OS doesn't report the error
and
then it just hangs.

patch things up, patch up NBU, also you my want a bigger pipe on the
master/media servers, lastly the tcp socket close timeout on the master
and
media server may need to be adjusted down.

Thanks,

Bob