When left running 24x7, sometimes A JavaScript error is found on Monday and requires clearing to print #19
Comments
|
Hmmm....I wonder if this was due to the new Alma release over the weekend....and there's a place in the APD code that still poses a problem. |
|
This morning we experienced a similar occurrence. Perhaps there was server side maintenance this weekend as well. Mark |
|
Yes, there was a new release over the weekend. I'll look into it again. Thanks. |
|
Mark...is there anything in the log file from around the time this last happened? The file would be located in the username/AppData/Roaming/alma-print-daemon directory. Considering the screenshot you included, I'm going to guess no. |
|
I just checked there is nothing in the log since December 28. I also looked in the log for the December 7th occurrence and found nothing related. 12/8 has checking for update notes, and that is what I see on 12/28 as well. Mark |
|
Thanks for checking, Mark. |
|
This morning when we arrived the Printer Daemon was in an error state with different error messages than previously. See attached. Follow up clarification: The Printer Daemon was in error this morning, after I believe an Alma update occurred this weekend. However the error in the picture seems likely to be from the user clicking the icon to run the older version of the Daemon which we understand is not compatible with the updated JSON file format. So this error image is likely unhelpful. We removed the shortcut to the old version and the new version worked properly when restarted.
|
* Support multiple printer profiles Updates to support linking different Alma printout queues to different physical local/network printers. Also, one installation on a workstation supports multiple users with their own configuration. * Update package.json Option to install for all users or just the logged in user. * Update main.js Fix defect when writing error log. If a per-workstation installation, the app would crash trying to write the log where it didn't have permission. Fix logging to write to user's directory. * Update main.js Another attempt at fixing issue #19. * Upgrade electron and electron-builder Electron -> 9.4.2 Electron-Builder ->22.9.1 * Update README.md
|
This morning a javascript error was showing in a dialog box. Once we okayed it, printing resumed. |
|
That's progress...we got a line number in the error this time. :) |
|
Mark there was an error message: Error on 2021-04-04T02:17:52.204Z': 503 Service Unavailable - General error with the API Gateway – please retry later. This was with v1.3 beta. We are upgrading to 1.3 proper now. |
|
After the weekend update we received a similar error this morning. |
|
We are seeing this error now, too! |
|
@markcorry, with which version of the Alma Print Daemon? If pre-2.0, please try the 2.0 beta. Thanks. |
We just implemented Alma Print Daemon and got this error. However my IT department was reluctant to install a beta version, so we settled on 1.3.1, the latest stable release. Are bugs only fixed on the beta? If so, what makes a release stable? Is there a plan for a new stable release? |
|
@daniels, version 1.3.1 is no longer receiving updates. 2.0 added the ability the install the Alma Print Daemon as a Windows service, Any new features and bug fixes will happen in 2.0. Its been in use for quite a while by some Alma customers. We were hoping for additional feedback on the Windows Service feature before it comes out of beta. |
|
@evilsizorm, please give the latest beta a try, if you like: https://github.com/ExLibrisGroup/alma-print-daemon/releases/tag/v2.2.0-beta-02 |
This morning a dialog box showed indicating, "A JavaScript error occurred in the main process". I have attached an image. Even thought it looks like the daemon is running. Our staff reported that printing did not resume until the error was cleared.
TypeError: Cannot read property '0' of undefined at Function.
Mark
The text was updated successfully, but these errors were encountered: