Thanks for the reply. There is some comfort in shared misery. ☺
I am sorry to say that my AEM server and my print server are both running Windows Server 2019, so if your issue is related, you aren't likely to see a resolution.
On Friday, July 30, 2021 at 10:03, Jason Hamilton eloquently inscribed:
> You may be happy to learn you are not the only AEM customer experiencing
> issues. I forget the exact error code, but it occurred roughly 3 weeks
> ago and I have not been able to resolve it. I use AEM for Alma with our
> campus Gmail. I am currently in the process of acquiring an updated
> Windows virtual server. The current instance we are running on is
> Windows Server 2008. My hope was migrating to a newer version of Windows
> Server would fix the issues, plus campus IT has been asking me to do the
> I will certainly let you know if upgrading to a newer version of Windows
> solves the issue, but from your experience, it sounds like it may be moot.
> I have not started working with our IT department system admins to
> troubleshoot yet, but that is my next step.
> Stay tuned...
> On Fri, Jul 30, 2021 at 9:52 AM Hammer, Erich F <[log in to unmask]> wrote:
>> This is a (library-related) IT question and not really a "code" question,
>> but I'm hoping someone has a suggestion or two...
>> Our workflow for ILL materials, holds and transfers between our own
>> libraries requires slips of paper. There is no way around that as best
>> we can imagine, and we don't want to manually generate these bits of
>> paper all day long. We have Alma sending email "letters" for each of
>> the (currently) 15 different kinds and/or locations for these needs,
>> and then we use Automatic Email Manager
>> (https://www.automatic-email-manager.com/) to process them and print
>> them to the appropriate receipt printer. AEM is written/published by a
>> very small group and is fiddly and we've had some hiccups, but it has
>> generally worked.
>> Until the other day when our servers were rebooted after the July updates
>> that fixed the "Print Nightmare" vulnerability. Now, we just get errors.
>> "Normal" printing works from everywhere, but AEM can't manage it to
>> anywhere (to any printer), and the company doesn't have a clue as to why.
>> I can't (and shouldn't) back out of the updates, and have updated the
>> printer drivers to the latest release. (Some brands of printers needed
>> changes after Microsoft's fix.)
>> Between Alma as a cloud service (i.e. without printing abilities) and
>> Microsoft's "Modern Authentication" with 2-factor, and serious print
>> spooler vulnerabilities and AEM quirkiness, I'm tired of this unreliable
>> process. I can't imagine we are the only library with this kind of
>> workflow, and thus either we are doing it "wrong", or other folks are
>> encountering this frustration too. Thus, I am wondering what other folks
>> are doing for this kind of thing. Do others use AEM and are happy with
>> it? Are there other products out there that can run as a service (i.e. not
>> within Outlook as a plugin)?
>> Erich Hammer Head of Library Systems
>> [log in to unmask] University Libraries
>> 518-442-3891 University @ Albany
>> "Prayer /n/: how to do nothing and still claim you're helping."