- Product: Voyager
- Product Version: 8.1.1
When a remote Z39.50 target disconnects from session with Run-time errors.
- The client can crash after a period of inactivity in the Remote Search session.
- The client can crash when the target is removed from the Remote Search list.
Issue 16384-21121 / VYG-4617 is currently in Development.
- In System Administration, set up as z3950 target, a database which has a timeout of known length.
- In Cataloging, connect to target database.
- Wait longer that the timeout period.
- Try to remove the database from the list of remote search connections.
- Receive RTEs below:
Run-time error '65099': Connection lost Application will be aborted
Run-time error '440': Application-defined or object-defined error
Run-time error '97': Can not call friend function on object which is not an instance of a defining class
Run-time error -2147418105 (80010007): Application-defined or object-defined error.
- Avoid leaving your Remote Search search session inactive for any amount of time.
- Remove target from Remote Search list before remote server disconnects.
Remote connections thru Z39.50 can have very brief timeouts (session inactivity timers) before they disconnect. For example, Library of Congress is 3 minutes (See the Library of Congress Z39.50 session inactivity timer information). OCLC WorldCat has a similar very brief timeout (5 minutes). Other libraries have even shorter timeouts. So that you do not lose your work, it is wise to not leave your Remote Search session inactive and to disconnect from the Remote Database as soon as you do not need it.
- Article last edited: 10-Jul-2019