Posted by Robert G Laurin on December 20, 2007 at 08:04:06:
I always tought that after a crash, Comet would automatically "clean-up" the old session upon restart and/or shutdown.
Yesterday one client's system lost power with a record extracted. Upon re-power, a new connection was granted to the station and the old one was not terminated. Tried re-boot and it won't go away.
Old connection was 72 new connection is 65.
Security server says only one connection, FileServer says 2 connection. We use unique station names (ENTRY12 in this case) with no overlapping partition number.
I tried all utilities and found nothing to shut it down. Only solution looks like a restart of the CFAM services on the FileServer - which means kicking off 80+ users.
There's a old NLMUTIL on the QTILITY menu, but any attempt to use it 'cause COSH TO REPORT "An error has occured in your applicaiton" message and un-gracefully go down with no possibility to restart Comet without terminating a few tasks first.
So How do we "KILL" an orphan Extract ?
Using Latest & Greatest of everything: Comet 2007.385 CFAM 7.05