- Article Type: General
- Product: Voyager
- Product Version: 8.2.1
?€¢ Discharging items in Circulation results in error:
"Run-time error '13': Type mismatch"
?€¢ Circulation client crashes, but previous item scanned is discharged successfully
?€¢ Problem may happen more often to particular operators based upon speed at which items are discharged
Items are being discharged in rapid succession, or too many items are being scanned at once.
If Voyager does not have enough time to process the existing transaction before another is entered, this can result in two barcodes that run together; then Voyager cannot find a match and is unable to process the discharge request.
Operators should adopt a slightly slower pace and discharge one item at a time.
This will allow Voyager time to ensure each barcode is processed separately.
This problem can also occur if multiple items are scanned at once and some items have hold requests on them.
Reporter can also generate "Run-time error 13: Filetype Mismatch" when you are trying to run archives and one (or more) .inp file is corrupt. You need to determine which file (or files) is corrupt and remove them from the archives. To do this, move all the .inp, .err, and .msg files in all of the Reporter subdirectories on the PC, and then starting with the most recent .inp file copy the file back to its correct location and attempt to run it. Continue to move files in methodically until you hit the corrupted file and delete it. Copy back all the remaining .inp files and try running the archives again. You may need to go through this workflow several times. If you had to delete an archived file that you need to run again, see: How to reprocess Reporter notices
Category: Circulation - Voyager
- Article last edited: 10/21/2019