Closed prbutler closed 1 year ago
@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.
Thank you, that resolved the error. Cheers, Paul
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](https://github.com/ExLibrisGroup/alma-print-daemon/assets/8865793/7f73e863-3889-4df3-a1a1-c865bcb39424)
After I click OK this is the next thing I see, same error but the receipt is displayed in the daemon.![BSU-two](https://github.com/ExLibrisGroup/alma-print-daemon/assets/8865793/8ce360b7-5c2f-46e2-ae72-17bc91cef8ad)
I see the same error here: https://github.com/ExLibrisGroup/alma-print-daemon/issues/19#issuecomment-912009060