An Easy Way To Change The Cataloging Runtime To Voyager 13. Repair

September 9, 2021 By David Serisier Off

Table of Contents

Recommended: Fortect

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

Download this software and fix your PC in minutes.

Here are some easy methods to fix Voyager Cataloging Runtime 13 issue.

Symptoms

The location “RTE 13: Type Conflict” occurs on 10.0.0.3 clients when downloading an offline loan record file due to a user scenario that has two barcodes from active and identical users in different user groups.

Error status

Replication steps

Create a user with two user groups, each with the same active barcode.
Load loan user without database connection to get offline loan.
Perform each transaction with a specially created user
Connect the loan borrower to the database, try loading a large loan file, call “RTE 13: Type Mismatch” and the Error.txt file in your local Voyager folder.

Article last modified: March 20, 2020

Symptoms

When a specific remote Z39.50 target disconnects with runtime errors.

The client may crash after this period of inactivity in the remote search session.
Visitor may crashif the target is also removed from the remote search list.

Error status

Replication steps

In sysadmin, you first configure the database as a z3950 target with a known timeout period.
Enter cataloging to work with the database.
Please wait a little longer than the waiting time.
Try removing the index from your deleted siblings search list.
Get the RTE below:

Runtime error "97": We cannot call a friend's function on an object, nor is it an instance of the defining class

Workaround

Do not leave a remote exploration session for long, less active periods.
Remove the target from the remote search list before disconnecting the remote computer.

Additional information

It may take a very short timeout (no session timers) before disconnecting remote connections via Z39.50. For example: Library Congress – 3 times (see Library Idle Timer InformationZ39.50). WorldCat oclc provides an equally short latency. Other libraries have even less latency. To avoid losing your personal work, it is recommended that you do not leave the remote search session idle and disconnect from the remote database as soon as you no longer need it.

Article was last modified: 10.07.2019.

Voyager will be installed on all computers in the central library during IT as part of the initial setup. Detailed instructions for the IT department can be purchased in the Bard2 article, “Voyager Buyer Installation” (Access restricted to subscribers to allow employees).

Two-Step Opening Process

There are two options for running employee Voyager components (also known as employee clients) on slave computers:

Double-click the PuTTY shortcut on the desktop to open a Secure Shell (SSH) tunnel to the Voyager server; Once it opens, you can cut it. (This workaround was designed to avoid timeout issues caused by firewall settings.)
To open a specificVoyager Personal, you must be signed in to Module Plus. This way, each user ID password works for regular units, so if you’re already logged in when it comes to one, you can open the next one without logging into a specific previous home.

Configure PuTTY For First Use

Recommended: Fortect

Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

Before using Voyager Personal Modules on a specific machine for the first time, each of these users must perform a unique restore to properly configure PuTTY. How to run a single patch:

On the Central Library drive, go to Voyager> v9 Installation Files> Custom Computer Files> PuTTY to open PuTTY
Copy folder:

Right-click the Voyager merge icon on the desktop (if this method asks if you want to swap an existing file, answer yes)

Right click to see the One Right Click Combine star you just copied to your desktop to display the Adventure menu.

Select Combine (first item on the menu).
Usually appears as followsfurther warning:

Click Yes to close the warning and continue.
The following verification principles appear:

becomes

Click OK to ignore the message.

Double click on the PuTTY table link icon which is open to PuTTY.
The following warning is displayed:

Click Yes to update the settings so the warning no longer appears.

You will then receive a message that you can collapse.

You can now safely remove the Voyager merge icon by right clicking on the desktop (do not remove this type from the shared drive).

Running Voyager With Multiple Monitors

There is your own known issue with Voyager when using multiple monitors. The error message is usually “Runtime Error 6: Message Overflow” in this particular cataloging mechanism. This usually happens because the user moved the Cataloging Items window to a secondary window and then the control tried to find it.This is the id of the start page.

A workaround might be to start the cataloging section (and enter) in the main window. In this window, do a full search for the Bib ID. Once the scan is complete, the user can drag and drop your module’s directories onto any monitor and everything should continue as usual.