• Article Type: General
• Product: Aleph
• Product Version: 17.01

Description:
We have downloaded the Java Virtual machine to a number of workstations in order to print from the GUI, and printing works fine on those machines. Today, however, we added it to a workstation and, when trying to print a loan receipt we get the following message: Remote file error (global-91) Unable to open local file. This has not occurred when trying to print loan receipts on other workstations.

Resolution:
These kinds of problems are pretty tough to diagnose remotely, as they only involve workstations. But I do have some suggestions for things to try to resolve the problem.

It seems that the problem could be caused by a couple of things. A table is out of whack and is pointing to a file that doesn't exist, a file that should be there is not, or possibly the program is trying to write a file to a protected space and then can't find it. And there may well be other possibilities.

For the first two possibilities, I think one way to check it would be to get a copy of the c:\al500 directory from a working workstation and copy it to the one that isn't working. If there are settings you want to preserve, you can copy or rename the original one for later restoration. If it works, that suggests that either a file was missing on the workstation or a table has a bad setting. If you need the original settings, you can restore them little by little to figure out what file might be wrong. If you don't, the problem is resolved.

For the third possibility, you might try running the process under a Windows login that has administrative privileges. If it works that way, there's a pretty good chance that you have a permissions problem. If you can live with your circ login having administrative or power user privileges, that would be an easy route to a solution. If not, you might just start looking for subfolders, either in the al500 folder or in c:\temp or other such places, where your current login does not have permission to write and grant it write permission.

In this case, the problem did turn out to be with administrator permissions and the site was able to fix it.

• Article last edited: 10/8/2013