The "classic" for this one is a GUI client session which is still connected and hasn't timed out or (ODBC/JDBC) exhausted it's result set.
Look for ODBC/JDBC/UO connections or UniAdmin..... If in doubt then: Disable access to UniVerse (I use permission changes from a script). "uvlictool clean_lic -a" "ipcs -mop|grep ace|wc -l" to count how many sessions are in use MASTER OFF anyone left behind Stop the unirpc daemon Try stopping again afterwards... I seem to recall that a connection from a client session left open binds the TCP port open even if the server side is killed (Unix). In the above scenario you may find that you can't restart the RPC service without killing the CLIENT| side of the connection to make Unix let go of the port. You could always blow away the TCP service on Unix (briefly) using "net stop" which may clear it. Regards JayJay ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
