I ran into this issue with my computer and one other staff member remarked that they had the same problem. I added the console to my startup and noticed that it always seemed to hang on the printer initialization section. I reviewed the printers I had installed on my computer (and there were many) and removed the ones I never use including some built-in MS ones. That seemed to help. This started happening with one of the 4.x installs. I am still on Win 7 but the other person was on Win 10.

flutebrarian@gmail.com

Thanks, Karen -- I'll look at the printers installed on the computer.

pshirley@cuyahogafallslibrary.org

We still have this problem - Jar errors prevent the SDA starting. Clearing the jarcache directory makes it more likely to start when when that happens. Any other thoughts?

pshirley@cuyahogafallslibrary.org

We migrated to hosted on October 28 and this has been a real problem at many of our locations since the day after migration. We have an open ticket with the helpdesk on this and the last I knew, III was going to get their cloud team involved. (LAKEL - 811851). It's an ongoing issue and has been extremely frustrating at our 40 locations in 9 counties with hundreds of staff Sierra logins every day.

We have sent data, sent packet captures, and all kinds of stuff but as yet, no response to our escalated ticket.

This never happened until we went hosted from always having our severs in house since 2002.

Sheryl VanderWagen
Lakeland Library Cooperative
Grand Rapids, MI 49534
sheryl@llcoop.org

sheryl@llcoop.org