Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JavaScript error with 2.1.0 #75

Closed
prbutler opened this issue May 17, 2023 · 2 comments
Closed

JavaScript error with 2.1.0 #75

prbutler opened this issue May 17, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@prbutler
Copy link

We are encountering what looks to be a JavaScript error on one of our circ stations running Windows 10 and the 2.1.0 daemon.

I uninstalled and reinstalled the daemon and the issue still occurs. Once the error occurs I can not do anything else in the daemon, can't delete or print the receipt and can not access the daemon configuration. If I cancel the print job from within Alma using the Printouts queue I can at least access the daemon configuration area, but the next time I try to print I get the same error message and the daemon is stuck again. Any suggestions? Thanks, Paul

This first image is when the print job first enters the daemon.
BSU-one

After I click OK this is the next thing I see, same error but the receipt is displayed in the daemon.
BSU-two

I see the same error here: #19 (comment)

@mgobat
Copy link
Contributor

mgobat commented May 17, 2023

@prbutler, I believe this error occurs when the Alma Print Daemon is configured to use a local or network printer that is no longer available to the workstation on which the Alma Print Daemon is running. Even if a printer name has changed, it will trigger this error. Is that possible in your case? I would suggest deleting the configured Printer Profiles in the Alma Print Daemon and recreating them in the UI.

There is a known issue in the underlying framework used in the Alma Print Daemon that prohibits catching this particular error in the code.

@mgobat mgobat self-assigned this May 17, 2023
@mgobat mgobat added the bug Something isn't working label May 17, 2023
@prbutler
Copy link
Author

Thank you, that resolved the error. Cheers, Paul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants