We are having a problem with the Lotus Notes agent for ADSM
when running with Lotus notes V4.6.2a.  The environment is a
two-node Windows NT cluster.

Several hundred .nsf files are saved successfully with the agent.
These have all just been created; they each have about 230
"documents" in them, and all save fine.  However, there are three
.nsf files with some real messages in them.  When the agent
hits these, it just "hangs".  The session as viewed from the
server goes into an "IdleW" state.  The client is consuming
no CPU or IO.  It appears to be just waiting for something.
The only way to stop the agent is to ^C and then do an end
task via the taskmanager.  And then, even if Lotus tries to
get into the file, it fails, saying the file is locked.  Apparantly
the agent has set some sort of lock on the file, either
internally or externally, and it's not released.

When the client starts up, it prints a message stating that
it was built with the "Lotus Notes API V4.6.1".  Is it possible
that this dot release to Lotus has broken the agent?

This problem is somewhat of a showstopper for this site's
rollout of ADSM.  Can anybody offer any ideas on how
to deal with this?

Kelly Lipp
Storage Solutions Specialists, Inc.
lipp AT storsol DOT com
www.storsol.com
(719) 531-5926